
ICP
Risk analysis for ICP (ICP) on Base — contract 0x00f3c42833c3170159af4e92dbb451fb3f708917. Covers liquidity, holder concentration, creator activity and available contract security signals, with unavailable checks shown as unavailable.
0x00f3…8917 ExplorerPrice chart
Market overview
Market data
Trading activity
Markets & liquidity pools
What is ICP?
ICP ($ICP) is a BEP-20 token on the Base blockchain Its primary trading venue is aerodrome, with roughly $419.35K in live on-chain liquidity. Rug.Tools' current assessment of ICP is "Analysis Pending", based on live on-chain signals including holder concentration, liquidity depth, creator wallet history and contract permissions.
ICP is a Base token tracked live by Rug.Tools. Live market snapshot: $419,353 liquidity, $217,925 24h volume, $1,253,894,104 market cap, trading mainly on aerodrome. Holder distribution, contract authorities and creator history are available on demand — run a free Rug.Tools scan to generate the full risk report.
Rug.Tools signals
Key statistics
Rug.Tools analysis

Holder distribution
Token activity
No notable activity recorded yet.
Similar tokens
Loading similar Base tokens…
Learn more
Frequently asked questions
What is ICP?⌄
ICP is a Base token analyzed by Rug.Tools using public on-chain data — holders, liquidity, creator wallet activity and contract security signals. This page shows the latest cached analysis and refreshes automatically.
Is ICP safe?⌄
Current Rug.Tools verdict: Analysis Pending. The verdict is based on on-chain signals only. No token can be guaranteed safe: verdicts summarize on-chain risk signals only and cannot detect off-chain intent. Always do your own research.
How many holders does ICP have?⌄
Rug.Tools currently sees an unknown number of holders. The top individual wallet holds — of supply; the top 10 individual wallets together hold —.
Where is ICP traded?⌄
The primary trading venue detected on Base is aerodrome. Use the "Trade" button above to open the pair on DexScreener.
How often does this page update?⌄
This page renders from cached data in our database. It refreshes when a new scan runs — either on a scheduled background sync or when a user clicks Refresh above. Opening this page does not trigger a new scan.