55.2% of the top 10,000 tokens are HIGH RISK. 131 are confirmed honeypots – tokens where you can buy but cannot sell. 1,865 are upgradeable proxy contracts, of which 139 are controlled by a single private key that can silently replace the entire token implementation in one transaction. Only 18.7% pass all 127 security checks and receive a CLEAN verdict.

What Token Audit Found

BNB Smart Chain is the most dangerous chain in the dataset: 68.3% high risk and only 7.6% clean. Ethereum shows 59 confirmed honeypots – tokens that passed as legitimate long enough to enter the CoinGecko top 10,000, then trapped every buyer inside. The two most widespread risk patterns: 35.9% of tokens have no enforceable supply cap (unlimited inflation possible), and 34.4% have no timelock on privileged admin functions (instant malicious governance possible, no delay, no warning).

What Other Tools Miss

Token Audit runs 127 checks across 11 modules (8 currently active, 3 coming soon), including Ownership, Supply, Liquidity, Transfer, Approve, Permit, Pausability, Reentrancy, and Proxy Analysis. The checks that matter most are the ones competitors cannot run: transitive approve() call graph analysis, phantom balanceOf detection, EIP-2612 permit preload, reentrancy invariants, and asymmetric pause detection (pause that blocks sells but not buys). These threats are invisible to GoPlus, CertiK Skynet Token Scan, TokenSniffer, and Honeypot.is – which together cover fewer than 40 checks, all at the interface level. The 599 verdicts in this dataset driven by Approve and Reentrancy findings represent tokens that every competing tool would have passed as clean. This same deployer-behavioral approach powers ChainAware’s token launch auditor agent, which combines contract risk with deployer wallet screening in a single call.

Co-Founder Statement

“We assumed the top 10,000 by market cap would be the safer end of the market. What we found is that more than half carry meaningful risk vectors – and roughly 600 of those are threats that no other automated tool would detect. The sophisticated operators know exactly which checks existing tools run, and they design around them. Token Audit was built to catch what they build.” – Martin Ploom, Co-Founder, ChainAware.ai

Proxy Risk: 139 Tokens One Transaction Away From a Honeypot

Token Audit’s proxy classification goes beyond detecting whether a contract is upgradeable. It identifies who controls the upgrade – and the answer matters enormously. Of 1,865 proxy contracts in the top 10,000, 139 are EOA-controlled: a single unprotected private key can replace the entire implementation in one block, with no timelock, no multisig, no governance vote. BSC carries the highest concentration – 75 of those 139 EOA-controlled proxies are on BSC, where the tactic is a known professional rug pull pattern. On the positive side, 153 UUPS proxies have permanently locked or renounced their upgrade path – Token Audit surfaces this as an explicit positive signal rather than treating all proxies as equally risky. This deployer-level behavioral scoring is the same methodology behind ChainAware’s Wallet Auditor, applied here to contract creators and LP providers instead of individual users.

For the full methodology, chain-by-chain breakdown, finding frequency analysis, honeypot signal correlations, and the complete competitive comparison against GoPlus, TokenSniffer, CertiK Skynet, and Honeypot.is, read the deep-dive: ChainAware Token Audit Launched – We Tested 10,000 CoinGecko Tokens. Here Are the Results. →

ChainAware.ai is the Web3 Agentic Growth Infrastructure – 20M+ wallet personas, 98% fraud detection accuracy, 127-check Token Audit, Agent Trust Score for 274,000+ ERC-8004 agents available via the Prediction MCP. Named in CB Insights’ AI Fraud Prevention Market Map. chainaware.ai

The post 55% of the Top 10,000 CoinGecko Tokens Are High Risk. ChainAware Token Audit Shows Why. first appeared on ChainAware.ai.

The smart contract security audit market is broken. Manual audits cost $5,000 to $150,000 and take weeks. Meanwhile, thousands of new tokens launch every single day – and the vast majority of retail investors check exactly nothing before they buy. On Binance Smart Chain alone, 95% of new liquidity pools end in rug pulls. The tools that exist – GoPlus, TokenSniffer, Honeypot.is – catch the obvious scams. They completely miss the sophisticated ones.

Today, ChainAware is changing that. Token Audit is live: 127 automated security checks across 11 analysis modules (8 currently active, 3 coming soon), powered by deep code analysis and ChainAware’s behavioral intelligence layer. To validate the system, we ran it against the top 10,000 tokens on CoinGecko, sorted by market capitalization. Those are not random memecoins – they are the most-traded, most-held tokens in crypto. The results are alarming.

This article presents every finding. Specifically, you will learn what the most dangerous patterns look like at scale, which chains produce the highest risk concentrations, and why the tools you are currently using are systematically missing the threats that matter most.

The Study: 10,000 CoinGecko Tokens, 13,000 Audits, 6 Chains

The dataset covers the top 10,000 tokens by market capitalization on CoinGecko as of July 2026. Because many tokens exist simultaneously on multiple blockchains – USDT, for example, runs on Ethereum, BSC, Polygon, Base, and Arbitrum – the total audit count reaches 12,998 individual contract audits across 6 chains. Consequently, each audit is independent: the same token contract deployed on ETH and BSC receives two separate audits, because the contract code, liquidity structure, and ownership configuration can differ significantly between deployments.

Furthermore, this is not a random sample of newly launched tokens. These are established, widely-traded assets – the tokens that appear in your wallet app, on DeFi dashboards, and in portfolio trackers. If findings this severe appear in the top 10,000 by market cap, the situation in the broader universe of hundreds of thousands of tokens is considerably worse.

Each audit runs 127 checks across 11 modules (8 currently active, 3 coming soon), including Ownership, Supply, Liquidity, Transfer, Approve, Permit, Pausability, Reentrancy, and Proxy Analysis. Three detection layers underpin each audit: deep code analysis for semantic code-level findings, direct on-chain RPC calls for live state verification, and ChainAware’s behavioral database for creator and LP trust scoring. Results are stored in a structured database with one scalar column per finding – enabling the statistical analysis below.

Chain Distribution

Token classification matters for accurate results. Reflection tokens, rebasing tokens, ERC-4626 vault tokens, and bridge tokens all have non-standard transfer mechanics that would trigger false positives in a naive static analysis tool. Token Audit identifies these token types using dedicated classifiers and adjusts its findings accordingly – for example, a reflection token legitimately fails the transfer conservation check by design, and Token Audit documents this distinction rather than incorrectly flagging it as a theft vector. Accurate false-positive management at scale is essential for a tool that will be embedded in high-volume platform integrations, where a false positive on a major legitimate token destroys user trust far faster than a false negative on an obscure scam.

Ethereum leads by audit count, reflecting the concentration of established DeFi protocols on the oldest EVM chain. BSC’s 26.7% share is notable: despite hosting a smaller share of top-10,000 market cap tokens, it accounts for a disproportionate share of the worst findings – as the chain-by-chain breakdown below demonstrates.

The Headline Results: 55% of the Top 10,000 Tokens Are High Risk

The single most important finding from this study is also the most unsettling one. Among the top 10,000 tokens by market cap – the most established, most liquid, most widely held tokens in the entire crypto market – 55.2% receive a HIGH RISK verdict from ChainAware Token Audit.

Only 18.7% of audited tokens receive a CLEAN verdict – meaning they pass all critical security checks, have no meaningful rug pull vectors, and carry no significant code-level risks. Put another way, more than 4 in every 5 tokens in the top 10,000 carry some level of meaningful security concern.

These numbers require context. HIGH RISK does not automatically mean the token is a scam. Many HIGH RISK findings reflect architectural choices that are widespread in legitimate DeFi protocols: uncapped mint functions controlled by governance contracts, upgradeable proxy architectures managed by multisigs, or LP positions not locked because the team chose a different treasury structure. However, HIGH RISK does mean that the token contract contains mechanisms a malicious actor could use to harm investors – and that investors deserve to know about them before committing capital.

Moreover, 131 confirmed honeypots in the top 10,000 is not a small number. These are tokens where the Token Audit’s simulation analysis module confirmed that you can buy – but cannot sell. Twelve of those honeypots were found on Ethereum, the chain most associated with institutional quality and regulatory oversight. The assumption that “top 10,000 by market cap = safe” is demonstrably false.

Results by Chain: BSC Is the Most Dangerous

BSC stands out dramatically. Only 7.6% of BSC token deployments in the top 10,000 are clean – the lowest of any chain in the study. Meanwhile, 68.3% are high risk and another 23.0% are suspicious. Combined, that means 91.3% of top-10,000 BSC tokens carry some security concern. This finding is consistent with BSC’s broader reputation: Chainalysis research identifies BSC as hosting approximately 71% of all rug pull scams globally, driven by lower transaction fees that make deploying fraudulent contracts nearly cost-free.

Base, by contrast, is the cleanest chain in the study at 22.5% clean. Its 40.0% high risk rate reflects a newer, more curated DeFi ecosystem. Nevertheless, 40% high risk across Base’s top tokens is not a reassuring figure.

What Drives the Risk: The Two Dominant Findings

Two findings appear far more frequently than any other in the dataset, together driving 76% of all HIGH RISK verdicts. Understanding them is essential to understanding why so many established tokens carry elevated risk scores.

Finding #1: 35.9% of Tokens Have No Mint Cap (INV_S2_NO_MINT_CAP)

The most common single finding across the entire dataset: 4,668 tokens – 35.9% of all audited contracts – have a mint function with no enforceable supply cap. This means the token’s owner, governance contract, or admin address can create unlimited new tokens at any time, diluting every existing holder’s position to zero.

Critically, this finding appears almost exclusively in HIGH RISK verdicts. Cross-referencing the two columns shows that zero CLEAN tokens carry NO_MINT_CAP – a perfect separation. Every CLEAN token in the dataset either has no mint function at all or has a mint function with an immutable, on-chain cap. The 4,668 NO_MINT_CAP tokens are split between HIGH RISK (4,439) and HONEYPOT (75), with only 154 in the SUSPICIOUS tier.

For investors, the implication is straightforward: a token with an uncapped mint function carries a structural risk that no amount of team credibility or market cap size eliminates. The inflation vector exists regardless of whether the team currently intends to use it.

Finding #2: 34.4% of Tokens Have No Timelock on Privileged Functions (INV_O6_NO_TIMELOCK)

The second-most common finding: 4,470 tokens – 34.4% – have privileged administrative functions (ownership transfer, fee modification, upgrade execution, mint authorization) with no timelock. A timelock requires that any privileged action be announced on-chain and delayed by a minimum period – typically 24 to 72 hours – giving the community time to react if a malicious or compromised admin executes a dangerous change.

Without a timelock, a single administrative transaction can drain a protocol, rug liquidity, or convert a functioning token into a honeypot in a single block. The attacker’s advantage is complete: investors cannot react to changes they cannot anticipate. Adding a timelock costs developers essentially nothing but a few lines of Solidity – which makes its absence in 34.4% of the top-10,000 tokens particularly striking.

Together, NO_MINT_CAP and NO_TIMELOCK account for the overwhelming majority of high-risk verdicts in this dataset. Both findings are invisible to honeypot simulation tools like Honeypot.is – which only checks whether a sell transaction reverts. Furthermore, both are absent from the GoPlus Security API’s detection layer. ChainAware’s Ownership and Supply modules specifically scan for these patterns using deep code analysis, which can trace through function call chains to confirm whether an enforceable cap or delay mechanism actually exists – not merely whether the contract declares one.

Liquidity Risk: 25.7% of Tokens Have Completely Unlocked LP

Beyond the supply and ownership findings, the Liquidity module produced the study’s most operationally urgent results. Liquidity is the primary signal that drives 42% of all verdicts – more than any other module – because liquidity risk is both the most directly dangerous and the most immediately verifiable.

The 25.7% unlocked LP figure is particularly significant. When LP tokens remain in the deployer’s wallet, the entire liquidity backing the token can be removed in a single transaction. Every investor who holds the token is exposed to total loss within one block. The deployer may have committed publicly to never removing liquidity – but without an on-chain lock, that commitment is entirely unenforceable. For how ChainAware detects LP lock status across both V2 (ERC-20 LP tokens) and V3 (NFT positions), see the Liquidity Verification module documentation.

Notably, liquidity lock expiry detection – finding INV_L3_LOCK_EXPIRED – currently has zero hits in the dataset. This finding detects LP locks that have already expired but the associated tokens have not yet been removed. Its absence likely reflects the study’s population: tokens with expired locks often appear after rug pulls have occurred, meaning the token may have been delisted or the pool may have been drained before it entered the CoinGecko top-10,000 dataset.

Confirmed Honeypots: 131 Tokens Where You Can Buy But Cannot Sell

Token Audit’s simulation analysis module forks the relevant blockchain, executes a real buy transaction inside the fork, then attempts a sell. When the sell reverts – meaning the token architecture actively prevents investors from exiting their positions – the verdict is HONEYPOT. This study confirmed 131 honeypots across the top 10,000 CoinGecko tokens.

Ethereum’s 59 confirmed honeypots deserve special attention. The assumption that Ethereum’s higher gas costs and more sophisticated user base filter out honeypot contracts is not supported by this data. Sophisticated honeypots on Ethereum often work precisely because they look legitimate: verified source code, reasonable tax rates, functioning buy mechanics, and professional-looking documentation. The sell block is implemented deep in the transfer call graph – typically using assembly instructions or layered delegation patterns that simple rule-based scanners do not detect.

What Makes a Honeypot: The Three Strongest Signals

Signal 1: hp_CUSTOM_TRANSFER_ENTRY_POINT – Present in 63% of confirmed honeypots (correlation +0.34). This finding fires when the token contract routes transfer calls through a non-standard function before reaching the standard _transfer implementation. Custom entry points are the primary mechanism honeypot developers use to insert sell-blocking logic while keeping the standard ERC-20 interface intact.

Signal 2: hp_UNEXPECTED_EVENTS_IN_TRANSFER – The single highest-correlation honeypot predictor at +0.46, present in 50% of confirmed honeypots. When a transfer function emits events beyond the standard Transfer(from, to, amount) required by ERC-20, it almost always indicates hidden logic inserting itself into the transfer path.

Signal 3: hp_LAYERED_TRANSFER_DELEGATION – Present in 53% of confirmed honeypots and 10.2% of all tokens. Layered delegation means the transfer function calls internal functions that call further internal functions, each potentially adding conditions. Professional honeypots use five or six levels specifically to bury the sell-blocking condition deep enough that automated scanners trace only the outer layers. For how ChainAware’s transfer invariant checking works, see the Transfer Verification documentation.

What Only ChainAware Finds: The Sophisticated Threats

The most significant contribution of this study is not the headline numbers – it is the class of threats that appear in this dataset and cannot be detected by any competing automated tool. ChainAware Token Audit runs 127 checks. Competitors like GoPlus run approximately 40. CertiK Skynet’s free Token Scan runs 19. The gap between those check counts corresponds directly to classes of threat that are invisible to current market-standard tools.

Transfer Conservation Analysis: The Silent Value Drain

Token Audit’s most technically distinctive check is Transfer Conservation (INV_T1_CONSERVATION_FAIL): the invariant that when Alice transfers 100 tokens to Bob, Alice’s balance decreases by exactly 100 and Bob’s balance increases by exactly 100. If sender_lost does not equal recipient_gained, value is being silently diverted – typically to a hidden fee recipient not disclosed anywhere in the token’s interface. Conservation-failing tokens pass every honeypot simulation test. Honeypot.is returns CLEAN. GoPlus returns CLEAN. The investor loses capital on each trade while the token technically allows selling.

The Phantom Balance variant (INV_T5_PHANTOM_BALANCEOF) – found in 5 tokens – is even more sophisticated. The token maintains two separate balance mappings: one that balanceOf() reads and displays to the investor, and a different one that _transfer() actually debits. Your wallet shows you holding 10,000 tokens while the transfer mechanism has already marked your real balance as zero. For the full invariant specification, see the Transfer Invariants documentation.

Permit Correctness: The EIP-2612 Attack Surface

EIP-2612 permit() is implemented in 30% of tokens in this dataset (3,903 tokens). No automated scanner other than ChainAware checks whether the permit implementation is actually correct. Finding INV_P7_PRELOADED_PERMIT – a constructor-time unlimited approval grant – appears in 21 tokens. These 21 tokens allow the deployer to drain any holder’s position at any time using a signature created before any investor bought the token. For how ChainAware detects permit vulnerabilities, see the Permit Verification module.

Approve Security: The Transitive Attack

ChainAware’s Approve module traces the complete call graph of approve() – catching tokens where calling approve(spender, 1000) also silently writes the caller’s balance to zero as a hidden side effect. Finding INV1_EXTRA_STATE_WRITE appears in 63 tokens. INV3_EXTERNAL_CALL_IN_APPROVE appears in 28 tokens. Both require deep code analysis. Neither GoPlus, TokenSniffer, CertiK Skynet, nor De.Fi Scanner runs this analysis. See the Approve Verification documentation.

Reentrancy Analysis

ChainAware is the only automated token scanner that includes reentrancy detection. This study found 540 tokens with no reentrancy guard (INV_R2_NO_REENTRANCY_GUARD), 485 tokens using legacy ETH transfer patterns vulnerable to callback exploitation (INV_R6_ETH_TRANSFER_LEGACY), and 48 tokens with read-only reentrancy exposure (INV_R5_READONLY_REENTRANCY). According to the OWASP Smart Contract Top 10, reentrancy remains one of the most exploited vulnerability categories in DeFi. See the Reentrancy Verification documentation.

Proxy Analysis: 13.2% of Tokens Are Upgradeable Contracts

Token Audit detected proxy contracts in 1,865 tokens – 14.3% of all audited contracts. More importantly, it classifies each proxy by who controls the upgrade function, producing a six-tier risk assessment for the upgrade authority.

Tier	Upgrade Control	Tokens	% of Proxies	Risk
EOA-Controlled	Single private key	139	7.5%	🔴 Critical
Unknown Auth	Cannot be resolved	383	20.5%	🟠 High
Contract-Controlled	DAO / protocol governance	1,152	61.8%	🟡 Medium
Multisig-Controlled	Multiple required signers	29	1.6%	🟢 Low
Timelock-Controlled	Delayed on-chain execution	9	0.5%	🟢 Lowest
UUPS Locked / Renounced	Upgrade permanently disabled	153	8.2%	Immutable

Among all proxy findings, the 139 EOA-controlled proxies represent the most urgent concern. These tokens are upgradeable by a single private key – no multisig, no governance vote, no timelock delay. One transaction from one address can replace the entire contract implementation. BSC accounts for 75 of the 139 EOA-controlled proxies – 54% of the most dangerous proxy tier on less than a third of the token count. For how ChainAware classifies proxy types, see the Ownership Verification module documentation.

Risk Score Analysis: What the Numbers Say at Scale

Liquidity and Supply together drive 76% of all verdicts. The 2.8% driven by Approve and 1.8% by Reentrancy represent high-value findings that no competitor detects. Those 599 verdicts cover the sophisticated operators who invest in clean-looking code specifically to pass GoPlus and TokenSniffer while hiding more subtle attack vectors.

How Token Audit Compares to Existing Tools

Security Check	GoPlus	TokenSniffer	CertiK Skynet	Honeypot.is	ChainAware
Honeypot simulation
Mint capability				❌	+ hidden mint + cap quality
LP lock status			❌	❌	(V2 + V3 NFT positions)
Timelock absence check	❌	❌	❌	❌	Unique
Approve() call graph analysis	❌	❌	❌	❌	Unique
Transfer conservation invariant	❌	❌	❌	❌	Unique
Phantom balanceOf detection	❌	❌	❌	❌	Unique
Permit() correctness (EIP-2612)	❌	❌	❌	❌	Unique
Reentrancy analysis	❌	❌	❌	❌	Unique
Creator behavioral Trust Score	❌	❌	❌	❌	Unique
LP provider Trust Scores	❌	❌	❌	❌	Unique

GoPlus Security is the market standard, averaging 717 million monthly API calls in 2025. Its coverage is broad but rule-based rather than semantic. The approve transitive attack, phantom balance exploit, permit preload, and reentrancy vectors are all invisible to GoPlus’s current architecture. For how ChainAware fits into the broader DeFi security ecosystem, see our Rug Pull Detection Tools comparison and DeFi Compliance Tools guide.

The Behavioral Layer: What Code Analysis Cannot See

Code analysis answers one question: does this contract contain dangerous mechanisms? It cannot answer a more important one: does the person who deployed this contract intend to use those mechanisms maliciously?

This distinction matters because the most dangerous operators specifically invest in clean-looking code. A professional rug pull team in 2026 runs deep code analysis before deploying, checks their own contract against GoPlus, and removes every pattern that produces a red flag. They keep the mint function but make it look like a governance-controlled feature. They leave the LP unlocked but explain it as a treasury management decision. The code passes every automated check. Then, after accumulating enough liquidity, they execute.

ChainAware’s behavioral Trust Score system operates on a fundamentally different signal: the on-chain history of every wallet that deployed the contract and every wallet that provided liquidity. A deployer whose previous contracts ended in rug pulls carries that history regardless of how clean the new contract looks. An LP provider who has removed liquidity from multiple projects within 30 days of launch carries that behavioral signature regardless of how long they have held the current position.

These behavioral signals draw on ChainAware’s core fraud detection infrastructure – the same system that achieves 98% fraud prediction accuracy across 20 million+ wallet behavioral profiles. Combined with the code-level findings from Token Audit’s analysis modules, the result is the only token security tool that catches both the technical vulnerability and the operator intent simultaneously. For the full behavioral intelligence methodology, see What Are Web3 Personas and the Fraud Detector documentation.

The Data Moat: Why Token Audit Cannot Be Replicated

Token Audit is built on three proprietary data assets accumulated over years of continuous operation. A competitor starting today cannot purchase these assets, compress the time required to build them, or replicate them from publicly available sources alone. Each one directly enables detection capabilities that require the asset to exist before the analysis can run – meaning the gap between ChainAware and any new entrant widens over time rather than narrowing.

20M+ Wallet Personas: The Behavioral Trust Score Foundation

Every Token Audit includes a creator behavioral Trust Score and LP provider Trust Scores – signals that no competing token scanner offers. These scores draw on ChainAware’s database of more than 20 million wallet behavioral profiles accumulated across 8 blockchains. Each profile represents a complete behavioral fingerprint: transaction history, timing patterns, counterparty networks, protocol diversity, AML exposure, and dozens of derived features trained against confirmed fraud outcomes. The result is 98% fraud prediction accuracy on held-out test data.

This persona depth is what makes the behavioral layer meaningful. A deployer whose previous contracts ended in rug pulls carries that history as a permanent behavioral signal – regardless of how clean the new contract code looks. Without the 20M+ persona database, the behavioral Trust Score would be a near-zero confidence interval. Building that database required years of continuous on-chain data collection and iterative retraining against real-world fraud cases. A new entrant cannot compress that timeline. Furthermore, the model retrains continuously on new confirmed fraud cases – meaning the behavioral edge compounds as ChainAware observes more fraud patterns than any competitor accumulating data from a cold start.

One Year of On-Chain Pair History: The Criminal Record Database

Token Audit’s creator Trust Score cross-references the token deployer’s wallet address against ChainAware’s database of confirmed rug pull and honeypot operators – a database built from more than a year of continuous monitoring of liquidity pair creation and removal events across PancakeSwap, Uniswap, and other major DEX venues. This database records which wallet addresses created pools that subsequently exhibited rug pull patterns, and which wallet addresses previously deployed honeypot token contracts.

This is the data asset that catches the serial scammer deploying a new token after previous campaigns. The rug puller of Q4 2025 is registered as a known criminal in ChainAware’s pair history database. When they deploy a new token in Q1 2026, Token Audit flags the creator wallet immediately – regardless of how clean the new contract code appears. No competitor runs this check because no competitor maintains a paired rug pull database cross-referenced against token deployer wallets. Building it retroactively is also impossible: identifying fraud outcomes requires the passage of time to observe liquidity removal patterns after the fact. The database is a one-year head start that cannot be bought or downloaded. For the data behind this detection layer, see our Rug Pull Tracker report.

Deep Code Analysis Infrastructure: The Semantic Engine Behind 127 Checks

The analysis modules that produce Token Audit’s unique findings – approve call graph analysis, transfer conservation invariants, phantom balance detection, permit correctness checking, and reentrancy analysis – all depend on a semantic code analysis infrastructure built specifically for EVM token analysis. It handles Solidity’s inheritance chains, proxy delegation patterns, assembly blocks within Solidity functions, and the non-standard token architectures (reflection, rebasing, ERC-4626 vault tokens) that cause false positives in naive static analysis tools.

Building this infrastructure required years of engineering investment. Every EVM edge case – from DELEGATECALL chains that must be traced across contract boundaries, to assembly-level balance manipulation that bypasses Solidity’s type system, to the layered transfer delegation patterns used by professional honeypot developers – required specific detection logic designed from first principles. The result is a scanner that runs 127 checks in a median of 11.3 seconds across any EVM-compatible contract. That combination of depth and speed is what enables the unique findings in this study that no competitor detects. A new entrant replicating this infrastructure from scratch would need years of engineering time and a corpus of real fraud contracts to validate against – both of which ChainAware has already invested. For the competitive context, see our Forensic vs AI-Powered Blockchain Analysis guide.

Why the Moat Compounds

Each of these three assets improves as it grows. More wallet personas means better fraud prediction precision on creator behavioral scores. More pair history means more confirmed criminal operator wallets in the cross-reference database. More contracts analyzed means more edge cases handled correctly in the deep code analysis infrastructure. A competitor starting today with identical engineering resources would still need years to reach ChainAware’s current capability level – and by then, ChainAware’s data assets would be proportionally larger still. The advantage is a trajectory, not a snapshot.

What Does a CLEAN Token Look Like?

2,436 tokens in this dataset – 18.7% – received a CLEAN verdict. Understanding what they have in common is as instructive as understanding what HIGH RISK tokens share.

Notably, zero CLEAN tokens have an uncapped mint function. Every CLEAN token either has no mint capability at all, or has a mint function with an immutable, verifiable on-chain cap. This single characteristic is the strongest predictor of a clean verdict – more consistent than any other single check in the dataset.

Additionally, CLEAN tokens overwhelmingly have verified source code. Their LP is either locked in a recognized locker (PinkLock, UniCrypt, Team Finance), burned to a dead address, or the project has explicitly structured treasury management differently with transparent on-chain documentation. Their ownership model is either renounced, controlled by a multisig with public signers, or timelocked. The transfer function has no assembly in its call graph, no external calls, and emits exactly the events ERC-20 requires – nothing more, nothing less. For the complete CLEAN verdict criteria, see the Token Audit Verdict Methodology.

Implications for Investors, Platforms, and Builders

For Individual Investors

The core finding of this study is that market capitalization rank is not a security signal. Tokens in the CoinGecko top 10,000 are 55.2% high risk and 1% confirmed honeypot. Before committing capital to any token, check three things specifically: whether the LP is locked, whether the mint function has an enforceable cap, and whether the contract is upgradeable by a single EOA. ChainAware Token Audit checks all three – and 124 other things – in under 60 seconds, free, without requiring a wallet connection. For how to interpret Token Audit results, see the Token Audit Investor Guide.

For DeFi Platforms and DEX Aggregators

Platforms that surface token information currently rely almost entirely on GoPlus for token security data. This study demonstrates that GoPlus-equivalent analysis leaves substantial risk categories completely undetected. Embedding Token Audit results at the listing or interaction point gives users substantially more protection than any current alternative. The REST API and MCP integration return full structured results including per-finding boolean flags, per-module risk scores, and a human-readable verdict. For technical integration details, see the Token Audit API documentation and the MCP Integration guide.

For Token Builders

The 18.7% CLEAN rate in this study is not a verdict on intent – most high-risk findings reflect architectural patterns that developers adopted without understanding their security implications. Token Audit runs in full against any deployed contract, returning specific findings with remediation guidance for each. Running Token Audit costs nothing and takes 60 seconds. It identifies every architectural risk that investors, security researchers, and automated tools will find after deployment – and gives developers the opportunity to fix them first. For how to use Token Audit in a pre-deployment security review, see the Pre-Deployment Checklist.

Pausability: 5% of Tokens Can Freeze All Trading Right Now

This study found 648 tokens – 5.0% of all audited contracts – where the mint function continues operating even when the token is paused (INV_PA5_MINT_NOT_PAUSED). An admin can pause all investor transfers while continuing to mint new tokens into their own wallet – simultaneously trapping existing holders and diluting their positions.

The most sophisticated pausability vulnerability – INV_PA4_ASYMMETRIC_PAUSE – blocks sells (transferFrom) while allowing buys (transfer). Honeypot.is tests a sell by calling transfer – the same function that is allowed in the asymmetric pause scenario – so it returns CLEAN for a token that is functionally a honeypot. ChainAware detects the asymmetric pattern by analyzing whether the pause condition applies differently to transfer versus transferFrom.

The 22 tokens currently paused represent an immediate alert for any investor holding these tokens. Token Audit calls paused() directly on each pausable contract to determine whether the pause is currently active – those 22 tokens are actively frozen right now. See the Pausability Verification documentation.

Supply Analysis: Hidden Minting and Supply Manipulation at Scale

Finding INV_S1_HIDDEN_MINT appears in 822 tokens – 6.3% of the dataset. Hidden mint detects functions that inflate the total token supply through mechanisms not labeled as mint() or _mint(). Because they bypass the standard _mint internal function, simple checks that scan for mint selectors in the contract ABI will miss them entirely. ChainAware traces every function that modifies the total supply variable regardless of name. See the Supply Verification documentation.

Finding INV_S4_FAKE_BURN appears in 318 tokens – 2.4%. A fake burn transfers to address(0) but does not reduce totalSupply(). Tokens marketed as deflationary based on burn history may be inflating their apparent scarcity. Additionally, 216 tokens show deployer concentration at 100% of circulating supply (INV_S6_DEPLOYER_100PCT) – the optimal setup for a coordinated pump-and-dump.

Audit Performance: 15 Seconds Average, 98.4% Source Verified

The median audit completes in 11.3 seconds – well within the threshold for interactive use cases like a DEX listing flow or a wallet pre-transaction security check. Only 9 audits across the entire 12,998-audit dataset exceeded 120 seconds – representing 0.07% of cases and well within operational tolerances for any integration scenario. 98.4% of tokens in this dataset have verified source code. For unverified contracts, Token Audit operates in bytecode analysis mode – the Liquidity module, Simulation module, and Behavioral Trust Score all operate on bytecode and on-chain state rather than source code. For details see the Unverified Contract Analysis documentation.

Conclusion: The Token Security Gap Is Real

This study set out to answer a simple question: how safe are the tokens that most investors actually hold? The answer – 55.2% high risk, 1% confirmed honeypot, 13.2% upgradeable proxy, 25.7% unlocked LP – is more alarming than most observers expected from the top 10,000 by market capitalization. These are not obscure tokens in forgotten DEX pools. Many appear in mainstream wallet apps, on regulated exchange listings, and in institutional portfolio allocations.

Furthermore, the findings that established tools miss are precisely the ones that matter most for sophisticated attacks. GoPlus, TokenSniffer, and CertiK Skynet catch the obvious patterns. Consequently, professional scam operators have adapted: they write clean-looking code that passes all three tools, then execute through vectors those tools cannot see. The approve transitive attack, the phantom balance exploit, the permit preload, the asymmetric pause – all of these appear in this dataset, and all of them are invisible to current market-standard scanners.

ChainAware Token Audit changes this equation. It brings institutional-grade deep code analysis to every token, automatically, for free, in under 60 seconds. Combined with simulation analysis, behavioral Trust Scores, and proxy upgrade authority classification, Token Audit produces a security profile that exceeds what any competing automated tool provides. According to FATF’s Virtual Assets Recommendations, real-time token screening is becoming a compliance requirement for virtual asset service providers globally. Token Audit is live today – test any contract free, no signup, no wallet connection. For enterprise integration, book a technical walkthrough below.

Frequently Asked Questions

What is a token audit?

A token audit is an automated or manual security review of a cryptocurrency token’s smart contract. A manual token audit performed by firms like CertiK or Hacken costs $5,000 to $150,000 and takes one to four weeks. ChainAware Token Audit performs automated analysis across 127 checks in under 60 seconds at no cost for individual queries.

How is ChainAware Token Audit different from GoPlus?

GoPlus Security runs approximately 717 million monthly API calls. Its detection is rule-based – it checks for known dangerous patterns at the interface level. ChainAware Token Audit adds semantic analysis via deep code analysis, which traces the complete execution paths of transfer(), approve(), and related functions to find vulnerabilities hidden deep in internal call chains. ChainAware also adds reentrancy detection, permit correctness analysis, supply consistency checking, and behavioral Trust Scores – none of which GoPlus offers.

What does HIGH RISK mean in practice?

HIGH RISK means the token contract contains one or more mechanisms that a malicious or compromised admin could use to harm investors – an uncapped mint function, unlocked LP, EOA-controlled proxy, or admin with no timelock. HIGH RISK does not mean the token is currently being exploited – it means the architectural risk exists and investors should evaluate it consciously before committing capital.

How does the simulation analysis work?

Token Audit’s simulation module forks the relevant blockchain at the current block using an Anvil instance, then executes real buy and sell transactions inside the fork. This catches dynamic honeypot behavior that static analysis cannot detect: tokens where sells revert, tokens where the effective sell tax differs from the declared sell tax, and tokens where token conservation fails. See Simulation Module documentation.

Which chains does Token Audit cover?

Token Audit currently supports seven chains: Ethereum, BNB Smart Chain, Base, Polygon, Arbitrum, Optimism, and Avalanche. The analysis architecture is chain-agnostic at the contract level: deep code analysis, ownership tracing, and supply verification work identically across EVM-compatible chains. The 10,000-token study referenced throughout this article was run before Avalanche support was added, which is why Avalanche does not appear in the dataset tables above.

What does the creator behavioral Trust Score measure?

The creator Trust Score evaluates the on-chain behavioral history of the wallet that deployed the token contract. It draws on ChainAware’s database of 20 million+ wallet behavioral profiles to assess whether the deployer has patterns consistent with fraud operators – prior rug pulls, coordination with known scam wallet clusters, funding source characteristics, and behavioral sequences associated with professional exit scam operations. See Fraud Detector documentation.

Can Token Audit be used pre-deployment?

Token Audit requires a deployed mainnet contract address – it analyzes live on-chain state alongside contract code. For pre-deployment security review, ChainAware recommends running deep code analysis directly against the contract source, then running Token Audit immediately after mainnet deployment. According to the Smart Contract Weakness Classification Registry, the majority of token vulnerabilities are deterministic at the code level and identifiable through static analysis shortly after deployment.

Sources: Chainalysis Crypto Crime Report · OWASP Smart Contract Top 10 · Smart Contract Weakness Classification Registry · EIP-2612: Permit Extension for ERC-20

Related ChainAware Reading: Best Rug Pull Detection Tools 2026 · DeFi Compliance Tools Comparison · KYT and AML Guide for DeFi · Web3 Wallet Auditing Providers 2026 · What Are Web3 Personas · Prediction MCP for AI Agents · The Web3 Agentic Economy · Agent Trust Score: On-Chain Trust Scoring for ERC-8004

The post ChainAware Token Audit Launched – We Tested 10,000 CoinGecko Tokens. Here Are the Results. first appeared on ChainAware.ai.

ChainAware was named in CB Insights’ AI Fraud Prevention Market Map alongside Chainalysis, Elliptic, and TRM Labs – and remains the only Web3 AI token across all 200+ companies in that list. The 32 sub-agents documented here are the operational engine behind that recognition: real, deployed tools that DeFi protocols, compliance teams, launchpads, DAOs, and AI agent developers use in production today. Every agent is open-source, MIT-licensed, and available at github.com/ChainAware/behavioral-prediction-mcp .

This article classifies all 32 agents into two functional categories – Fraud Tech and Growth Tech – and for each agent provides a precise description, concrete use case, and the specific trigger conditions that signal when a team needs it. Use this as your reference guide for selecting, combining, and deploying ChainAware’s agent suite.

In This Article

• Two Categories – Fraud Tech and Growth Tech
• The Complete Classification Table – All 32 Agents
• Fraud Tech Agents – 17 Agents, Complete Reference
• Growth Tech Agents – 15 Agents, Complete Reference
• How Agents Compose Into Pipelines
• Getting Started – Integration in Three Steps
• Frequently Asked Questions

Two Categories – Fraud Tech and Growth Tech

ChainAware’s 32 agents divide into two functional categories that reflect the platform’s core thesis: the same behavioral data that prevents fraud also drives growth. Both categories draw from the same underlying Prediction MCP tools and the same 20M+ wallet persona database. The distinction lies in what question each agent answers and what action it enables.

Fraud Tech agents answer: “Can we trust this wallet, contract, token, or transaction?” They protect protocols from losses, enforce AML compliance, prevent Sybil attacks, and screen counterparties before execution. Consequently, Fraud Tech agents operate primarily at the gate – before onboarding, before transactions, before token distributions, before listing decisions. Their outputs are verdicts: allow, block, flag, reject, or escalate.

Growth Tech agents answer: “Now that we know this wallet is legitimate, how do we convert it, retain it, and grow it?” They turn behavioral intelligence into personalized acquisition, onboarding, conversion, and retention decisions. Moreover, Growth Tech agents operate primarily post-gate – after a wallet passes initial screening, they determine how to engage it most effectively. Their outputs are recommendations: which product to surface, which message to send, which onboarding flow to show, which upsell to offer.

Furthermore, both categories share a fraud gate: every Growth Tech agent checks probabilityFraud before generating any recommendation and blocks output for high-risk wallets. This means the categories are not sequential stages but parallel layers – fraud protection runs continuously across every growth decision. For the foundational framework explaining why behavioral intelligence is essential for both fraud prevention and growth, see our Web3 Behavioral User Analytics guide .

The Complete Classification Table – All 32 Agents

The table below lists every agent with its category, primary MCP tool, supported networks, and core function. Agents are sorted by category, then by specificity – from broad-purpose agents to narrow specialists. Use this as your quick-reference lookup before reading the detailed descriptions that follow.

#	Agent	Category	Primary Tool	Networks	Core Function
1	fraud-detector	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	Wallet fraud probability (98% accuracy) + 19 AML forensic flags
2	rug-pull-detector	Fraud Tech	predictive_rug_pull	ETH BNB BASE HAQQ	90.1% rug pull prediction – contract + deployer behavioral analysis
3	aml-scorer	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	AML score (0-100) with full forensic flag breakdown
4	trust-scorer	Fraud Tech	predictive_fraud	ETH BNB POLYGON TON BASE TRON HAQQ	Trust score (0.00-1.00) = 1 − fraud probability. Composable building block
5	sybil-detector	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch Sybil detection – wallet farms, coordinated attacks, proxy voting fraud
6	governance-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	DAO voter tier (Core Contributor → Disqualified) + voting weight multiplier
7	counterparty-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Pre-transaction Safe / Caution / Block verdict in a single API call
8	compliance-screener	Fraud Tech	Orchestrator	Multi-chain via sub-agents	MiCA-aligned PASS / EDD / REJECT with full documented evidence trail
9	transaction-monitor	Fraud Tech	predictive_behaviour + predictive_rug_pull	ETH BNB BASE HAQQ SOL + fallback	Real-time ALLOW / FLAG / HOLD / BLOCK for autonomous agent pipelines
10	token-launch-auditor	Fraud Tech	predictive_rug_pull + predictive_fraud	ETH BNB BASE HAQQ	Launchpad listing audit → APPROVED / CONDITIONAL / REJECTED + safety badge
11	airdrop-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch airdrop eligibility – filters bots, ranks eligible wallets by reputation
12	rwa-investor-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	RWA investor suitability → QUALIFIED / CONDITIONAL / REFER_TO_KYC / DISQUALIFIED
13	gamefi-screener	Fraud Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	P2E bot farm and multi-account cheater detection + player tier classification
14	credit-scorer	Fraud Tech	credit_score	ETH	Crypto credit score (1-9) combining fraud probability + social graph analysis
15	lending-risk-assessor	Fraud Tech	predictive_behaviour + credit_score	ETH BNB BASE HAQQ SOL	Borrower risk grade (A-F) + recommended collateral ratio + interest rate tier
16	portfolio-risk-advisor	Fraud Tech	predictive_rug_pull + token_rank_single	ETH BNB BASE HAQQ	Portfolio rug pull scan → grade A-F + prioritized exit/reduce plan
17	agent-screener	Fraud Tech	predictive_fraud + predictive_behaviour + predictive_rug_pull	ETH BNB BASE HAQQ SOL + fallback	AI agent trust score (0-10) screening agent wallet + feeder wallet
18	wallet-auditor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Complete 22-dimension Web3 Persona – fraud + behavioral + personalization
19	reputation-scorer	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Reputation score (0-1000) = experience × risk_capability × (1 − fraud)
20	wallet-ranker	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Global wallet rank from experience, total points, age, transaction count
21	whale-detector	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Whale tier (Mega / Whale / Emerging) + Active/Dormant status + domain
22	ltv-estimator	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	12-month revenue potential (USD range) from behavioral + risk signals
23	lead-scorer	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Lead score (0-100) + Hot/Warm/Cold/Dead + recommended outreach angle
24	wallet-marketer	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Hyper-personalized marketing message (max 20 words) from on-chain signals
25	platform-greeter	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Platform-specific welcome message (max 35 words) – different per platform
26	onboarding-router	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Onboarding flow decision – Beginner / Intermediate / Skip from real experience
27	defi-advisor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Personalized DeFi product recommendations (3 tiers) by experience + risk
28	upsell-advisor	Growth Tech	predictive_behaviour	ETH BNB BASE HAQQ SOL	Upgrade readiness (0-100) + next product + trigger event + conversion probability
29	cohort-analyzer	Growth Tech	predictive_behaviour + predictive_fraud	ETH BNB BASE HAQQ SOL + fallback	Batch behavioral cohort segmentation – 8 cohorts + per-cohort strategy
30	token-ranker	Growth Tech	token_rank_list	ETH BNB BASE SOL	Token discovery by community strength – AI / RWA / DeFi / DeFAI / DePIN
31	token-analyzer	Growth Tech	token_rank_single + predictive_fraud	ETH BNB BASE SOL	Single-token deep-dive: community rank + top holder profiles + fraud screening
32	marketing-director	Growth Tech	Orchestrator (7 specialist agents)	All networks via sub-agents	Full-cycle campaign orchestrator → complete Marketing Campaign Brief

Fraud Tech Agents – 17 Agents, Complete Reference

ChainAware’s Fraud Tech agents protect Web3 protocols from the full spectrum of on-chain threats: wallet fraud, rug pulls, money laundering, Sybil attacks, governance manipulation, P2E cheating, and fraudulent AI agents. Together, they cover every point in the protocol lifecycle where malicious actors attempt to extract value – from the moment a wallet first connects to the moment a transaction executes. According to FATF’s Virtual Assets Recommendations , the compliance requirements for crypto asset service providers now demand pre-execution risk assessment that legacy forensic tools were never designed to deliver. ChainAware’s Fraud Tech agents fill that gap with predictive behavioral intelligence rather than reactive forensic lookup.

Moreover, these agents share a critical structural advantage over traditional blockchain forensics: they analyze behavioral patterns across 20M+ wallet personas rather than matching against static blocklists. Professional fraud operators deliberately evade blocklist-based tools by using fresh wallets and clean contract code. They cannot, however, mask their behavioral fingerprint – the pattern of on-chain activity that identifies an operator regardless of which specific address they use today. This is why ChainAware achieves 98% fraud detection accuracy on ETH where forensic tools frequently miss sophisticated operators. For the complete technical comparison, see our Forensic vs AI-Powered Analytics guide .

1. chainaware-fraud-detector

The flagship fraud detection agent calls predictive_fraud on any wallet address and returns a fraud probability score, wallet status (Not Fraud / Fraud / New Address), OFAC sanctions check, and 19 AML forensic flags covering mixers, darknet transactions, phishing wallets, fake token creation, money laundering patterns, cybercrime associations, and more. Accuracy reaches 98% on ETH and 96% on BNB, backtested against CryptoScamDB – the largest publicly available database of documented crypto fraud incidents. Coverage spans 7 networks: ETH, BNB, POLYGON, TON, BASE, TRON, and HAQQ.

Use Case: A DeFi lending protocol screens every wallet requesting a loan before processing the application. The team integrates chainaware-fraud-detector into its onboarding API – each new wallet receives a fraud probability score and forensic flag check in under one second. Wallets scoring above 0.70 are automatically declined. Wallets between 0.40 and 0.70 route to enhanced due diligence. Wallets below 0.20 pass to the standard lending flow. The same agent works equally well for exchange KYC pre-screening, NFT allowlist vetting, and airdrop participant verification.

When Is It Required: Deploy chainaware-fraud-detector whenever a protocol accepts wallet connections from unknown participants – particularly before any value transfer, credit extension, or whitelist grant. It is specifically required when a protocol falls under MiCA, AML5D, or equivalent regulation that mandates pre-onboarding risk assessment. Additionally, it is required before running any Growth Tech agent on a wallet – the fraud gate in chainaware-wallet-marketer and chainaware-ltv-estimator calls this agent’s underlying tool before generating any recommendation. For the complete implementation methodology, see our Fraud Detector guide .

2. chainaware-rug-pull-detector

Analyzes smart contracts, liquidity pools, and token launches for rug pull risk before any capital is deployed. The agent runs predictive_rug_pull on the contract address and predictive_fraud on the deployer wallet, combining both into a unified verdict. Critically, the deployer fraud score can escalate the overall verdict by one tier – a contract scoring 0.35 (Medium risk) paired with a deployer scoring 0.72 (High risk) produces a combined High Risk verdict. This escalation catches the most dangerous category of rug pulls: professionally deployed clean contracts by operators with documented fraud histories on other wallets. Accuracy on the PancakeSwap V2 dataset reaches 90.1%, covering $569M in documented rug pull losses from weeks 1-20 of 2026. Networks supported: ETH, BNB, BASE, HAQQ.

Use Case: A DEX launchpad reviews 50 new token submissions per week. Without automated screening, each review requires a developer to manually inspect contract code and trace the deployer wallet – a process taking 30-60 minutes per token. With chainaware-rug-pull-detector, the launchpad runs all 50 contracts in batch mode and receives a ranked risk table in minutes. Contracts scoring above 0.80 are automatically rejected. Contracts between 0.50 and 0.80 require manual review with specific red flags already identified. Contracts below 0.20 proceed to standard listing.

When Is It Required: Use chainaware-rug-pull-detector before listing any token on a DEX, before depositing LP into any new pool, before investing in any IDO or pre-sale, and before any yield vault strategy deploys capital into a new protocol. It is specifically required for launchpad teams that need a standardized, reproducible audit process rather than ad hoc developer reviews. It pairs with chainaware-token-launch-auditor when a full public-facing audit report with a safety badge is needed. For the detailed comparison against GoPlus, Token Sniffer, and Honeypot.is, see our Rug Pull Detection Tools guide .

3. chainaware-aml-scorer

Calculates a structured AML score (0-100) using a two-branch logic that separates forensic compliance from probabilistic fraud risk. If any forensic flag is present – mixer usage, sanctioned entity association, stolen funds link, darknet transaction, ransomware wallet interaction – the AML score is 0 regardless of the fraud probability score. This hard-zero rule reflects regulatory reality: a forensic flag requires human review and escalation regardless of the overall risk probability. When forensics are clean, the AML score equals (1 − probabilityFraud) × 100, providing a continuous risk gradient for compliance tiering. The agent returns the complete forensic breakdown alongside the score, producing output that is audit-ready for regulatory review under MiCA and equivalent frameworks.

Use Case: A crypto exchange onboards 500 new wallets per day and must document AML screening decisions for regulatory reporting. Previously, the compliance team ran manual checks on wallets flagged by a basic blocklist – a process that missed sophisticated operators and created a documentation backlog. With chainaware-aml-scorer, every onboarding wallet receives an automated AML report in under one second. Wallets scoring 0 (forensic flag detected) escalate to the compliance team with the specific flags identified. Wallets scoring 71-100 receive automated approval documentation. Wallets in the 41-70 range trigger enhanced due diligence with a specific set of additional checks, creating a complete and auditable compliance trail for every onboarded wallet.

When Is It Required: Deploy chainaware-aml-scorer for any platform falling under AML/CFT regulatory requirements – exchanges, OTC desks, lending protocols, and any DeFi platform accepting significant TVL from institutional wallets. It is also required when chainaware-compliance-screener is the orchestrating agent, since compliance-screener calls aml-scorer as one component of its structured MiCA-aligned report. See our MiCA Compliance guide for the full regulatory compliance stack.

4. chainaware-trust-scorer

Returns a single trust score using one formula: Trust Score = 1 − fraud_probability. The output ranges from 0.00 (confirmed fraud) to 1.00 (zero fraud probability). Designed as a composable building block rather than a standalone product, trust-scorer feeds into other calculations across the agent suite: reputation score uses it as the base fraud penalty, AML score uses it as the clean-forensics branch, governance vote weighting multiplies by it, and marketing campaign gates use it as a minimum threshold before message generation. Covers 7 networks via predictive_fraud. Response time is sub-100ms by design, making it the fastest agent in the suite.

Use Case: A developer building a custom reputation system for their DeFi protocol needs a standardized trust signal to combine with their own on-chain activity metrics. Rather than building a fraud detection model from scratch, they integrate chainaware-trust-scorer as the fraud component and combine it with their own activity score. The resulting composite score inherits ChainAware’s 98% fraud accuracy while adding protocol-specific activity signals that ChainAware’s general model does not capture. The trust score’s mathematical cleanliness – it is simply the complement of fraud probability – makes it easy to incorporate into any scoring formula.

When Is It Required: Use chainaware-trust-scorer whenever a custom scoring formula needs a standardized, high-accuracy fraud component – governance vote weighting, airdrop allocation, lending collateral ratios, and marketing campaign eligibility gates all benefit from incorporating the trust score as a fraud signal. It is the recommended starting point for teams building composite scores rather than using a pre-built agent, since its output is mathematically clean and directly interpretable.

5. chainaware-sybil-detector

Batch-screens wallet lists for Sybil attacks, coordinated voting fraud, and wallet farm operations. Beyond individual wallet scoring, the agent applies four pattern detection rules across the full submitted set: a cluster flag triggers when 10%+ of wallets share experience scores within ±0.2 points and were created in the same approximate period – the signature of a coordinated wallet farm. A fraud concentration flag triggers when 20%+ of voters show fraud probability above 0.25. A new wallet surge flag triggers when 30%+ of wallets have experience below 1.5. A uniform risk profile flag triggers when 60%+ share identical behavioral categories, indicating coordination rather than organic community diversity. Each wallet is classified as ELIGIBLE, REVIEW, or EXCLUDE, and the cleaned voter list is ready for Snapshot or on-chain governance integration.

Use Case: A DAO preparing a governance vote on a $2M treasury allocation notices unusual activity: 400 new wallets registered in the 48 hours before the vote, all with minimal transaction history. Running chainaware-sybil-detector on the full voter list identifies 312 of those 400 wallets as part of a coordinated new-wallet cluster, disqualifying them from the vote. The attack is neutralized before it reaches quorum. The cleaned voter list shows genuine community support from 89 ELIGIBLE voters, and the vote proceeds with integrity intact.

When Is It Required: Run chainaware-sybil-detector before any governance vote controlling significant treasury funds, parameter changes, or upgrade authority. It is specifically required before Snapshot votes for DAOs with public token distribution, before on-chain governance proposals reaching quorum thresholds, and before any delegation validation process where vote weight can be amplified through coordinated proxy delegation. For the complete governance protection framework, see our Governance Screeners guide .

6. chainaware-governance-screener

DAO voter screening with four-tier classification and voting weight calculation. The agent assigns each wallet to one of five tiers: Core Contributor (experience ≥ 8, fraud ≤ 0.10, protocols ≥ 5 → 2.0× multiplier), Active Member (experience ≥ 5, fraud ≤ 0.25, protocols ≥ 2 → 1.5×), Participant (experience ≥ 2, fraud ≤ 0.40 → 1.0×), Observer (new address or experience < 2 with low fraud → 0.5×), and Disqualified (fraud gate fails → 0.0×). Within each tier, the multiplier adjusts downward for elevated fraud probability. Three governance models are supported: token-weighted, reputation-weighted (ChainAware reputation score as direct weight), and quadratic (multiplier applies to square root of token balance).

Use Case: A DeFi protocol wants to implement reputation-weighted governance to counteract plutocracy – the tendency of token-weighted systems to concentrate governance power in the largest holders regardless of protocol engagement. Using chainaware-governance-screener in reputation-weighted mode, every voter’s influence is determined by behavioral quality rather than token balance alone. A Core Contributor holding 1,000 tokens has more governance weight than a dormant whale holding 100,000 tokens but showing no protocol engagement. The result is governance that rewards genuine contributors rather than passive large holders.

When Is It Required: Deploy chainaware-governance-screener for any DAO that needs to validate voter quality before a proposal goes live. It is particularly required for protocols implementing reputation-weighted or quadratic voting models, for DAOs with public token distributions vulnerable to Sybil accumulation, and for any governance system where a single bad-faith actor could acquire enough voting power to pass a malicious proposal. It works alongside chainaware-sybil-detector – the Sybil detector identifies coordinated wallet farms, while governance-screener classifies remaining legitimate voters by quality tier.

7. chainaware-counterparty-screener

Pre-transaction safety agent optimized for minimum latency and maximum decisiveness. A single predictive_behaviour call retrieves both the fraud probability and the behavioral context needed for ambiguous cases – eliminating the two-call pattern that adds latency to pre-transaction flows. The verdict logic applies decisive rules first (confirmed fraud or forensic flag → immediate Block; fraud probability ≤ 0.15 → immediate Safe) and contextual rules only for the 0.16-0.70 range. Transaction-type context adjusts the risk assessment: approve actions receive a 1.3× risk multiplier, bridge and liquidity actions 1.2×, stake actions 0.9×. Compact mode returns a single line for autonomous agent pipelines.

Use Case: A DeFi aggregator routes user transactions across multiple protocols and counterparties. Before executing any multi-hop route, the aggregator’s AI agent calls chainaware-counterparty-screener on every intermediate counterparty address. A Block verdict causes the agent to find an alternative route avoiding the flagged address. A Caution verdict triggers additional monitoring for the transaction. A Safe verdict allows execution to proceed normally. The entire screening adds under 200ms to the routing decision – negligible for a user experience that already involves multi-second blockchain confirmation times.

When Is It Required: Use chainaware-counterparty-screener immediately before signing any transaction with an unknown counterparty – particularly token approvals (highest risk action type), LP deposits (contract risk), bridge transactions (irreversible cross-chain exposure), and high-value transfers. For autonomous AI agents executing transactions without human review, this agent provides the fraud gate that substitutes for human judgment. It pairs naturally with chainaware-transaction-monitor: counterparty-screener handles the pre-transaction check on specific addresses, while transaction-monitor handles real-time pipeline risk scoring across sender, receiver, and contract simultaneously.

8. chainaware-compliance-screener

The most comprehensive compliance agent in the suite – a MiCA-aligned orchestrator sequencing AML scoring, fraud detection, and transaction risk assessment into a single structured Compliance Report with a three-tier verdict: PASS, ENHANCED DUE DILIGENCE, or REJECT. Unlike the individual specialist agents, compliance-screener is specifically designed to produce documentation: every signal, every flag, every threshold applied is recorded in the output, creating an audit trail that compliance officers can present to regulators. The verdict structure mirrors MiCA’s layered compliance approach – PASS wallets proceed normally, EDD wallets receive additional checks before service, REJECT wallets are declined with specific reasons documented.

Use Case: A crypto asset service provider (CASP) operating under MiCA needs to document its compliance process for every customer onboarding. Manual KYC combined with blockchain forensics produces reports taking hours per customer and lacking standardization. With chainaware-compliance-screener, every onboarded wallet receives an automated, structured Compliance Report in under 5 seconds – covering sanctions screening, AML forensic flags, behavioral fraud risk, and transaction pattern analysis. The report format is consistent across all wallets, making regulatory reporting systematic rather than ad hoc. EDD cases are automatically flagged with the specific signals that triggered the enhanced review requirement.

When Is It Required: Deploy chainaware-compliance-screener for any platform regulated under MiCA, AML5D, FinCEN guidance, or equivalent frameworks requiring documented pre-onboarding risk assessment. It is specifically required when a compliance team needs to demonstrate to regulators that their screening process is systematic, documented, and applied consistently – not selectively or manually. The agent is also the right choice for institutional DeFi platforms serving accredited investors where documented compliance is a prerequisite for institutional capital access. For the complete regulatory compliance cost comparison, see our MiCA Compliance guide .

9. chainaware-transaction-monitor

Real-time transaction risk scoring designed for autonomous AI agent pipelines rather than human compliance review. The agent screens sender, receiver, and contract address simultaneously, computes a composite risk score (0-100) using weighted contributions from each address, applies action-type multipliers (approve 1.3×, bridge and liquidity 1.2×, stake 0.9×, unknown 1.1×), and returns a machine-actionable ALLOW / FLAG / HOLD / BLOCK signal. Override rules immediately produce a BLOCK regardless of composite score whenever sender or receiver carries confirmed fraud status or any AML forensic flag. Compact mode returns a single-line signal for mempool monitoring and high-frequency agent pipelines where sub-50ms response is required.

Use Case: A DeFi trading bot executes 200+ transactions per day across multiple protocols. Without transaction monitoring, the bot has no way to detect when it is being routed through a fraudulent intermediary or interacting with a compromised contract. With chainaware-transaction-monitor as a pre-execution hook, every transaction is screened in under 100ms before signing. BLOCK signals cause the bot to abort the transaction and find an alternative path. FLAG signals execute but generate a compliance log entry for review. Over a 30-day period, the monitoring prevents the bot from executing 14 transactions with BLOCK-level counterparties – including two interactions with wallet addresses later confirmed as hack-related by blockchain investigators.

When Is It Required: Deploy chainaware-transaction-monitor for any autonomous AI agent executing blockchain transactions without per-transaction human approval. This specifically includes DeFi trading bots, yield optimization agents, automated treasury management systems, and any AI agent operating under the emerging ERC-8004 standard for on-chain agent identity. It is also required for any protocol needing ongoing post-onboarding transaction screening – complementing chainaware-fraud-detector (which handles one-time onboarding checks) with continuous monitoring of user activity. For the complete integration guide, see our Transaction Monitoring guide .

10. chainaware-token-launch-auditor

Launchpad listing audit agent combining rug pull detection on the contract with full fraud and behavioral analysis on the deployer wallet. The output includes a composite Launch Safety Score, a public-facing safety badge suitable for embedding on listing pages, and specific conditions the launchpad should impose – mandatory LP lock periods, restricted admin key permissions, or vesting schedule requirements. The three-tier verdict (APPROVED, CONDITIONAL, REJECTED) gives launchpad teams a standardized decision framework they can communicate publicly to investors. CONDITIONAL listings include explicit conditions that, if met, convert the listing to APPROVED.

Use Case: An IDO launchpad receives a new project application for a DeFi token on BNB. The applying team has a polished website, a detailed whitepaper, and a professionally written smart contract that passes standard code review. However, chainaware-token-launch-auditor detects that the deployer wallet has previously deployed three tokens on ETH, all of which experienced LP withdrawal events within 72 hours of launch – a behavioral signature of serial rug pull operations. The contract score is 0.28 (Medium) but the deployer score is 0.81 (Critical), producing a REJECTED verdict. The launchpad declines the listing. Three weeks later, the same team launches the token on an unscreened DEX, where it rugs within 36 hours.

When Is It Required: Run chainaware-token-launch-auditor before approving any token listing on a launchpad or DEX maintaining listing standards. It is specifically required for platforms displaying a safety badge or endorsement alongside listed tokens – without auditor-backed evidence, any safety claim creates legal and reputational liability. The agent is also required for any accelerator or incubator program vetting projects before providing funding or platform access. It works as a pre-listing screening gate for token sale platforms where retail investors rely on the platform’s due diligence.

11. chainaware-airdrop-screener

Batch airdrop eligibility engine that filters fraud wallets, bots, and Sybil clusters from token distribution lists, then ranks eligible wallets by ChainAware’s reputation formula for merit-based allocation. Five disqualification rules apply in order: fraud probability above 0.70 → HIGH FRAUD disqualified; confirmed fraud status → CONFIRMED FRAUD disqualified; new address with fraud above 0.40 → SUSPICIOUS NEW disqualified; new address with zero experience and no categories → BOT/FRESH disqualified; any AML forensic flag → AML FLAG disqualified. Surviving wallets receive a reputation score calculated as (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability) and are assigned allocation multipliers from 0.5× (Low Score) to 4× (Elite). When a token budget is provided, the agent calculates exact per-wallet token allocations ready to plug into a Merkle tree contract.

Use Case: A DeFi protocol distributes 10 million tokens across 5,000 wallet addresses collected through a six-week quest campaign. Without screening, ChainAware’s analysis of similar campaigns finds that approximately 84% of campaign participants are ghost wallets – addresses with zero real engagement that bot operators control mechanically. Running chainaware-airdrop-screener on the 5,000 addresses disqualifies 3,420 as bots, fraud, or suspicious new wallets. The remaining 1,580 eligible wallets are ranked by reputation score and receive allocations scaled from 0.5× to 4× of the base amount. The protocol distributes tokens to genuine community members, avoids immediate sell pressure from farming wallets, and creates a foundation of quality token holders.

When Is It Required: Run chainaware-airdrop-screener before every token distribution event – regardless of campaign size. It is specifically required for distributions above 100,000 USD equivalent where bot farming has high economic incentive, for any distribution including vesting where recipient quality affects long-term token price stability, and for governance token airdrops where recipient quality directly affects the quality of future governance participation. The agent pairs naturally with chainaware-sybil-detector (which identifies coordination patterns before disqualification) and chainaware-reputation-scorer (which provides the ranking formula for tiered allocations).

12. chainaware-rwa-investor-screener

Real World Asset investor suitability screening assessing three dimensions simultaneously: AML/fraud compliance (40% weight), investor sophistication via on-chain experience score (35%), and risk profile alignment against the RWA’s declared risk tier (25%). The composite Suitability Score (0-100) maps to four tiers: QUALIFIED (full access, standard caps), CONDITIONAL (reduced cap, enhanced monitoring), REFER_TO_KYC (on-chain profile insufficient, route to manual KYC), and DISQUALIFIED (fraud gate, AML flag, or confirmed fraud). Recommended investment caps are tied to experience level within each tier – a QUALIFIED Sophisticated investor has no cap, while a QUALIFIED Intermediate investor caps at $25,000. Three RWA risk tiers define minimum experience thresholds: conservative (≥ 2.0), moderate (≥ 4.0), aggressive (≥ 6.5).

Use Case: A tokenized real estate platform onboards investors for a $50M moderate-risk RWA offering. Traditional KYC takes 3-5 days per investor. The platform needs to process 2,000 investor applications in a two-week window before the offering closes. Chainaware-rwa-investor-screener processes all 2,000 wallets in batch mode in under 10 minutes, classifying 1,240 as QUALIFIED, 380 as CONDITIONAL, 210 as REFER_TO_KYC, and 170 as DISQUALIFIED. The 170 disqualified wallets are excluded immediately. The 1,620 QUALIFIED and CONDITIONAL wallets complete automated onboarding in minutes – dramatically reducing compliance cost and time-to-investment for legitimate investors.

When Is It Required: Deploy chainaware-rwa-investor-screener for any tokenized asset platform needing automated investor suitability assessment. It is specifically required when traditional KYC throughput is insufficient for the number of investors the platform needs to process, when the regulatory framework requires documented suitability assessment rather than just AML screening, and when the platform offers products across multiple risk tiers requiring different investor qualification standards. It complements chainaware-compliance-screener (which handles AML compliance) by adding the investor sophistication and product suitability dimensions that pure AML screening does not cover.

13. chainaware-gamefi-screener

Play-to-Earn bot farm and multi-account cheater detection for Web3 games. The agent screens wallets connecting to a P2E platform for bot signatures (coordinated transaction timing, uniform behavioral patterns, zero genuine game interaction history), multi-account cheating (same operator controlling multiple wallets extracting parallel rewards), and reward abuse patterns (wallets appearing across multiple P2E reward events in behavioral coordination). Legitimate players are classified into experience tiers for matchmaking and receive P2E reward eligibility scores scaling allocations by behavioral quality. The fraud gate disqualifies wallets above 0.70 fraud probability regardless of game-specific behavior.

Use Case: A P2E game launches a tournament with $100,000 in prize pool rewards. Within 48 hours, 40% of tournament participants are identified as bot farms – coordinated wallet clusters playing mechanically to extract rewards without genuine gameplay. Chainaware-gamefi-screener deployed at tournament registration identifies the bot wallets before they accumulate rewards. The disqualified wallets are excluded. Remaining players are classified into tiers from Beginner to Expert and receive reward multipliers (0.5× to 4×) scaled to their on-chain gaming experience. Prize pool distribution shifts from bot-dominated to skill-correlated, improving tournament integrity and the genuine player community’s experience.

When Is It Required: Run chainaware-gamefi-screener at every P2E tournament registration, every in-game reward event, and every NFT loot drop in a play-to-earn context. It is specifically required for any P2E game with real economic value at stake – when rewards are worth more than the cost of running bots, bot farms appear without exception. The agent is also required for scholarship programs in P2E games, where scholarship managers need to verify that scholar wallets are controlled by genuine individual players rather than farming operations controlling multiple scholarship slots simultaneously.

14. chainaware-credit-scorer

Returns a crypto credit score from 1 to 9 using ChainAware’s credit_score tool, combining fraud probability with social graph analysis of the wallet’s transaction network. Score 9 is Prime (highest creditworthiness, best lending terms). Score 1 is Very High Risk (decline lending). Currently supported on ETH only, where social graph data density is highest. The credit score is the simplest borrower signal in the suite – designed specifically as a composable building block that chainaware-lending-risk-assessor combines with experience score and risk appetite to produce a full Borrower Risk Grade.

Use Case: A DeFi lending protocol wants to offer differentiated interest rates based on borrower quality – lower rates for high-credit-score borrowers to attract and retain the best users, higher rates for lower-credit-score borrowers to compensate for elevated default risk. Chainaware-credit-scorer provides the credit signal driving the rate differentiation. Prime borrowers (score 9) receive the protocol’s best rate. High-Risk borrowers (score 1-2) are declined or required to over-collateralize at 200%+. The differentiation improves risk-adjusted revenue and creates a meaningful incentive for borrowers to maintain clean on-chain behavior over time.

When Is It Required: Use chainaware-credit-scorer as a component within chainaware-lending-risk-assessor for full borrower risk assessment, or standalone when a simple 1-9 credit rating is sufficient for the use case. It is specifically required for ETH-based lending protocols wanting a standardized credit signal compatible with the broader DeFi lending ecosystem. For multi-chain lending platforms, chainaware-lending-risk-assessor provides broader coverage by combining the credit score with behavioral signals from the full Prediction MCP toolset. See our Credit Score guide for the complete methodology.

15. chainaware-lending-risk-assessor

Full borrower risk assessment for DeFi lending protocols – combining fraud probability, on-chain experience score, risk appetite classification, and (on ETH) credit score into a Borrower Risk Grade from A to F with specific recommended collateral ratio and interest rate tier. Grade A borrowers (low fraud, high experience, appropriate risk profile) receive the best terms. Grade F borrowers are declined. The agent covers ETH, BNB, BASE, HAQQ, and SOLANA – enabling multi-chain lending platforms to apply consistent underwriting standards across all supported networks using behavioral signals rather than collateral value as the only risk proxy.

Use Case: A DeFi lending protocol currently applies a flat 150% collateralization ratio to every borrower regardless of on-chain history. This approach drives away high-quality borrowers who resent over-collateralization for loans they will clearly repay. With chainaware-lending-risk-assessor, the protocol offers Grade A borrowers 110% collateralization at the best rate, Grade B borrowers 130% at standard rates, and Grade C borrowers 160% at elevated rates. Grade D-F wallets are declined or required to provide significant over-collateral. Capital efficiency improves, quality borrower acquisition increases, and risk-adjusted returns improve across the loan book.

When Is It Required: Deploy chainaware-lending-risk-assessor for any DeFi lending or credit protocol wanting to move beyond collateral-only risk assessment. It is specifically required for undercollateralized or uncollateralized DeFi lending products, where behavioral risk signals are the primary protection against default. Additionally, it is required for any lending protocol seeking to compete on borrower experience by offering differentiated rates – flat-rate protocols cannot attract and retain the highest-quality borrowers who have better options elsewhere.

16. chainaware-portfolio-risk-advisor

Portfolio-level rug pull risk scan that evaluates every token in a submitted portfolio, aggregates risk into a Portfolio Risk Score (0-100) and grade (A-F), flags dangerous concentrations, and produces a prioritized exit/reduce rebalancing plan. The primary signal for each token is its rug pull probability from predictive_rug_pull. Supplementary community rank from token_rank_single enriches the risk assessment with holder quality data for the approximately 2,500-3,000 tokens covered by the pre-calculated index. Concentration flags alert when a single high-risk token represents more than 20% of portfolio value (Critical Concentration) or when multiple tokens share the same deployer (Cluster Risk).

Use Case: A DeFi investor holds 12 positions across ETH and BNB, total value $85,000. Three tokens have no community rank data and significant social media promotion – a combination warranting scrutiny. Running chainaware-portfolio-risk-advisor identifies two of those three tokens as High Risk (TRS 58 and 71), with deployer behavioral signatures consistent with previous rug pull operations. The agent produces a rebalancing plan: exit both High Risk positions immediately ($12,400 combined), reduce a Moderate Risk position to 5% of portfolio, and hold the remaining nine positions scoring Low Risk. The investor exits before the highest-risk position rugs two weeks later.

When Is It Required: Run chainaware-portfolio-risk-advisor before deploying significant new capital into any multi-token DeFi position, before any rebalancing decision in a portfolio containing tokens launched in the last 90 days, and as a regular monthly audit of any DeFi portfolio containing more than five positions. It is specifically required for protocols managing DAO treasuries or yield strategies on behalf of users, where portfolio risk is a fiduciary responsibility rather than a personal investment choice.

17. chainaware-agent-screener

The first dedicated AI agent trust scoring tool in the on-chain intelligence market. Screens two addresses simultaneously: the agent wallet (the address the autonomous agent uses to transact) and the feeder wallet (the address that funds the agent). The feeder wallet is typically the most revealing signal – a fraudulent feeder means the agent operates on behalf of a bad actor regardless of how clean the agent wallet appears. The output is a normalized Agent Trust Score from 0 to 10: 0 means confirmed or likely fraud, 1 means new address with insufficient data, and 2.0-10.0 is a normalized reputation score. When the agent wallet is a smart contract rather than an EOA, behavioral data is unavailable and the score is capped at 6.0 with a proxy calculation. This directly addresses the structural vulnerability in the ERC-8004 agent registry – 196,000+ registered agents with no behavioral trust signals attached to their on-chain identities.

Use Case: A DeFi protocol evaluating whether to accept automated interactions from third-party AI trading agents faces a core challenge: without agent trust scoring, the protocol cannot distinguish between a legitimate institutional trading bot and a fraudulent agent designed to manipulate protocol state. Running chainaware-agent-screener on each agent’s wallet and feeder wallet produces a trust score used as an access gate. Agents scoring 7.0+ receive full access. Agents scoring 4.0-6.9 receive limited access with lower transaction limits and no admin function access. Agents scoring below 4.0 or with Score 0 are blocked entirely. Score 1 (new feeder wallet) triggers a manual review before access is granted.

When Is It Required: Deploy chainaware-agent-screener whenever a protocol, DEX, lending platform, or DAO accepts or considers accepting automated interactions from third-party AI agents. As the agentic economy grows – with AI agents increasingly operating autonomously across DeFi, executing trades, managing positions, and participating in governance – the need for behavioral trust assessment of agents becomes as important as the need for behavioral trust assessment of human wallets. The agent is also required for ERC-8004 registry participants seeking to validate the trustworthiness of other registered agents before delegating tasks or sharing resources with them. For context on the growing agentic economy and its fraud implications, see our Web3 Agentic Economy guide .

Growth Tech Agents – 15 Agents, Complete Reference

ChainAware’s Growth Tech agents convert the same behavioral intelligence that prevents fraud into measurable protocol growth – higher conversion rates, better user retention, smarter acquisition spend, and more relevant product recommendations. The foundational insight driving this category is that 84% of wallets connecting to a typical DeFi protocol after a marketing campaign are ghost wallets – addresses with zero real engagement that farming bots and airdrop hunters control. Traditional Web3 growth tools cannot distinguish these ghost wallets from genuine users because they lack behavioral intelligence. Growth Tech agents solve this by treating each wallet’s on-chain history as a behavioral fingerprint that reveals its intentions, experience, risk appetite, and likely lifetime value – before the protocol spends a single dollar acquiring or engaging it.

Together, these 15 agents cover the complete user lifecycle: identifying high-value targets before acquisition (lead-scorer, ltv-estimator), personalizing the first moment of engagement (platform-greeter, onboarding-router), recommending the right products (defi-advisor, wallet-marketer), retaining users through their journey (upsell-advisor), and understanding the full user base through segmentation (cohort-analyzer, whale-detector). Furthermore, every Growth Tech agent runs a fraud gate internally – a wallet that fails the fraud check receives no marketing message, no personalized greeting, and no upsell recommendation. For the foundational framework on why behavioral intelligence outperforms demographic or web analytics approaches for Web3 growth, see our Web3 User Segmentation guide .

18. chainaware-wallet-auditor

The flagship intelligence agent delivers the complete 22-dimension Web3 Persona for any wallet address in under one second. A single predictive_behaviour call returns the full behavioral profile: fraud probability (98% accuracy), all 12 intention probabilities (Borrow, Lend, Trade, Gamble, NFT, Stake ETH, Stake Yield Farm, Leveraged Staking, Leveraged Staking ETH, Leveraged Lending, Leveraged Long ETH, Leveraged Long Game), experience score (0-10), risk capability (0-9), AML forensic flags, Wallet Rank, behavioral categories, protocol usage history, and ChainAware’s direct personalization recommendations. This is the broadest intelligence output in the suite – used when a protocol needs everything about a wallet rather than a specific signal. Coverage: ETH, BNB, BASE, HAQQ, SOLANA.

Use Case: A DeFi protocol’s product team wants to understand who is actually connecting to their platform before redesigning the UI. Using chainaware-wallet-auditor on a sample of 500 recent connecting wallets reveals that 62% have High Lend intention, 18% have High Trade intention, 11% are experienced DeFi power users with 8+ experience scores, and 9% are ghost wallets with zero meaningful history. This behavioral distribution tells the product team that their core user is a yield-seeking lender, not the active trader they assumed. The UI redesign prioritizes lending product visibility – a decision driven by behavioral data rather than assumption.

When Is It Required: Use chainaware-wallet-auditor when the use case requires the complete behavioral picture rather than a single signal – individual due diligence on high-value wallets, building a comprehensive user understanding before product decisions, and providing the full context that orchestrating agents like chainaware-marketing-director need to compose complete reports. The free Wallet Auditor at chainaware.ai/audit runs this agent for any address with no signup required – start there to understand the full output before integrating via API. See our Wallet Auditor guide for the complete usage guide.

19. chainaware-reputation-scorer

Calculates the deterministic ChainAware reputation score (0-1000) using the standard formula: (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability). A score of 1,000 represents the theoretical maximum – experience 10, risk capability 9, fraud probability 0.00. In practice, scores above 750 represent Elite wallets: expert DeFi users with aggressive risk profiles and clean fraud histories. Scores below 125 indicate either ghost wallets with no history or high-fraud-probability addresses. The score is deterministic – given the same MCP inputs, the formula always produces the same output, making it auditable and reproducible for governance and allocation purposes. Coverage: ETH, BNB, BASE, HAQQ, SOLANA.

Use Case: A DAO wants to create a community leaderboard that ranks members by contribution quality rather than token holdings. Using chainaware-reputation-scorer on all community wallets produces a ranked list where active DeFi power users with long track records rise to the top, while passive token holders with minimal protocol engagement remain at the bottom. The leaderboard displays publicly on the DAO’s governance portal, creating a visible quality signal that incentivizes genuine participation over passive holding. Top-ranked wallets receive additional governance weight, early access to new protocol features, and community recognition – none of which require manual review to assign.

When Is It Required: Use chainaware-reputation-scorer when a standardized, comparable quality metric is needed across a large set of wallets – governance leaderboards, airdrop tier allocation (used internally by chainaware-airdrop-screener), lending collateral ratios, and marketing campaign quality gates all benefit from the single-number reputation score. It differs from chainaware-wallet-ranker (which ranks by total points and transaction count) in that the reputation formula explicitly penalizes fraud probability – a wallet with high activity but elevated fraud risk scores lower than a wallet with moderate activity and a clean history.

20. chainaware-wallet-ranker

Returns global wallet rank from experience score, total points, wallet age, and transaction count across the 20M+ wallet network. The rank provides a comparable quality metric across wallets from different blockchains through the unified behavioral scoring model – a wallet’s experience score on ETH is directly comparable to one on SOLANA. Batch mode produces a ranked leaderboard sorted by total points descending, identifying the highest-quality wallets in any submitted list. Unlike reputation-scorer (which uses a specific formula), wallet-ranker reflects ChainAware’s internal composite scoring of each wallet’s overall on-chain quality without the explicit fraud penalty component.

Use Case: A DeFi protocol wants to identify its top 50 users for a VIP program offering fee discounts and early feature access. Running chainaware-wallet-ranker on all 12,000 addresses that have ever interacted with the protocol produces a ranked leaderboard. The top 50 wallets by total points become VIP members. Because wallet rank reflects genuine on-chain quality rather than just protocol-specific activity, the VIP list includes wallets that are highly engaged across DeFi broadly – users most likely to promote the protocol within their wider DeFi networks and generate the most valuable word-of-mouth acquisition.

When Is It Required: Deploy chainaware-wallet-ranker for community leaderboards, VIP tier identification, governance weight calculation, and token holder quality assessment. It pairs naturally with chainaware-whale-detector – whale-detector identifies high-value wallets by behavioral depth, while wallet-ranker produces the specific numerical rank for ordering and comparison purposes. For the complete framework on wallet quality signals, see our Wallet Rank guide .

21. chainaware-whale-detector

Classifies wallets into four whale tiers – Mega Whale (experience ≥ 9, total points ≥ 5,000, active categories ≥ 3), Whale (experience ≥ 7.5 and total points ≥ 2,000, or experience ≥ 7 with high protocol diversity), Emerging Whale (experience ≥ 5 and total points ≥ 500, or experience ≥ 6 with high stake and trade intent), and Not a Whale. Each tier also receives an Active or Dormant classification based on forward-looking intent signals: Active whales have at least one High intent probability; Dormant whales have high experience but all-Low intent – they were once significant participants but are not currently engaged. Domain classification further identifies the wallet’s primary area: Trading Whale, DeFi Whale, NFT Whale, Multi-Chain Whale, Yield Whale, or Multi-Dimensional Whale. Fraud gate excludes wallets above 0.30 fraud probability from any whale classification.

Use Case: A DeFi protocol is launching a new advanced yield product designed for sophisticated users. The marketing team needs to identify which existing wallets in their user base qualify as genuine whales – and specifically which whales are currently active vs. dormant. Running chainaware-whale-detector on all 8,000 wallets that have interacted with the protocol in the last 90 days identifies 23 Mega Whales, 87 Whales, and 214 Emerging Whales. Within those groups, 68% are Active and 32% are Dormant. Active Mega Whales receive direct personal outreach for the new product launch. Dormant Whales receive a re-engagement campaign. Emerging Whales receive nurture content designed to accelerate their progression to the next tier.

When Is It Required: Run chainaware-whale-detector before any VIP program launch, before direct outreach campaigns targeting high-value users, before governance voting weight design (where whales warrant different treatment than retail participants), and as a regular audit of any protocol’s most valuable users to identify when whales go dormant and need re-engagement before they migrate to a competitor. The domain classification adds a targeting layer – a protocol launching an NFT-adjacent feature should specifically target NFT Whales, while a new yield vault should target Yield Whales and DeFi Whales.

22. chainaware-ltv-estimator

Estimates 12-month revenue potential for any wallet as a USD range using a seven-step model. Step one derives the annual transaction rate from experience level (Beginner → 5 tx/year, Expert → 700 tx/year). Step two applies an intent multiplier from forward-looking signals (3+ High intents → 1.25×, all Low → 0.65×). Step three calculates average transaction value from wallet balance × platform share (configurable, defaults to 15%). Step four applies the fee rate (configurable, defaults to 0.1%). Step five applies a category multiplier from activity breadth (1 category → 1.0×, 5+ categories → 1.75× cap). Step six applies a risk multiplier from risk profile (Conservative → 0.70×, Aggressive → 1.40×). Step seven applies a retention factor from fraud probability (0.00-0.09 → 0.95, 0.51-0.70 → 0.20). The final estimate applies ±25% to produce a range. Hard reject conditions return $0 with no range for confirmed fraud, fraud above 0.70, or any AML forensic flag.

Use Case: A DeFi protocol’s growth team plans a user acquisition campaign with a $200,000 budget. Before spending, they run chainaware-ltv-estimator on 10,000 target wallet addresses from a purchased marketing list. Results reveal that 6,200 wallets have estimated 12-month LTV below $10 (Dormant tier), 2,800 wallets have LTV in the $10-$100 range (Low tier), 800 wallets have LTV in the $100-$1,000 range (Medium tier), and 200 wallets have LTV above $1,000 (High tier). Rather than spending the $200,000 uniformly across all 10,000 addresses, the team concentrates 80% of the budget on the 1,000 Medium and High LTV wallets. Expected ROI improves dramatically compared to uniform distribution.

When Is It Required: Use chainaware-ltv-estimator before any acquisition campaign to prioritize high-value targets, before VIP tier assignment to identify which wallets generate the most protocol revenue, and before marketing budget allocation decisions where targeting the right wallets determines whether the campaign generates positive ROI. It works alongside chainaware-lead-scorer – lead-scorer measures conversion probability, while ltv-estimator measures revenue magnitude. Combining both gives a complete acquisition prioritization signal: high-lead-score × high-LTV wallets deserve the most aggressive outreach investment.

23. chainaware-lead-scorer

Sales lead qualification engine returning a lead score (0-100), tier (Hot/Warm/Cold/Dead), conversion probability, and recommended outreach angle for any wallet. The scoring model weights five components: experience (35%), intent strength (25%), activity breadth (20%), risk appetite (10%), and fraud penalty (up to −10). Product context doubles the weight of the matching intent signal – a staking product doubles Prob_Stake, a cross-chain bridge doubles Prob_Bridge – making the score product-specific rather than generic. Hot leads (75-100) warrant immediate personalized outreach. Dead leads (0 or fraud-disqualified) are excluded from all campaigns entirely, preventing budget waste on wallets that would never convert.

Use Case: A DeFi yield aggregator launching on BASE wants to identify which ETH-based DeFi users are most likely to bridge and adopt the new platform. The growth team runs chainaware-lead-scorer on 25,000 ETH wallet addresses that have interacted with competing yield products, with product context set to “cross-chain yield aggregator on BASE.” The scoring returns 340 Hot leads (score 75+, high Prob_Bridge and Prob_Stake intent), 2,800 Warm leads (score 50-74), 15,000 Cold leads (score 25-49), and 6,860 Dead leads (below 25 or fraud-disqualified). The team focuses personalized outreach on the 340 Hot leads and runs automated campaigns for the 2,800 Warm leads. Acquisition cost per converted user drops significantly compared to the previous campaign that treated all 25,000 addresses identically.

When Is It Required: Run chainaware-lead-scorer before any acquisition outreach campaign, before direct sales team prioritization, and before budget allocation across different wallet segments. It is specifically required when a protocol launches a new product or feature and wants to identify existing wallet holders most likely to adopt it based on behavioral signals – rather than guessing based on past protocol interactions alone. See our Behavioral Analytics guide for the complete acquisition framework.

24. chainaware-wallet-marketer

Generates a hyper-personalized marketing message of maximum 20 words for any wallet, derived directly from its on-chain behavioral signals – no generic crypto copy, no templated language. Signal priority determines the message angle: Prob_Stake High leads with staking yield opportunity; Prob_Trade High leads with trading execution quality; Prob_Bridge High leads with cross-chain capability; Prob_NFT_Buy High leads with NFT feature; DeFi Lender category leads with lending/yield rates; experience above 7.5 leads with advanced power user features; experience below 2.5 leads with simple beginner-friendly onboarding. The message mirrors what the wallet actually does on-chain, making it feel personal rather than promotional. Fraud gate blocks message generation entirely for high-fraud-probability wallets.

Use Case: A DEX wants to run a re-engagement campaign targeting 5,000 wallets that connected once but never executed a trade. Running chainaware-wallet-marketer in batch mode on all 5,000 addresses produces 5,000 distinct messages – each derived from that specific wallet’s behavioral signals. A wallet with High Prob_Stake and DeFi Lender category receives: “Your lending habits earn yield. Our single-click vault automates it. Start here.” A wallet with High Prob_Trade and Active Trader category receives: “You trade fast. Our zero-slippage routing finds better fills. Try one swap.” A beginner wallet with experience below 2 receives: “New to DeFi? Earn your first yield in under two minutes. Start here.” The personalized messages achieve 3-4× higher click-through rates than the generic campaign the DEX ran previously.

When Is It Required: Use chainaware-wallet-marketer for any outbound campaign where personalization improves conversion – which is essentially every outbound campaign. It is specifically required when a protocol has a segmented user base with significantly different behavioral profiles, when re-engaging dormant users where a generic message will be ignored, and when the campaign budget is large enough that even a 2× improvement in conversion rate generates meaningful additional revenue. For the complete personalization framework, see our Why Personalization Matters guide .

25. chainaware-platform-greeter

Contextual welcome message engine generating platform-specific in-app messages of maximum 35 words at wallet connection. The same wallet receives a completely different message on Aave than on 1inch or OpenSea – because what matters to a DeFi lender visiting a lending platform differs fundamentally from what matters when that same wallet visits a DEX or an NFT marketplace. Platform type detection maps the wallet’s dominant behavioral signals to the most relevant platform angle. Returning users with protocol history receive “welcome back” framing with specific references to their history. First-time visitors with strong intent alignment receive “you know X, here’s what we do for X” framing. Low-experience first-timers receive simplified educational framing. Tone is configurable across friendly, professional, and bold to match brand voice.

Use Case: A lending protocol integrates chainaware-platform-greeter into its wallet connection event. When a DeFi Lender wallet with experience 8 and existing Aave positions connects, it sees: “Your lending positions are working – ETH supply rate is up 0.4% since your last visit. Check your health factor before rates move.” When a High Prob_Trade wallet connects for the first time, it sees: “You trade – here you can also earn on idle assets between swaps.” When a low-experience wallet connects for the first time, it sees: “New here? Deposit any token and earn interest automatically. No minimums.” Three different wallets, three different messages, all generated automatically at connection with zero manual configuration per user segment.

When Is It Required: Deploy chainaware-platform-greeter for any DeFi platform with diverse user types – a protocol serving both experienced DeFi power users and first-time users needs different first-moment experiences for each segment. It is specifically required when conversion analytics show a significant percentage of connecting wallets leaving without taking any action – a sign that the current generic landing experience does not resonate with the behavioral diversity of the connecting wallet population. The agent adds under 200ms to the wallet connection flow, negligible for user experience purposes.

26. chainaware-onboarding-router

Routes each connecting wallet to the correct onboarding experience based on verifiable on-chain experience rather than self-reported surveys or assumed user segments. Experience 0-2.5 → Beginner Tutorial (full guided walkthrough – this wallet needs hand-holding through every step). Experience 2.6-6 → Intermediate Guide (condensed tips that skip the absolute basics while still orienting the user to platform-specific features). Experience 6.1-10 → Skip Onboarding (power user, straight to the product – tutorials waste their time and signal that the platform doesn’t understand them). Secondary signals refine the route: a wallet with experience 5.5 that already uses the platform’s specific protocol category can skip most tutorials even though its overall score is technically Intermediate. New Address always routes to Beginner regardless of other signals.

Use Case: A DeFi platform’s user research team discovers that 23% of users who complete the full onboarding tutorial are experienced DeFi power users who were frustrated by being forced through beginner content. These users have 3× higher churn rates in the first week compared to users correctly identified as power users who skipped onboarding. Integrating chainaware-onboarding-router eliminates the mis-routing: power users (experience 6.1+) go directly to the product, intermediate users see a condensed orientation, and genuine beginners receive the full tutorial. First-week churn drops 31% as power users stop abandoning the platform out of frustration with irrelevant onboarding content.

When Is It Required: Deploy chainaware-onboarding-router for any platform with a multi-step onboarding flow and a diverse user base that includes both experienced DeFi users and newcomers. It is specifically required when product analytics show high drop-off during onboarding – a symptom that the current fixed onboarding experience is poorly matched to the actual experience distribution of the connecting wallet population. The agent works best in combination with chainaware-platform-greeter (which personalizes the first moment before onboarding begins) and chainaware-defi-advisor (which provides product recommendations post-onboarding). For the complete onboarding conversion analysis, see our DeFi Onboarding guide .

27. chainaware-defi-advisor

Personalized DeFi product recommendation engine with three product tiers calibrated to wallet experience and risk appetite. Tier 1 Safe Harbor covers Beginner and Conservative wallets: simple staking, stablecoin lending, savings vaults, fixed-rate lending. Tier 2 Yield Builder covers Intermediate and Moderate wallets: liquid staking, blue-chip LP pools, variable rate lending, multi-asset vaults. Tier 3 Yield Maximizer covers Experienced and Aggressive wallets: leveraged yield farming, options vaults (DOVs), concentrated liquidity CLMM active management, cross-chain yield arbitrage, and veToken strategy stacking. Intent signals boost recommendations within the tier: Prob_Stake High prioritizes staking products first; Prob_Trade High prioritizes LP pools and active liquidity. Protocol history adds a further targeting layer: a wallet that already uses Aave receives Aave-compatible product recommendations over generic alternatives.

Use Case: A DeFi aggregator platform connects 500 different wallets per day across its product suite. Without personalization, every wallet sees the same “Featured Products” section – typically the highest-APY products, which are also the highest-risk. Conservative beginners see leveraged products they don’t understand, and aggressive experts see beginner staking options that bore them. Integrating chainaware-defi-advisor personalizes the product menu for each connecting wallet: beginners see stablecoin lending and simple staking; power users see advanced leveraged strategies and CLMM management tools. First-session product interaction rates increase 2.4× across all experience tiers because every user sees products calibrated to their level.

When Is It Required: Use chainaware-defi-advisor for any multi-product DeFi platform where the right product for one user is actively wrong for another. It is specifically required when conversion analytics show significant variance in product adoption rates by user experience level – a sign that current product placement is suboptimal for at least one segment. For platforms launching new products, the agent identifies which existing wallet segments are most aligned with the new product’s requirements before the launch, enabling targeted pre-launch outreach to the highest-probability adopters. See our DeFi Platform Use Cases guide .

28. chainaware-upsell-advisor

Identifies the optimal next product to offer an existing user and the precise moment to offer it. Upgrade readiness score (0-100) combines experience headroom toward the next product tier (40% weight), intent alignment with the target product (35%), and risk appetite fit (25%). Score 80-100 → offer now, conversion probability above 65%. Score 60-79 → offer at the next behavioral trigger event. Score 40-59 → nurture first, offer after 1-2 more sessions. Score below 40 → do not upsell yet – the risk is churn rather than conversion. Trigger events are behavioral rather than time-based: a wallet ready for a staking upgrade gets the offer the next time it stakes or claims rewards, not on a fixed weekly cadence. A “What NOT to do” recommendation identifies the single upsell approach most likely to cause churn for each specific wallet – for example, “Don’t pitch leveraged products – this is a Conservative wallet and the complexity will cause churn.”

Use Case: A DeFi lending platform has 3,000 active users on its basic lending tier. The product team wants to introduce an advanced leveraged yield farming product and identify which users are ready to upgrade now vs. which need nurturing first. Running chainaware-upsell-advisor on all 3,000 users with the new product as context identifies 180 users with readiness above 80 (offer now), 620 users at 60-79 (offer at next trigger), 1,400 users at 40-59 (nurture first), and 800 users below 40 (do not upsell). The 180 “offer now” users receive immediate personalized outreach with specific trigger messaging aligned to their dominant intent signal. Within four weeks, 67% of the “offer now” group has upgraded – without wasting outreach budget on the 800 users who were not ready and would have churned if pushed.

When Is It Required: Deploy chainaware-upsell-advisor whenever a protocol launches a new product tier and wants to maximize adoption among existing users. It is specifically required for protocols with a tiered product structure where pushing the wrong product too early causes churn, for platforms with subscription-based models where upgrade timing significantly affects revenue, and for any DeFi protocol where the most valuable users are those engaging with multiple product tiers simultaneously. The trigger event recommendation is especially valuable – it replaces time-based upsell campaigns (which push users at arbitrary moments) with behavior-triggered campaigns (which engage users at the exact moment their intent signals indicate readiness).

29. chainaware-cohort-analyzer

Batch behavioral cohort segmentation for Web3 analytics teams. Classifies every wallet in a submitted list into one of eight behavioral cohorts: Power DeFi User (experience ≥ 7, DeFi Lender or Active Trader dominant, protocols ≥ 5), NFT Collector (NFT Collector dominant, experience ≥ 3), Yield Farmer (Yield Farmer dominant or Prob_Stake High with experience ≥ 5), Multi-Chain Explorer (Bridge User dominant or bridge-heavy protocol history), Active Trader (Prob_Trade High with experience ≥ 4), Casual User (experience 2-4.9, no dominant pattern), Dormant/Inactive (experience ≥ 2 but all intent signals Low), and New/Fresh Wallet (new address with clean fraud signals). Fraud exclusions – bots, confirmed fraud, AML flags, suspicious new wallets – are separated from behavioral cohorts entirely. Each cohort receives a specific engagement strategy recommendation, and the full report includes audience quality score, per-cohort statistics, and a three-priority action plan.

Use Case: A DeFi protocol planning its Q3 marketing budget wants to allocate spend across different user segments rather than running one generic campaign. Chainaware-cohort-analyzer on their 15,000-wallet user base reveals: 890 Power DeFi Users (6%), 1,200 NFT Collectors (8%), 2,100 Yield Farmers (14%), 800 Multi-Chain Explorers (5%), 3,400 Casual Users (23%), 2,800 Dormant wallets (19%), 1,600 New wallets (11%), and 2,210 excluded bots and fraud (15%). The budget allocation becomes data-driven: 35% to Yield Farmer acquisition for the new vault product, 25% to Casual User conversion, 20% to Dormant re-engagement, and 20% to New wallet onboarding. Each cohort receives a distinct message strategy rather than a generic campaign blasted to all 15,000 addresses.

When Is It Required: Run chainaware-cohort-analyzer before any marketing budget planning cycle, before product launch targeting decisions, and as a quarterly audit of user base composition to detect shifts in behavioral distribution. It is specifically required before an airdrop (to ensure token distribution aligns with cohort quality rather than farming behavior), before a governance token launch (to understand which community members qualify for each allocation tier), and before any significant UI redesign (to ensure the redesign serves the actual behavioral distribution rather than an assumed user persona).

30. chainaware-token-ranker

Discovers and ranks tokens by the behavioral quality of their holder community across five categories – AI Token, RWA Token, DeFi Token, DeFAI Token, DePIN Token – on ETH, BNB, BASE, and SOLANA. Community rank scores the aggregate behavioral strength of all token holders: wallet age, transaction history, protocol diversity, and experience scores across the 20M+ wallet network. A token whose holders are predominantly experienced, long-tenured, multi-protocol DeFi users ranks higher than a token with the same market cap but predominantly fresh wallets with minimal history. This ranking reflects genuine community quality – not just trading volume or price momentum, which can be manufactured. Supports sort by community rank, normalized rank, or holder count; category filtering; pagination; and name-based token search.

Use Case: An institutional DeFi fund wants to allocate capital to the top three AI tokens by community quality rather than market cap. Running chainaware-token-ranker for AI Token category on ETH and BNB returns a ranked list showing which AI tokens have the strongest holder bases of experienced, legitimate DeFi participants – and which have significant proportions of fresh wallets and farming addresses in their holder distribution. The fund identifies two tokens where community quality is significantly stronger than their market cap rank suggests – potential value opportunities where genuine community strength has not yet been reflected in price. Both tokens are added to the portfolio after individual deep-dives using chainaware-token-analyzer.

When Is It Required: Use chainaware-token-ranker for token portfolio research and selection when community quality is a meaningful signal, for DEX teams curating featured token listings based on genuine community strength rather than trading volume alone, and for any platform wanting to surface high-quality tokens to users before market price discovery catches up to community quality. It works as the first step in a two-step research process: token-ranker identifies the best candidates from a category, then chainaware-token-analyzer deep-dives each candidate’s specific holder composition. See our Token Rank guide for detailed methodology.

31. chainaware-token-analyzer

Deep-dives into a single token’s community rank and top holder profiles – returning each top holder’s wallet age, total transaction count, total points, and global rank across the 20M+ wallet network. Optional fraud screening on the top holders via predictive_fraud identifies whether the token’s largest positions are held by legitimate experienced wallets or by coordinated fraud networks disguising their concentration. The holder quality assessment computes average wallet age, average transaction count, and average global rank across the top holders, producing a Verdict (2-3 sentences on whether these are genuine power users or manufactured holders). Token-ranker identifies which tokens have the strongest community quality in aggregate; token-analyzer validates whether specific tokens actually back that aggregate signal with genuine individual holders.

Use Case: A crypto exchange is evaluating whether to list a new DeFi token. The community rank from chainaware-token-ranker shows the token in the top 20% of its category – strong enough to consider. Chainaware-token-analyzer deep-dives the top 20 holders: 14 have average wallet age above 800 days, high transaction counts, and global ranks in the top 10% of the 20M+ wallet network. However, three of the top 20 holders share a funding source and show coordinated acquisition patterns – signals of artificial holder concentration. The fraud screening confirms two of those three have elevated fraud probability. The exchange requires the team to reduce concentration before listing. Six weeks later, the concentration issue is resolved, and the token lists and performs well due to its genuinely strong community foundation.

When Is It Required: Run chainaware-token-analyzer before listing any token on an exchange or DEX with listing standards, before making significant portfolio allocation to a token where holder quality affects the investment thesis, and before any governance vote giving token holders significant power – understanding whether those holders are genuine community members or coordinated operators directly affects the legitimacy of governance outcomes. It is also required as part of due diligence for institutional crypto fund investments where holder composition is a material factor in the investment case.

32. chainaware-marketing-director

The orchestrator agent – a senior marketing strategist that delegates to seven specialist agents and synthesizes their outputs into a complete Marketing Campaign Brief. In batch mode (multiple wallets), the agent runs six sequential phases: segmentation via chainaware-cohort-analyzer, lead scoring and whale detection on the highest-potential wallets, per-cohort message generation via chainaware-wallet-marketer, upsell opportunity identification via chainaware-upsell-advisor, onboarding routing for new wallets, and executive campaign brief synthesis. In single-wallet mode, it runs five specialist agents simultaneously and returns a complete Wallet Marketing Profile including fraud risk, whale tier, lead score, personalized outreach message, platform welcome message, upsell path, and recommended onboarding flow. The Marketing Director represents the highest-level abstraction in ChainAware’s agent architecture – demonstrating what coordinated multi-agent intelligence delivers that no single specialist agent can replicate independently. It requires a platform description as input, using that context to make every generated message feel native to the specific protocol.

Use Case: A DeFi lending protocol is planning a growth push targeting 200 existing wallets that have connected but never borrowed. The growth lead does not have time to run each specialist agent separately and synthesize results manually. Running chainaware-marketing-director with the 200 wallet addresses and the platform description as input produces a complete Campaign Brief in one pass: 23 Hot leads requiring immediate personal outreach; 8 Mega and Whale wallets identified for VIP treatment; per-cohort message templates for the 6 behavioral cohorts represented in the wallet list; 31 wallets with upgrade readiness above 80 ready for a borrowing product offer; 18 new wallets routed to beginner onboarding; and 14 excluded as fraud or bots. The entire brief – segmentation, prioritization, messages, execution sequence – is ready for the growth team to execute.

When Is It Required: Use chainaware-marketing-director when a campaign needs the output of multiple specialist agents and the team does not have the resources to run them separately and synthesize results. It is specifically the right choice for time-sensitive campaigns where speed matters, for small growth teams needing a complete brief rather than raw intelligence, and for any campaign spanning multiple wallet segments requiring different strategies simultaneously. The agent is also the best entry point for teams new to ChainAware’s agent suite – a single Marketing Director run demonstrates the full capability range of the underlying specialist agents in one unified output. For the complete campaign planning framework, see our Web3 Marketing guide .

How Agents Compose Into Pipelines

The most powerful applications of ChainAware’s 32 agents emerge not from individual deployment but from composing them into pipelines – where the output of one agent becomes the input of the next. Every agent’s documentation includes a composability section mapping its natural connections to adjacent agents. Three core pipelines demonstrate the composability principle and cover the most common production deployments.

The Compliance Pipeline

The compliance pipeline sequences four agents: trust-scorer → aml-scorer → compliance-screener → transaction-monitor. Trust-scorer provides the fast first gate at under 50ms – any wallet below 0.30 trust score is immediately routed to enhanced review. AML-scorer adds forensic verification for wallets that pass the trust gate, checking all 19 forensic flag categories and producing the documented AML score needed for regulatory reporting. Compliance-screener orchestrates both signals plus transaction pattern analysis into the final PASS / EDD / REJECT verdict with full documented evidence trail. Transaction-monitor handles ongoing screening post-onboarding, flagging any transaction that exceeds risk thresholds after a wallet has been onboarded and approved.

Together, the four agents cover the complete compliance lifecycle from pre-onboarding screening through ongoing monitoring – the full stack required for MiCA-compliant operation. According to FATF’s Virtual Assets Recommendations , this kind of continuous monitoring is increasingly required rather than optional for regulated crypto asset service providers. Furthermore, the documented output from each agent in the pipeline creates the audit trail that regulators require – not just a screening decision, but the specific signals and thresholds applied to produce it.

The Growth Pipeline

The growth pipeline sequences six agents: cohort-analyzer → lead-scorer → whale-detector → wallet-marketer → onboarding-router → upsell-advisor. Cohort-analyzer segments the full wallet list and identifies fraud exclusions, producing the audience map for the campaign. Lead-scorer then ranks the highest-conversion targets within the highest-value cohorts. Whale-detector surfaces the VIP wallets within those cohorts for personal outreach. Wallet-marketer generates per-wallet personalized messages for the identified hot leads and whale wallets. Onboarding-router assigns new wallets in the cohort analysis to the correct first-time experience. Upsell-advisor identifies existing users ready for product upgrades, completing the full lifecycle from acquisition through retention.

Notably, chainaware-marketing-director runs this exact pipeline automatically – making it the recommended entry point for teams deploying the growth pipeline for the first time. The Marketing Director adds the synthesis layer that converts six separate agent outputs into a single actionable Campaign Brief, eliminating the manual work of combining results across multiple specialist runs.

The Token Intelligence Pipeline

The token intelligence pipeline sequences three agents: token-ranker → token-analyzer → rug-pull-detector. Token-ranker identifies the strongest tokens in a target category by community quality across ETH, BNB, BASE, or SOLANA – producing a shortlist of high-potential candidates. Token-analyzer then deep-dives each shortlisted token’s specific holder composition, validating whether the aggregate community quality score reflects genuine individual holders or manufactured concentration. Rug-pull-detector screens the contract address and deployer wallet for the tokens that pass both previous stages – confirming that the project behind the strong community is not itself a fraud risk.

The three agents together provide the complete due diligence stack for token investment decisions, exchange listing evaluation, and governance token selection. Moreover, they address the three distinct questions that token evaluation requires: which tokens have the strongest communities (token-ranker), are those communities genuinely strong or manufactured (token-analyzer), and is the contract itself safe (rug-pull-detector). Each question requires a different tool, and combining all three produces a confidence level in a token that no single tool delivers alone. For the complete framework on how behavioral intelligence applies to token research, see our Token Rank guide .

The Agentic Economy Pipeline

The agentic economy pipeline sequences two Fraud Tech agents with the transaction-monitor: agent-screener → counterparty-screener → transaction-monitor. As AI agents increasingly operate autonomously across DeFi – executing trades, managing positions, and participating in governance on behalf of humans – the need for agent-specific trust assessment becomes as important as wallet trust assessment. Agent-screener validates the trust score of any third-party AI agent before it is granted access to a protocol or given permission to interact with user funds. Counterparty-screener validates each specific address the agent will interact with before execution. Transaction-monitor provides continuous real-time risk scoring for every transaction the agent executes once granted access.

This pipeline addresses the structural vulnerability in the current ERC-8004 ecosystem – 196,000+ registered agents with no behavioral trust signals. ChainAware’s agentic economy pipeline provides the trust infrastructure that the registry itself lacks, making it the foundational security layer for any protocol accepting autonomous AI agent interactions. For the complete analysis of how AI agents are reshaping Web3 operations, see our Web3 Agentic Economy guide .

Getting Started – Integration in Three Steps

All 32 agents are available as open-source Claude Code agent definitions at github.com/ChainAware/behavioral-prediction-mcp . Integration requires three steps and no blockchain expertise. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for AI agent tool access – making ChainAware’s MCP-native delivery compatible with any LLM infrastructure that supports the standard.

Step one – register the Prediction MCP server in your Claude Code environment:

claude mcp add --transport sse chainaware-behavioral-prediction \
  https://prediction.mcp.chainaware.ai/sse \
  --header "X-API-Key: YOUR_KEY"

Step two – clone the repository and copy all 32 agent definitions into your project:

git clone https://github.com/ChainAware/behavioral-prediction-mcp.git
cp -r behavioral-prediction-mcp/.claude/agents/ your-project/.claude/agents/

Step three – invoke any agent directly from Claude Code:

claude --agent chainaware-fraud-detector
# or trigger from within Claude Code:
@chainaware-wallet-auditor

API keys are available at chainaware.ai/pricing . The free Wallet Auditor at chainaware.ai/audit demonstrates the full behavioral intelligence output with no API key or signup required – start there to understand the complete output before building your integration. Additionally, the free Fraud Detector at chainaware.ai/fraud-detector and Rug Pull Detector at chainaware.ai/rug-pull-detector demonstrate the Fraud Tech agent outputs with no setup. For the complete developer integration guide covering Claude Desktop, Cursor, and custom MCP client setups, see our Prediction MCP guide .

Frequently Asked Questions

What is a ChainAware sub-agent?

A ChainAware sub-agent is a pre-built Claude Code agent definition – a markdown file containing a name, description, role definition, decision logic, output format specification, and MCP tool references. When placed in a Claude Code project’s .claude/agents/ directory, the agent becomes invocable by name from any Claude Code session in that project. The agent calls ChainAware’s Prediction MCP tools (predictive_fraud, predictive_behaviour, predictive_rug_pull, credit_score, token_rank_list, token_rank_single) with the appropriate parameters, interprets the response according to its decision logic, and returns a structured output in the format defined in the agent file. All 32 agents are open-source under the MIT license at github.com/ChainAware/behavioral-prediction-mcp .

How do the 32 agents relate to the ChainAware Prediction MCP?

The Prediction MCP is the intelligence layer – the SSE endpoint at prediction.mcp.chainaware.ai/sse that exposes ChainAware’s six prediction tools as MCP-callable functions. The 32 agents are the application layer – pre-built Claude Code agents that call those tools with the right parameters, apply decision logic to the results, and return structured outputs ready for human or automated action. Any developer can call the raw MCP tools directly via the REST API for custom integrations. The agents provide a head start – 32 production-ready agent definitions covering the most common use cases, tested and maintained by ChainAware’s team. For the complete MCP integration guide, see our Prediction MCP guide .

Which agent should I start with?

Start with chainaware-wallet-auditor for the broadest view of what ChainAware’s intelligence produces – it returns the complete 22-dimension Web3 Persona in one call, showing every signal that the specialist agents use individually. The free Wallet Auditor at chainaware.ai/audit runs this agent for any wallet address with no setup required. Once you understand the full output, select the specialist agent matching your primary use case: fraud prevention teams start with chainaware-fraud-detector; launchpad teams start with chainaware-rug-pull-detector; compliance teams start with chainaware-aml-scorer; growth teams start with chainaware-cohort-analyzer for their existing user base; teams evaluating AI agent trustworthiness start with chainaware-agent-screener.

Can I modify the agent definitions for my specific use case?

Yes – all 32 agent definition files are open-source under the MIT license. Fork the repository, modify any agent’s decision thresholds, output format, or tool selection, and deploy your customized version alongside the standard agents. Common customizations include adjusting fraud probability thresholds for specific risk tolerances, adding platform-specific context to message templates in chainaware-wallet-marketer and chainaware-platform-greeter, and modifying the governance tier classification thresholds in chainaware-governance-screener to match specific DAO requirements. The only component that is proprietary and cannot be modified is the underlying Prediction MCP server and its trained ML models – the intelligence that powers the tool calls. Agent definitions, decision logic, and output formats are all freely modifiable.

What is the difference between Fraud Tech and Growth Tech agents?

Fraud Tech agents answer whether a wallet, contract, or transaction can be trusted – they produce verdicts (block, flag, allow, reject, qualify). Growth Tech agents answer how to engage a wallet that has passed trust assessment – they produce recommendations (which product to surface, what message to send, which onboarding flow to show). Both categories draw from the same 20M+ wallet persona database and the same Prediction MCP tools. However, every Growth Tech agent runs a fraud gate before producing any recommendation – a wallet that fails the fraud check receives no marketing message, no personalized greeting, and no upsell recommendation. This means the categories are parallel layers rather than sequential stages: fraud protection runs continuously through every growth decision, ensuring that behavioral personalization never extends to wallets that ChainAware’s models identify as fraudulent operators.

How accurate are ChainAware’s fraud detection models?

ChainAware achieves 98% fraud detection accuracy on ETH and 96% on BNB, backtested against CryptoScamDB – the largest publicly available database of documented crypto fraud incidents. The rug pull detection model achieves 90.1% accuracy, backtested on the PancakeSwap V2 dataset covering $569M in documented rug pull losses from weeks 1-20 of 2026. These accuracy figures measure the model’s ability to correctly identify fraudulent wallets and contracts before they commit their recorded offense – not accuracy on post-incident classification. The distinction matters: ChainAware’s models are designed to predict fraud before it executes, which is structurally harder than forensic classification of known fraud incidents. For the complete accuracy methodology and comparison against forensic approaches, see our Forensic vs AI-Powered Analytics guide .

Are the agents available on all blockchains?

Coverage varies by agent and underlying MCP tool. The predictive_fraud tool – used by fraud-detector, aml-scorer, trust-scorer, and counterparty-screener – covers the broadest network set: ETH, BNB, POLYGON, TON, BASE, TRON, and HAQQ. The predictive_behaviour tool – used by wallet-auditor, reputation-scorer, whale-detector, and the growth agents – covers ETH, BNB, BASE, HAQQ, and SOLANA. The predictive_rug_pull tool covers ETH, BNB, BASE, and HAQQ. Agents supporting networks not covered by their primary tool include automatic fallback logic – for example, chainaware-airdrop-screener falls back to predictive_fraud for POLYGON, TON, and TRON wallets. The classification table in this article lists exact network coverage per agent for quick reference.

Why did ChainAware build on Claude specifically?

Claude’s tool use and structured output capabilities make it particularly well-suited for the deterministic decision logic that fraud detection and compliance agents require. An agent applying five disqualification rules in strict order – stopping at the first failure – needs a model that follows logical sequences reliably without hallucinating intermediate steps. Additionally, Claude Code’s native agent support (the .claude/agents/ directory standard) makes deployment frictionless for teams already using Claude Code. Agents requiring faster, cheaper inference (chainaware-trust-scorer, chainaware-wallet-ranker) use Claude Haiku 4.5. Agents requiring richer analytical reasoning (chainaware-wallet-auditor, chainaware-cohort-analyzer, chainaware-marketing-director) use Claude Sonnet 4.6. The model selection is specified in each agent’s frontmatter and can be changed by forking the agent definition file. ChainAware’s Prediction MCP tools are model-agnostic – GPT-4, Gemini, and any other MCP-compatible model can call them directly via the REST API.

How does ChainAware’s intelligence relate to the CB Insights market map?

ChainAware was named in CB Insights’ AI Fraud Prevention Market Map in June 2026 – placed in the On-Chain Intelligence subcategory alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid. CB Insights selected companies based on Mosaic health scores and equity funding recency, filtering out thousands of projects that did not meet the institutional bar. ChainAware’s position on the map validates the Fraud Tech agents (fraud-detector, aml-scorer, compliance-screener, rug-pull-detector, and transaction-monitor) specifically – these are the agents that deliver the on-chain intelligence capability CB Insights recognized. Beyond the map placement, ChainAware is the only company in the entire CB Insights list with a publicly traded token listed in CoinGecko’s AI category – a position that reflects the dual institutional and decentralized distribution model that the 32 agents are built to serve.

External Sources: ChainAware GitHub Repository · Anthropic Model Context Protocol · FATF Virtual Assets Recommendations · ERC-8004 Agent Registry · CB Insights AI Fraud Prevention Market Map

The post ChainAware.ai’s 32 Claude Sub-Agents – Fraud Tech and Growth Tech for the Agentic Economy first appeared on ChainAware.ai.

ChainAware.ai appears in the On-Chain Intelligence subcategory alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid. That placement represents meaningful institutional validation – CB Insights selects companies based on Mosaic health scores above 600 and equity funding recency since 2024, filtering out thousands of projects that do not meet the bar.

One additional data point makes ChainAware’s position unique across the entire 200-company map. ChainAware is the only Web3 AI token in the full list – and the only company in the On-Chain Intelligence category with a publicly traded token listed in CoinGecko’s AI category. Among 1,385 tokens in that category, ChainAware’s AWARE token is the single representative of on-chain intelligence and behavioral fraud detection.

This article explains what that combination means, why it matters for enterprise buyers, developers, and investors – and how ChainAware’s specific products produce outcomes that no other company on the map delivers.

What Is the CB Insights AI Fraud Prevention Market Map?

CB Insights is the institutional research and intelligence platform that tracks private company health scores, funding rounds, and competitive landscapes for 100,000+ technology companies. Its market maps represent the authoritative view of emerging technology categories – used by venture capital firms, corporate development teams, enterprise procurement departments, and regulatory bodies to identify leading vendors and benchmark competitive positioning.

The AI Fraud Prevention Market Map, published June 2, 2026, covers the companies building infrastructure to detect, prevent, and manage fraud in the AI era. That framing is deliberate and significant – it separates the legacy fraud prevention market (rules-based, human-reviewed, slow) from the emerging category of AI-native fraud prevention (predictive, automated, operating at agent speed).

Why This Map Exists Now

CB Insights publishes category maps when a market reaches sufficient maturity and investment volume to justify systematic mapping. The timing of the AI Fraud Prevention map reflects three converging forces that have made fraud prevention one of the most actively funded technology categories of 2026.

First, AI-generated fraud has scaled dramatically. Deepfake video scams, synthetic identity creation, and AI-powered phishing campaigns have collectively pushed AI-based fraud losses toward the $40 billion annual mark projected by industry analysts. Traditional fraud detection tools were built for human-speed fraud – they cannot detect AI-generated attacks operating at machine speed.

Second, the agentic economy has created entirely new fraud surfaces. AI agents transacting autonomously on behalf of humans do not carry passports, credit histories, or biometric signatures. Every identity and trust system built over the last 30 years assumes the actor is human. Agents need identity and trust infrastructure built specifically for how they operate – a gap that every major new crypto VC fund has identified as their primary investment thesis.

Third, stablecoin adoption has accelerated on-chain transaction volumes toward levels that require institutional-grade compliance infrastructure. According to CB Insights, stablecoin transaction volumes in 2025 grew to double-digit trillions – approaching Visa and Mastercard combined. That volume requires fraud detection, AML screening, and behavioral intelligence that scales with it.

CB Insights Map Structure

The map organizes 200+ companies into three primary sections, each with multiple subcategories:

• Agentic Trust Infrastructure – Agent observability and evaluation, Agent authentication and authorization (KYA), Agent runtime governance and oversight
• Digital Identity and Verifiable Credentials – Decentralized identity (DID), Passwordless authentication, Post-quantum identity, Know Your Customer (KYC), Biometric identity
• Fraud Detection and Prevention – Fraud orchestration and case management, Risk scoring and signals, AML compliance, AI-generated content detection, On-chain intelligence, Transaction monitoring, Bot detection, Graph analytics and network fraud, Account takeover (ATO) protection

ChainAware sits in the Fraud Detection and Prevention section, specifically in the On-Chain Intelligence subcategory – the most directly Web3-native category on the entire map.

The On-Chain Intelligence Category – Who Made the List

The On-Chain Intelligence subcategory contains eleven companies. Understanding each one – what they do, who they serve, and where they differentiate – establishes the competitive context in which ChainAware operates.

Chainalysis

Chainalysis is the dominant forensic intelligence platform for blockchain – built originally for law enforcement agencies including the FBI, DEA, and IRS. Its Know Your Transaction (KYT) product handles VASP compliance screening, and its investigation tools reconstruct transaction graphs across chains for evidence-grade fund flow analysis. Enterprise pricing ranges from $100,000 to $500,000 annually. Chainalysis is reactive by design: it traces where funds came from after transactions have occurred, which makes it essential for post-incident investigation but structurally unable to prevent fraud before execution. According to Chainalysis’s platform documentation , its clustering heuristics and entity attribution cover hundreds of major counterparties across multiple blockchains.

Elliptic

Elliptic serves a similar VASP compliance use case with a stronger European and institutional focus. Its blockchain analytics cover transaction monitoring, wallet screening, and sanctions compliance for exchanges, banks, and asset managers. Elliptic has expanded into DeFi protocol screening and NFT risk analysis – but remains fundamentally a forensic and compliance tool rather than a predictive intelligence platform.

TRM Labs

TRM Labs occupies the government and financial institution segment with the highest Mosaic score of any company in the On-Chain Intelligence category. Its platform serves FinCEN, OFAC, and major global banks – and has expanded into proactive threat intelligence that goes beyond pure reactive forensics. Spencer Bogart of Blockchain Capital invested in TRM Labs, citing the compliance infrastructure gap as one of the clearest institutional crypto needs.

Crystal Intelligence, Blockaid, and the Remaining Companies

Crystal Intelligence provides blockchain analytics and AML compliance with particular strength in European markets and cross-border transaction monitoring – covering 40+ blockchains. Blockaid approaches on-chain security from a different angle: transaction simulation and malicious dApp detection. Blockaid is now integrated into MetaMask, Coinbase Wallet, and Rainbow – but it protects at the transaction level rather than scoring the behavioral history of the parties behind transactions. Anchain.ai, CUBE AI, Merkle Science, NOTA BENE, and TestMachine occupy specialist positions serving government, institutional, and testing use cases across the category.

ChainAware.ai – The Behavioral Prediction Layer

ChainAware occupies a position in the On-Chain Intelligence category that no other company covers – behavioral prediction. While every other company answers “what has this wallet done or where did these funds come from?”, ChainAware answers “what will this wallet do next, and is this wallet likely to commit fraud before it acts?” That forward-looking prediction capability, combined with being the only Web3 AI token in the full 200-company CB Insights list, makes ChainAware uniquely positioned at the intersection of enterprise compliance and the decentralized token economy.

Why CB Insights Inclusion Matters for Enterprise Buyers

Enterprise procurement decisions for security and compliance infrastructure are significantly influenced by analyst validation. A security or compliance team evaluating on-chain intelligence vendors does not start with a Google search – they start with CB Insights, Gartner, Forrester, or IDC market maps. Inclusion in these maps is the difference between being considered and not being considered in enterprise vendor evaluations.

The Mosaic Score Gate

CB Insights selects companies based on its proprietary Mosaic score – a composite health measure incorporating funding recency, investor quality, web traffic, news sentiment, team quality, and patent activity. The AI Fraud Prevention map requires a Mosaic score above 600 and equity funding since 2024. Most projects in the blockchain space never appear on a CB Insights map because they fail either the Mosaic score threshold or the funding recency requirement. ChainAware’s inclusion confirms that its profile meets institutional investment standards – a signal that matters to the compliance officers, procurement teams, and CISOs who use CB Insights to shortlist vendors.

The Reference Check Effect

When a DeFi protocol’s compliance team receives a proposal from ChainAware, the first thing they do is verify the company’s credibility through third-party sources. The CB Insights listing now serves as that third-party validation – alongside CoinGecko’s AI category listing, the AWARE token on BSC, and ChainAware’s GitHub repository of open-source MIT-licensed agent definitions. Credibility signals compound. Each additional validation source reduces the friction of the enterprise sales cycle and increases the probability of converting enterprise interest into a signed API contract.

The CoinGecko AI Category – 1,385 Tokens, One Web3 AI Fraud Prevention Token

CoinGecko’s AI category currently lists 1,385 tokens – representing the full spectrum of AI-related blockchain projects, from Bittensor (decentralized AI compute) to Render (GPU network) to Virtuals Protocol (AI agent launchpad) to dozens of AI-themed meme coins. The category spans legitimate infrastructure projects, speculative tokens, and everything between.

Among these 1,385 tokens, ChainAware’s AWARE token is the only one building on-chain intelligence and behavioral fraud detection as its core product. None of the major forensic compliance companies – Chainalysis, Elliptic, TRM Labs, Crystal Intelligence – have tokens. None of Blockaid, Anchain.ai, Merkle Science, or NOTA BENE have tokens. They are pure SaaS companies with no token economy.

Why No Token Is the Default for Compliance Companies

Most on-chain intelligence companies avoid tokens for regulatory reasons – a tradeable token creates securities law complexity in most jurisdictions. Chainalysis, TRM Labs, and Elliptic have collectively raised over $1 billion in venture capital while deliberately remaining token-free. Their customers (banks, regulated exchanges, government agencies) cannot hold or use utility tokens as payment. ChainAware’s bifurcated model – enterprise API subscriptions for institutional clients plus the AWARE utility token for Web3 ecosystem participants – allows it to serve both audiences simultaneously without compromising either relationship.

The Unique Intersection

The combination of CB Insights validation and CoinGecko AI category listing creates a position that no competitor occupies. Companies on the CB Insights map without tokens serve institutional clients through SaaS contracts – their distribution is purely through enterprise sales cycles. Companies in the CoinGecko AI category without CB Insights validation are building token economies without institutional credibility. ChainAware sits at the intersection – credible enough for enterprise evaluation and token-native enough to participate in the decentralized economy it analyzes.

How ChainAware Differs From Every Other Company on the Map

Understanding ChainAware’s differentiation requires examining five dimensions where it diverges fundamentally from every other company in the On-Chain Intelligence category.

Dimension 1 – Prediction vs. Forensics

Every other company in the On-Chain Intelligence category is forensic – backward-looking by design. Chainalysis traces where funds came from. Elliptic reconstructs transaction graphs. TRM Labs identifies sanctioned counterparties. Crystal Intelligence monitors cross-border fund flows. All four describe the past. ChainAware predicts the future. Its behavioral ML models, trained on 20M+ wallet personas across 8 blockchains, produce probability scores for what a wallet will do next – not descriptions of what it has done. That prediction happens in milliseconds, before any transaction occurs, based on behavioral patterns that professional fraudsters cannot disguise by using clean contract code.

Dimension 2 – Fraud Tech and Growth Tech Combined

The CB Insights map treats fraud prevention as a purely defensive category – a cost center that organizations pay for to stay compliant and avoid losses. ChainAware reframes the category entirely by combining fraud prevention with growth intelligence in a single platform. ChainAware’s 20M+ wallet personas do not just tell a compliance team whether to block a wallet – they also tell a product team which content to show it, which features to surface, and which growth campaign to trigger. A wallet with high Lend intention and low fraud probability gets surfaced lending products automatically. A wallet with high fraud probability gets blocked before it enters the funnel. Both decisions come from the same behavioral intelligence layer. These same behavioral signals power ChainAware’s 32 ready-made Claude agents, which apply fraud screening and growth targeting directly inside AI agent workflows.

Dimension 3 – MCP-Native Delivery for AI Agents

AI agents need behavioral intelligence delivered in the format they can consume – structured predictions via the Model Context Protocol (MCP), not raw blockchain data that requires further analysis. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for AI agent tool access. ChainAware’s Prediction MCP delivers complete behavioral profiles – fraud probability, all 12 intention scores, experience level, risk appetite, AML status – in a single structured response that any AI agent can act on without blockchain expertise. For how this works in practice, see our Prediction MCP guide .

Dimension 4 – Token-Native Economic Model

ChainAware’s AWARE token creates an economic flywheel that enterprise-only SaaS competitors cannot replicate. Token holders who stake AWARE unlock higher API rate limits and premium intelligence tiers. Developers who build integrations with ChainAware’s API earn AWARE rewards. As the platform’s wallet persona dataset grows – currently at 20M+ profiles – the intelligence quality improves, increasing the value of AWARE access.

Dimension 5 – The Free Entry Point

Chainalysis charges $100,000 to $500,000 annually. TRM Labs requires enterprise negotiations. Elliptic does not publish pricing. ChainAware’s Wallet Auditor delivers the complete Web3 Persona for any address – free, no signup, in under one second. Any developer, compliance officer, or investor can experience the full depth of ChainAware’s behavioral intelligence without a sales conversation. For the complete dimension-by-dimension breakdown, see our Wallet Auditor guide .

Predictive Intelligence vs. Forensic Intelligence – The Critical Distinction

The most important conceptual distinction in the On-Chain Intelligence category is between forensic and predictive intelligence. Understanding this distinction explains why the entire category is funded heavily – and why ChainAware’s predictive position is structurally different from the forensic majority.

What Forensic Intelligence Does

Forensic intelligence analyzes the complete history of blockchain transactions to reconstruct fund flows, identify sanctioned counterparties, and attribute addresses to known entities. It answers: “Where did these funds come from, and who has touched them?” This capability is essential for post-incident investigation. However, forensic intelligence is structurally reactive – it requires the fraud to have already happened, or at minimum for the fraudulent address to already appear in its entity database. A professional operator using a fresh wallet that has never appeared in Chainalysis’s database is invisible to forensic tools until they commit their first recorded offense.

What Predictive Intelligence Does

Predictive intelligence analyzes behavioral patterns – not just transaction histories – to forecast what a wallet will do next and what the probability of fraud is before any transaction executes. ChainAware’s behavioral ML models train on 20M+ wallet personas – learning the behavioral signatures that distinguish legitimate DeFi users from professional fraud operators, Sybil wallets, airdrop farmers, and governance attackers. A professional fraudster can use clean contract code. They cannot mask their behavioral pattern across 20M+ training examples. The model detects the operator, not just the incident. For the complete technical comparison, see our Forensic vs AI-Powered Analytics guide .

The 98% Accuracy Benchmark

ChainAware backtested its fraud detection model on CryptoScamDB – the largest publicly available database of documented crypto fraud incidents – achieving 98% prediction accuracy. The model correctly identified fraudulent wallets before they committed their recorded offense in 98 out of every 100 cases in the test set. For compliance teams operating under MiCA or similar frameworks, that accuracy level dramatically reduces the manual review burden. For the complete MiCA compliance stack, see our MiCA Compliance at 1% of Chainalysis Cost guide .

ChainAware Rug Pull Detector – 90.1% Prediction Accuracy

Rug pulls represent the most damaging category of DeFi fraud by absolute dollar value. ChainAware’s Rug Pull Detector – trained specifically on PancakeSwap V2 data – achieves 90.1% prediction accuracy, identifying high-risk tokens before the rug pull occurs rather than after investors have lost funds.

The PancakeSwap V2 Dataset

ChainAware trained and validated its rug pull detection model on PancakeSwap V2 transaction data from weeks 1 through 20 of 2026 – covering $569 million in documented rug pull losses across thousands of token launches. This dataset is the largest and most recent rug pull training corpus available in the public domain for BNB Chain tokens. The training methodology uses behavioral signals from the contract deployer wallet and all LP providers – not contract code analysis. Professional rug pull operators know exactly which code patterns trigger existing contract scanners, and they code around them. Their behavioral history across 20M+ wallet personas reveals the signature of serial rug operators regardless of how clean their current contract appears.

Rug Pull Detector vs. Competing Tools

GoPlus, Token Sniffer, and Honeypot.is all analyze contract code – detecting known patterns of mint functions, blacklisting mechanisms, sell restrictions, and honeypot logic. These tools catch common scams that reuse known code patterns. They do not catch professional operators who deploy clean code specifically to evade code scanners. ChainAware’s Rug Pull Detector catches what code scanners miss – the experienced operator with a history of rugging who deploys a technically perfect contract but whose behavioral fingerprint across 20M+ personas identifies them as high risk. For the complete comparison, see our Best Web3 Rug Pull Detection Tools guide .

The Agentic Economy and Why It Needs a New Fraud Layer

The CB Insights AI Fraud Prevention Market Map was explicitly timed to coincide with the emergence of the agentic economy – the structural shift from human-operated financial systems to AI-agent-operated ones. Understanding this shift explains why the on-chain intelligence category is the fastest-growing by funding momentum in 2026.

Agents Are Not Humans

AI agents transacting on behalf of humans operate 24/7, across all time zones simultaneously, at machine speed, without the cognitive friction that slows human decision-making. An AI agent does not hesitate before a suspicious transaction – it executes at the speed of the LLM inference cycle. This eliminates the natural fraud prevention that human decision-making provides. Consequently, AI agents need external fraud intelligence to substitute for the human judgment they lack. ChainAware’s Prediction MCP delivers that intelligence in the format agents can consume – structured behavioral profiles via natural language queries, sub-second response, no blockchain expertise required. For integration details, see our 12 Blockchain Capabilities Any AI Agent Can Use .

Haun Ventures’ $1B Thesis – Word for Word

Katie Haun’s Haun Ventures $1 billion fund announcement, published May 4, 2026, contains the most precise description of ChainAware’s product from any institutional source: “Every supporting layer will need to be rearchitected for this world: fraud prevention, credit, insurance, identity, privacy, provenance, reputation, and verification all require native versions designed for how agents transact.” That sentence describes ChainAware’s product roadmap. Haun Ventures is not alone – Dragonfly Capital closed $650 million, a16z crypto closed $2.2 billion, ParaFi Capital raised $125 million – every major fund closing in 2026 has identified the same gap that ChainAware is building into.

The Market Signal – $6B+ in VC Funding Points at the Same Gap

The $6 billion+ deployed into crypto and Web3 infrastructure during the first five months of 2026 is the strongest institutional signal the sector has seen since 2021 – but with a fundamentally different thesis. The 2021 cycle was driven by speculation on token appreciation. The 2026 cycle is driven by infrastructure investment in the trust, compliance, and intelligence layers that the agentic economy requires.

The Fund Closing Timeline

Dragonfly Capital’s $650 million fourth fund closed February 17, 2026. ParaFi Capital’s $125 million raise closed in March 2026, focused on stablecoins, tokenization, and on-chain financial products. Haun Ventures announced $1 billion on May 4, 2026. a16z crypto’s $2.2 billion fifth fund announced May 5, 2026 – bringing its total crypto-focused assets to $9.8 billion. Blockchain Capital is actively raising $700 million. Paradigm’s rumored $1.5 billion includes an AI-plus-crypto thesis. Total confirmed capital: over $4.5 billion closed in the first five months of 2026, with another $2.2 billion in process. Every fund thesis identifies the same three investment areas: new financial infrastructure, new assets and markets, and the agentic economy.

ChainAware as Growth Tech – The Revenue Dimension of On-Chain Intelligence

The CB Insights map positions fraud prevention entirely as a defensive category. ChainAware’s growth tech layer reframes on-chain intelligence as a revenue-generating capability – where the same behavioral data that prevents fraud also drives conversion, retention, and user acquisition efficiency.

The 84% Ghost Wallet Problem

ChainAware’s analysis of 9,999 unique wallet addresses from a major Web3 marketing campaign found that 84% were ghost wallets: zero real engagement, zero meaningful transaction history, zero likelihood of converting into active protocol users. Every dollar spent acquiring ghost wallets is waste – the acquired “user” will never transact, never provide liquidity, never participate in governance, and never generate fee revenue. ChainAware’s growth intelligence layer converts this waste into signal. Before running a campaign, protocols can screen target wallet lists through the Fraud Detector and Wallet Auditor – removing ghost wallets, Sybil clusters, and airdrop farmers from the acquisition pool before spending budget on them. For the complete framework, see our DeFi Onboarding guide .

The 12 Intention Scores as Growth Signals

ChainAware’s 12 behavioral intention scores – Borrow, Lend, Trade, Gamble, NFT, Stake ETH, Stake Yield Farm, Leveraged Staking, Leveraged Staking ETH, Leveraged Lending, Leveraged Long ETH, Leveraged Long Game – are not just risk signals. They are growth signals that tell a protocol exactly which products to surface to each connecting wallet. A wallet with High Lend intention should see lending products featured first. A wallet with Low Experience should see simplified onboarding. Neither wallet needs to self-identify their interests – the behavioral history already tells the protocol everything it needs to know. For the complete growth deployment architecture, see our User Segmentation guide .

Full Competitive Landscape – CB Insights Map Breakdown

The full CB Insights AI Fraud Prevention Market Map covers 200+ companies across six major sections. Understanding the complete map reveals where ChainAware’s behavioral intelligence layer fits within the broader fraud prevention ecosystem – and which categories represent potential integration partners rather than competitors.

Agentic Trust Infrastructure – A Partnership Category

The Agentic Trust Infrastructure section covers agent observability and evaluation (Arize, LangChain, Patronus AI), agent authentication and authorization (xAembit, Arcade, AuthMind, Skyfire), and agent runtime governance (Ciphero, HUMAN, Witness AI). ChainAware’s Prediction MCP is a natural integration layer for all three subcategories – adding on-chain behavioral fraud detection to agent monitoring, authentication, and governance workflows that these platforms currently lack.

Digital Identity – Complementary, Not Competing

The Digital Identity section covers decentralized identity (DID), passwordless authentication, post-quantum identity, KYC, and biometric identity. Companies like Humanity Protocol, Billions, Self, and zkMe provide proof-of-personhood and verifiable credentials – confirming that a wallet is controlled by a unique human. DID systems answer “is this wallet controlled by a unique person?” ChainAware answers “is this person’s behavior consistent with fraud – and what will they do next?” These questions are complementary, not overlapping. For how ChainAware integrates with DID systems, see our Blockchain Compliance guide .

AML Compliance – The Enterprise Complement

The AML compliance subcategory includes Amlyze, Comply Advantage, Fiverity, Hawk AI, Natech, and Sphinx – all providing transaction monitoring and AML reporting for regulated financial institutions. ChainAware’s AML screening and behavioral fraud detection complement these platforms rather than replacing them. Enterprise AML systems provide regulatory reporting, case management, and audit trails. ChainAware provides the pre-execution risk signal that determines which transactions require closer AML review. For the complete DeFi compliance stack, see our DeFi Compliance Tools guide .

How to Use ChainAware’s Intelligence Products Today

All three ChainAware intelligence products are available without signup, without wallet connection, and without a sales conversation. The free tier delivers the complete product – not a limited preview.

Rug Pull Detector

Navigate to chainaware.ai/rug-pull-detector . Paste any ERC-20 or BEP-20 token contract address. The detector returns a rug pull probability score, a breakdown of the risk factors identified, and a behavioral assessment of the contract deployer and LP providers. Results are available in under 3 seconds. No account required. Use it before buying any new token – especially on BNB Smart Chain where the $569 million PancakeSwap V2 dataset gives the model its highest accuracy. For the full methodology behind this scoring, see the Rug Pull Detector learn page.

Fraud Detector

Navigate to chainaware.ai/fraud-detector . Paste any wallet address. The detector returns fraud probability (98% accuracy), AML status, OFAC screening result, and a behavioral summary. Covers ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, and SOL. Results are available in under 1 second. No account required. Use it to screen wallets before approving DeFi protocol interactions and to verify team wallet addresses published by new token projects. Full scoring methodology is documented on the Fraud Detector learn page.

Wallet Auditor

Navigate to chainaware.ai/audit . Paste any wallet address. The Wallet Auditor returns the complete 22-dimension Web3 Persona: fraud probability, all 12 intention scores, experience level, risk appetite, AML status, OFAC screening, Wallet Rank, wallet age, transaction count, and balance. For the complete guide, see our Wallet Auditor guide . The full 22-dimension methodology is also documented on the Wallet Auditor learn page.

API Access and Prediction MCP

For teams integrating ChainAware intelligence at scale, the REST API provides full access to all intelligence products at volume. The Prediction MCP server at prediction.mcp.chainaware.ai/sse delivers complete behavioral profiles to any MCP-compatible AI agent in under 1 second. API documentation is available at swagger.chainaware.ai. For setup instructions and the full tool list, see the Prediction MCP learn guide.

Frequently Asked Questions

What is the CB Insights AI Fraud Prevention Market Map?

The CB Insights AI Fraud Prevention Market Map, published June 2, 2026, identifies 200+ companies building identity, trust, and fraud prevention infrastructure for the AI era. CB Insights selects companies based on Mosaic health scores above 600 and equity funding since 2024. ChainAware appears in the On-Chain Intelligence subcategory – alongside Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, and Blockaid – as the only Web3 AI token in the full list.

Why is ChainAware the only Web3 AI token in the CB Insights list?

Most on-chain intelligence companies – Chainalysis, Elliptic, TRM Labs, Crystal Intelligence, Blockaid – are pure SaaS businesses with no publicly traded token. They serve regulated institutional clients who cannot hold utility tokens, and they avoid tokens for regulatory complexity reasons. ChainAware’s bifurcated model – enterprise API subscriptions for institutional clients plus the AWARE utility token for Web3 ecosystem participants – allows it to appear in both institutional and decentralized discovery channels simultaneously.

How does ChainAware’s 90.1% rug pull accuracy compare to other tools?

GoPlus, Token Sniffer, and Honeypot.is analyze contract code – they do not publish accuracy statistics because they report risk flags rather than probability scores. ChainAware’s 90.1% accuracy is a backtested performance metric on the PancakeSwap V2 dataset covering $569 million in documented rug pulls from weeks 1 through 20 of 2026. The key distinction is that ChainAware’s model analyzes behavioral history of the contract deployer and LP providers – catching professional operators who deploy clean code to evade code scanners. For detailed methodology, see our Rug Pull Detection guide .

What is the difference between ChainAware and Chainalysis?

Chainalysis is a forensic compliance platform designed for law enforcement and regulated exchanges – it traces where funds came from after transactions have occurred, with enterprise pricing from $100,000 to $500,000 annually. ChainAware is a predictive behavioral intelligence platform designed for DeFi protocols, AI agents, and compliance teams – it predicts fraud before transactions execute, with a free tier and accessible API pricing. The two are complementary: Chainalysis provides post-incident forensics; ChainAware provides pre-execution fraud prevention. For the complete cost comparison, see our MiCA Compliance at 1% of Chainalysis Cost guide .

How does the Prediction MCP work for AI agents?

ChainAware’s Prediction MCP server is accessible at prediction.mcp.chainaware.ai/sse. Any MCP-compatible AI agent – Claude, GPT, or any other LLM – can connect to the MCP and query behavioral profiles via natural language. The agent sends a query such as “What is the fraud risk and behavioral profile of 0x2f71…?” and receives a structured response containing fraud probability, all 12 intention probabilities, experience level, risk appetite, AML status, and Wallet Rank – all pre-computed, in under one second. According to Anthropic’s MCP documentation , MCP is becoming the standard for AI agent tool access. For the integration guide, see our Prediction MCP guide .

Can ChainAware detect governance attacks before they execute?

Yes – governance attack detection is one of ChainAware’s most differentiated capabilities. DAO governance attacks typically use Sybil wallet clusters – coordinated addresses that each hold small token amounts and vote together to achieve disproportionate governance influence. ChainAware’s behavioral model detects these clusters by identifying wallets that share funding sources, exhibit synchronized transaction timing, and demonstrate consistent co-voting behavior across multiple governance proposals. For the complete governance attack detection framework, see our Web3 Governance Screeners guide .

How does ChainAware’s behavioral intelligence help with MiCA compliance?

MiCA (Markets in Crypto-Assets Regulation) requires crypto asset service providers operating in the EU to implement transaction monitoring, AML screening, and customer risk assessment. ChainAware’s Fraud Detector and AML screening cover the pre-execution risk assessment requirement – delivering 98% accurate fraud probability and real-time AML/OFAC screening for every wallet interacting with a MiCA-covered service. According to FATF’s Virtual Assets Recommendations , transaction monitoring requirements increasingly mandate real-time screening capabilities. For the complete implementation guide, see our DeFi Compliance Tools guide .

What makes ChainAware’s position in CoinGecko’s AI category strategically valuable?

CoinGecko’s AI category receives millions of views monthly from users specifically searching for AI-related blockchain investments and infrastructure. Being the only on-chain intelligence and behavioral fraud detection project among 1,385 tokens creates a discovery advantage that pure enterprise SaaS competitors cannot replicate. A developer researching AI-native blockchain tools who browses the CoinGecko AI category finds ChainAware as the only fraud intelligence and behavioral scoring option – without competition from Chainalysis, Elliptic, or TRM Labs who have no token presence. The combination of institutional validation from CB Insights and retail discovery via CoinGecko creates a dual-channel visibility that no competitor in either ecosystem can match.

External Sources: CB Insights AI Fraud Prevention Market Map · CoinGecko AI Category · Anthropic Model Context Protocol · FATF Virtual Assets Recommendations · Chainalysis Platform

The post ChainAware.ai Named in CB Insights AI Fraud Prevention Market Map – The Only Web3 AI Token in the List first appeared on ChainAware.ai.

103,695 separate rug pull events. $1,947,176,810 in liquidity removed by contract creators. $1,377,788,426 added before removal. The difference – $569,388,384 – flowed directly out of retail wallets and into the pockets of fraudulent actors operating industrial-scale extraction infrastructure on one of the world’s largest decentralized exchanges. Every single week. Quietly. Without ceremony.

This is the rug pull industry. Not a bug. An industry.

Today, ChainAware.ai publishes this data for the first time – and simultaneously launches Rug Pull Detector V3, our most advanced version yet, with 90.1% prediction accuracy achieved by combining behavioral analysis of contract creators with full smart contract inspection. This is the complete picture: what the data shows, why nobody talks about it, how the extraction machinery works, and how to stop it.

In This Guide

• The $569M Dataset: What We Measured and How
• Week-by-Week Breakdown: 20 Weeks of Retail Extraction
• The Industry Silence Problem: Why Nobody Talks About Rug Pulls
• How Rug Pulls Work: The Mechanics of Liquidity Extraction
• Beyond Basic Rug Pulls: The More Complex Extraction Methods We Did Not Count
• Rug Pull Detector V3: From 68% to 90.1% Prediction Power
• How the V3 Algorithm Works: Behavioral + Smart Contract Analysis
• Algorithm Verification and Accuracy Methodology
• Who Uses Rug Pull Detector: Retail Investors, Businesses, and AI Agents
• Projection: How Many Rug Pulls in the Next 20 Weeks?
• The Complete Protection Stack for DApps and Retail Investors
• Frequently Asked Questions

The $569M Dataset: What We Measured and How

ChainAware analyzed every liquidity event on PancakeSwap V2 across weeks 1 through 20 of 2026. The methodology is deliberately conservative. We measured only the most basic, unambiguous form of rug pull: a contract creator adds liquidity to a pool, then removes more than they added. The difference between liquidity added and liquidity removed – when removal exceeds addition – constitutes the rug pull value we report.

This definition intentionally excludes more sophisticated extraction methods. Complex multi-step schemes involving LP token transfers, associated wallet sell-offs, and unlocked token dumps are not included in these numbers. The $569M figure represents the floor – the minimum provably fraudulent extraction we could measure with mathematical certainty from on-chain data alone.

The full dataset covers:

• Total rug pull events detected: 103,695
• Total liquidity added by creators (Mints): $1,377,788,426
• Total liquidity removed by creators (Burns): $1,947,176,810
• Net extraction (Burns minus Mints): $569,388,384
• Period: Week 1 through Week 20, 2026
• Exchange: PancakeSwap V2 (BNB Chain)

PancakeSwap V2 on BNB Chain is one of the highest-volume decentralized exchanges in the world. It is also, by our measurement, one of the largest venues for systematic retail investor fraud. The combination of low gas fees, high token creation velocity, and large retail liquidity makes BNB Chain the preferred operating environment for industrial-scale rug pull operations.

For context on just how large this ecosystem of fraud is: the Bybit hack in February 2025 – which generated enormous industry coverage, emergency response coordination, and weeks of Twitter discussion – extracted $1.46 billion. Our 20-week PancakeSwap V2 measurement represents 39% of that headline-grabbing figure. On one DEX. In one 20-week window. With virtually zero media coverage.

Week-by-Week Breakdown: 20 Weeks of Retail Extraction

The weekly data reveals patterns that any serious analyst of DeFi fraud should study carefully. Rug pull activity is not random noise. It follows detectable rhythms tied to market sentiment, BNB price movements, and the operational cadence of the fraud factories running these schemes.

What the Weekly Patterns Tell Us

Four distinct patterns emerge from careful analysis of this 20-week dataset. Each pattern carries significant implications for how rug pull operations are structured and how retail investors can protect themselves.

Pattern 1 – Early surge, then stabilization: Weeks 1 through 5 represent the highest-intensity period, with Week 4 peaking at $53.4M in a single week. This early-year surge correlates with January-February market optimism, when retail capital flows into DeFi most aggressively following holiday periods. Fraud operators know this and deploy capital accordingly.

Pattern 2 – Persistent baseline fraud: Even in quieter weeks (W8, W17, W18, W19), fraud never drops to zero. The range of $12.6M to $16.7M represents what we call the baseline rug pull floor – the irreducible minimum level of extraction that persists regardless of market conditions. These weeks demonstrate that rug pulls are not opportunistic responses to bull markets. They are a continuous, professionally operated business.

Pattern 3 – Pool creation velocity diverging from fraud events: Week 2 shows the highest pool creation (24,145 total pools) but does not produce the highest fraud value. Week 4 shows far fewer pools (17,984) but delivers the peak fraud extraction. This divergence suggests that fraud operators optimize for pool value, not pool volume – they are creating fewer but more lucrative pools rather than flooding the market with low-value scam tokens.

Pattern 4 – Week 20 resurgence: After a six-week decline from W14 through W19, Week 20 spikes back to $39.9M – the second-highest single-week figure in the dataset. This resurgence suggests cyclical fraud campaigns that compress activity during low-sentiment periods and re-accelerate when retail interest returns. The Week 20 data point is a leading indicator, not an anomaly.

The Industry Silence Problem: Why Nobody Talks About Rug Pulls

Here is a question worth sitting with: Why does a $1.46B exchange hack generate hundreds of articles, emergency response calls, and weeks of industry-wide discussion – while $569M in retail losses across 20 weeks generates almost no coverage at all?

The answer is structural. Exchange hacks are dramatic, concentrated, and attributable. They happen to institutions – Bybit, Binance, Euler Finance – that have PR teams, legal counsel, and market presence. Rug pulls happen to anonymous retail investors, dispersed across thousands of small transactions, with no single victim large enough to command media attention and no single perpetrator identifiable enough to pursue.

$53.4M stolen from a major exchange in a single transaction is a crisis. $53.4M stolen from 6,000 retail investors across thousands of micro-transactions in a single week is business as usual. The victims are too distributed to organize. The fraud is too normalized to shock. The perpetrators are too anonymous to name.

This structural invisibility benefits the rug pull industry enormously. Unlike hacks – which trigger security audits, insurance claims, regulatory investigations, and protocol upgrades – rug pulls operate in a consequence-free zone. The operators who ran this week’s $28M extraction will run next week’s extraction with identical infrastructure. Nothing stops them. Nobody is watching. The industry is busy discussing the latest Layer 2 throughput numbers.

The Chainalysis 2025 Crypto Crime Report documents $17 billion in total crypto scam losses – a figure that includes rug pulls, phishing, fake investments, and other fraud categories. Rug pulls constitute one of the largest subcategories within this total, yet they receive proportionally far less analytical attention than flash loan exploits, bridge hacks, and protocol vulnerabilities.

Part of the problem is that rug pulls do not fit the traditional Web3 security narrative. Security firms make revenue from smart contract audits, not from behavioral fraud detection. Media outlets generate traffic from dramatic hacks, not from steady-state extraction statistics. Influencers amplify projects that pay them, not warnings that might upset project teams with marketing budgets. The incentive structure of the crypto information ecosystem systematically underweights the most consistent form of retail harm.

ChainAware exists, in part, to change this. Publishing this data is the first step. Building tools that let retail investors and DApps verify tokens and pools before committing capital is the second. For a broader perspective on the comparison between rug pulls and pump-and-dump schemes and how each extracts value from retail investors, our dedicated guide covers the full mechanics of both fraud types.

How Rug Pulls Work: The Mechanics of Liquidity Extraction

Understanding rug pull mechanics is the foundation of avoiding them. The basic liquidity rug pull – the type we measured in this dataset – follows a repeatable, five-step operational sequence that any investor can learn to recognize.

Step 1: Token and Pool Creation

A fraudulent actor deploys a new ERC-20 or BEP-20 token contract. On BNB Chain, this costs a fraction of a dollar and takes minutes. The token contract typically includes mint functions (allowing the creator to generate unlimited supply), hidden transfer restrictions (preventing buyers from selling), and ownership functions that are often not renounced. The pool is created on PancakeSwap V2 by pairing the new token with BNB or USDT, establishing an initial price.

Step 2: Liquidity Seeding

The creator deposits initial liquidity – real BNB or USDT – into the pool alongside the worthless token they created. This establishes a tradeable pair and makes the token appear legitimate on DEX aggregators and portfolio trackers. The liquidity seed is the bait. It represents the money the fraudster is temporarily risking to attract retail capital.

Step 3: Marketing and Social Momentum

Telegram groups are created. Twitter accounts post about the new token. Sometimes influencers are paid to promote it. Bots generate artificial trading volume to make the token appear active. Retail investors see a token with real liquidity, active trading, and social proof – and buy in. Each purchase increases the price and deepens the liquidity pool with real capital.

Step 4: Liquidity Removal

Once sufficient retail capital has entered the pool, the creator burns their LP tokens – withdrawing all liquidity from the pool. This single transaction extracts all the BNB or USDT that retail investors deposited when they bought the token. The token price drops to zero instantly. Holders are left with worthless tokens that cannot be sold. The creator walks away with the full liquidity amount, minus their initial seed deposit. The difference is pure profit extracted from retail investors.

Step 5: Repeat

Professional rug pull operators do not run one scheme. They run dozens simultaneously, across multiple wallets, with industrialized tooling that automates contract deployment, social media posting, and liquidity management. The 103,695 rug pull events in our dataset represent the output of a mature industry with operational infrastructure comparable to a sophisticated affiliate marketing operation – except the product being sold is fraud.

Beyond Basic Rug Pulls: The More Complex Extraction Methods We Did Not Count

Our $569M figure covers only the most conservative, mathematically verifiable form of rug pull: direct liquidity removal exceeding direct liquidity addition, by the same contract creator. This definition was chosen deliberately – it produces numbers that cannot be disputed, because they are derived purely from on-chain transaction data with no inferential assumptions.

However, professional rug pull operators frequently use more sophisticated extraction methods that our current measurement excludes. Understanding these methods matters for two reasons: first, because they represent additional losses not captured in the $569M figure; second, because ChainAware’s Rug Pull Detector V3 is being extended to detect these more complex patterns in future iterations.

LP Token Transfer Rug Pulls

Instead of burning LP tokens directly, the creator transfers them to a secondary wallet before burning. This adds one intermediary step that breaks the direct creator-to-burn attribution our basic methodology requires. The economic outcome is identical – retail liquidity is extracted – but the attribution chain is one step longer. Detecting this pattern requires tracking LP token ownership across wallets, not just monitoring mint/burn events on the original creator address.

Unlocked Token Sell-Offs

Some rug pulls never involve liquidity removal at all. Instead, the creator holds a large pre-minted supply of unlocked tokens and sells them gradually into the market as retail buyers push the price up. This is the “slow rug” – a controlled sell-off that extracts value over days or weeks rather than in a single transaction. Detecting this requires monitoring creator wallet sell behavior relative to price action, not liquidity pool events.

Associated Party Extraction

Sophisticated operators fund multiple secondary wallets that receive token allocations at launch and sell into retail buying pressure. The creator’s primary wallet never transacts after the initial liquidity seed – only associated wallets do. Connecting these wallets to the creator requires graph analysis of funding transactions, not just monitoring of the deployer address.

Honeypot Contracts

A honeypot is a contract that allows buying but blocks selling. Transfer restrictions embedded in the contract – hidden from Etherscan views unless you know where to look – prevent token holders from executing sell transactions. Buyers accumulate tokens they cannot sell, while the creator sells their pre-minted allocation freely. GoPlus Security detected 67,241 honeypot tokens in Q4 2024 alone – a figure that underscores the scale of this specific fraud variant. For a full comparison of rug pull detection tools that cover honeypot analysis, see our guide to best Web3 rug pull detection tools in 2026.

The conservative $569M figure – our confirmed minimum – would be substantially higher if all these additional extraction methods were included. ChainAware’s V3 algorithm already incorporates smart contract analysis that can detect honeypot patterns and some forms of unlocked token sell-off risk. Future iterations will extend this coverage further.

Rug Pull Detector V3: From 68% to 90.1% Prediction Power

The previous version of ChainAware’s Rug Pull Detector operated at approximately 68% prediction accuracy. For retail investors, that accuracy level is better than nothing – significantly better than the zero-analysis approach most investors use. However, 68% means that roughly one in three high-risk pools would pass the detector without a warning, and some legitimate pools would trigger false positives.

Our customers asked directly: can we do better? The answer is V3 – and the answer is yes.

ChainAware Rug Pull Detector V3 achieves 90.1% prediction accuracy. This jump from 68% to 90.1% represents a 32.5% relative improvement in prediction power – the largest single-version upgrade in the detector’s history. The improvement comes from a fundamental architecture change: V2 relied exclusively on behavioral analysis of contract creators. V3 combines behavioral analysis with full smart contract inspection.

Why the V2 Accuracy Gap Existed

Behavioral analysis alone – examining the on-chain history of the wallet that deployed a contract – is a powerful signal, but it has a ceiling. Experienced fraud operators know that behavioral signals can be spoofed. They create fresh wallets with clean histories. They fund deployer wallets through legitimate channels. They space out deployments to avoid clustering signals that behavioral models flag.

A behavioral model trained purely on creator wallet history will inevitably miss sophisticated operators who invest in maintaining clean deployer identities. This is the category that the 32% gap in V2 accuracy primarily represented. The false negatives were concentrated in professional, well-organized fraud operations – precisely the operators responsible for the largest individual rug pull events.

What V3 Adds: Smart Contract Analysis

Smart contract analysis reads the code of the contract itself – not just the history of the wallet that deployed it. Regardless of how clean a deployer wallet’s history looks, a contract with hidden mint functions, owner-only transfer restrictions, or unchecked liquidity lock mechanisms will trigger V3’s contract analysis layer.

This combination closes the gap that sophisticated fraud operators had exploited in V2. A fraudster who maintains a clean wallet but deploys a honeypot contract now triggers the smart contract analysis layer even when the behavioral analysis layer returns a clean signal. Conversely, a wallet with minor behavioral flags but a fully transparent, auditable contract receives a more accurate risk assessment that prevents false positives on legitimate projects.

The 90.1% accuracy figure represents the combined performance of both layers together – it is the V3 ensemble model’s prediction power, not either layer in isolation. The algorithm remains under active development. We expect accuracy to continue improving as the training dataset expands and additional smart contract analysis patterns are incorporated.

How the V3 Algorithm Works: Behavioral + Smart Contract Analysis

V3 runs two parallel analysis pipelines that produce independent risk scores, then combines them through an ensemble model trained on verified historical rug pull events. Both pipelines run in real time – the full analysis completes in under two seconds for any pool or token address submitted to the detector.

Pipeline 1: Creator Behavioral Analysis

The behavioral analysis pipeline examines the complete on-chain history of the wallet that deployed the contract. ChainAware’s 20M+ wallet persona database, trained across 8 blockchains, provides the foundation for this analysis. The pipeline evaluates multiple behavioral dimensions that collectively predict fraudulent intent:

• Deployment history: How many contracts has this wallet deployed? What is the historical fate of those contracts – did their pools maintain liquidity or were they rugged?
• Funding provenance: Where did the capital to seed liquidity originate? Wallets funded from known mixer outputs, fresh exchange withdrawals, or clusters of associated addresses receive elevated risk scores.
• Creator feeder analysis: Wallets that funded the deployer are also examined. A deployer wallet with a clean history but funded by a wallet with prior rug pull associations triggers a feeder-chain risk signal.
• Temporal patterns: How quickly after token deployment was liquidity removed in prior contracts from this wallet or associated wallets? Short hold periods are a strong predictor of rug pull intent.
• Wallet age and diversity: Fresh wallets with minimal on-chain history and a single purpose (token deployment and liquidity management) score significantly higher than wallets with years of diverse on-chain activity.

This behavioral layer is powered by the same predictive intelligence that drives ChainAware’s broader wallet analysis capabilities. For context on how the underlying wallet behavioral analysis works across other use cases, our guide to using the ChainAware Wallet Auditor covers the full 9-parameter profile in detail. The full methodology behind this deployer-level scoring is also documented on the Rug Pull Detector learn page.

Pipeline 2: Smart Contract Analysis

The smart contract analysis pipeline inspects the deployed contract code directly. For verified contracts (where source code is published), the analysis performs AST (Abstract Syntax Tree) parsing – examining the structural logic of the contract to identify dangerous patterns. For unverified contracts, bytecode inspection is used to detect characteristic opcode sequences associated with honeypot restrictions and hidden mint functions.

The contract analysis examines specific risk patterns:

• Hidden transfer restrictions: Functions that block selling by non-owner addresses, often disguised within complex conditional logic that is not obvious from casual code review.
• Owner-privileged mint functions: Unrestricted mint capabilities controlled by the deployer allow infinite token supply expansion after retail investors have bought in.
• Ownership renouncement status: Contracts that have not renounced ownership retain the ability to modify transfer restrictions, fee structures, and other parameters after launch.
• Liquidity lock verification: Whether LP tokens are locked – and in what contract, with what unlock conditions – is a critical signal. Unlocked LP tokens in the deployer’s wallet represent immediate rug pull risk.
• Fee manipulation functions: Contracts with owner-callable functions to increase buy/sell taxes after launch can effectively trap investors by making selling economically unviable.

For additional context on how AI-powered smart contract analysis compares to traditional audit approaches, our guide to AI-powered blockchain analysis and machine learning for crypto security covers the broader landscape of ML-based fraud detection.

The Ensemble Model

Outputs from both pipelines feed into an ensemble model that produces a single composite risk score between 0 and 100. Scores above 75 trigger a high-risk warning. Scores between 50 and 75 generate a medium-risk flag with specific risk factors highlighted. Scores below 50 return a lower-risk assessment – though not a guarantee of legitimacy, since the algorithm continues to develop and some novel fraud patterns may not yet be captured.

The ensemble model is trained on a labeled dataset of confirmed rug pull events – including events from the 103,695 cases in our PancakeSwap V2 analysis – and updated continuously as new rug pull events are confirmed. This continuous retraining is what allows the algorithm to adapt to evolving fraud operator tactics rather than becoming outdated as the fraud industry develops new evasion methods.

Algorithm Verification and Accuracy Methodology

The 90.1% accuracy figure requires explanation of its methodology, because prediction accuracy claims in the crypto security space are frequently made without rigorous verification frameworks. ChainAware’s accuracy is measured against historical confirmed rug pull events using a held-out test set – contracts and pools that were not included in the training data but whose eventual rug pull status is now known.

Full verification methodology, including the test set composition, evaluation metrics, false positive and false negative rates by pool type, and comparison to V2 baseline performance, is published at chainaware.ai/resources/rugpull-verification ↗.

Three important caveats about the 90.1% figure deserve explicit statement:

Caveat 1 – The algorithm is in active development. 90.1% is the current measured performance. We expect this number to improve. We also acknowledge that novel fraud patterns not yet present in our training data could temporarily reduce real-world performance below this benchmark.

Caveat 2 – False negatives exist. Roughly 9.9% of rug pull events will not be flagged by V3. These are concentrated in the most sophisticated fraud operations – those that maintain clean creator wallets and deploy contracts that pass automated inspection. Human review of tokenomics, social channels, and team identity remains important for high-value investment decisions.

Caveat 3 – False positives also exist. Some legitimate projects will receive elevated risk scores, particularly those deployed by newer wallets without extensive on-chain history or those using novel contract architectures that match patterns we associate with fraud. V3 is designed to flag risk, not to definitively declare fraud – the final investment decision always rests with the human investor.

For comparison with how other detection tools benchmark their accuracy, the broader context of the forensic versus AI-powered blockchain analysis framework explains why predictive accuracy figures differ fundamentally from forensic identification rates.

Who Uses Rug Pull Detector: Retail Investors, Businesses, and AI Agents

ChainAware’s Rug Pull Detector V3 serves three distinct user categories, each with different integration paths and use case requirements.

Retail Investors: Free Web Tool

Individual investors access the Rug Pull Detector at no cost through the web interface at chainaware.ai/rugpull. No account creation is required. Submit any pool address or token contract address on supported chains, and V3 returns a complete risk analysis within seconds. The tool handles both liquidity pool addresses (where additional LP-specific checks run) and regular token contract addresses.

For retail investors who want to go beyond rug pull risk and understand the complete behavioral profile of any wallet – including their own – the ChainAware Wallet Auditor provides a 9-parameter profile covering experience, risk willingness, intentions, AML status, and Wallet Rank. Both tools are free and require no signup. The full profile methodology is documented on the Wallet Auditor learn page.

DApps and Businesses: API Subscription

Businesses that need to check new pools or existing tokens at scale – DEX aggregators, portfolio trackers, launchpads, DeFi protocols – can subscribe to the Rug Pull Detector API. The API provides the same V3 analysis through a programmatic interface, enabling integration into existing DApp infrastructure without requiring users to manually submit addresses.

For DApps that want to screen wallet connections in real time – catching bad actors at the moment of wallet connection rather than at the moment of investment – the broader ChainAware suite integrates via Google Tag Manager pixel with zero code changes. See the complete Transaction Monitoring Agent guide for how automatic wallet screening works in a live DApp environment.

DApps that want to understand not just fraud risk but the full behavioral profile of their user base – their intentions, experience levels, and conversion likelihood – can combine the Rug Pull Detector API with ChainAware’s Web3 Behavioral User Analytics for a complete picture of who is using their platform and which users represent fraud risk versus conversion opportunity.

AI Agents: X402 Micropayment Protocol

AI agents operating autonomously in DeFi environments – executing trades, managing portfolios, or conducting due diligence on behalf of human principals – can access Rug Pull Detector V3 through the X402 micropayment protocol. This enables agents to pay per analysis in real time without requiring pre-approved API keys or subscription agreements.

An agent evaluating whether to provide liquidity to a new pool, or whether to purchase a newly launched token as part of a portfolio strategy, can query V3 and receive a risk assessment as part of its decision-making pipeline. This integration pattern – AI agents using on-chain behavioral intelligence to make better decisions – is the core use case that ChainAware’s MCP integration guide covers in detail, and the full setup process is documented on the Prediction MCP learn page. For the complete framework of how AI agents are replacing human functions in Web3, our guide to the Web3 agentic economy provides essential context.

Projection: How Many Rug Pulls in the Next 20 Weeks?

Based on the 20-week dataset, what does the next 20-week period look like? This is not a rhetorical question. The data provides enough signal to make a structured projection.

The Baseline Projection

Averaging the 20 weeks of data gives a mean weekly rug pull extraction of approximately $28.5M (total $569.4M divided by 20 weeks). If the next 20 weeks perform at the historical mean, the projected extraction would be approximately $570M – virtually identical to the first 20-week period.

However, averages obscure the variance that makes this projection more nuanced. Week 17 produced just $12.6M. Week 4 produced $53.4M. The range is wide – and what drives the range matters for any forward projection.

Bull Market Scenario

If BNB and the broader crypto market experience a significant price rally in the next 20 weeks, retail capital inflows to PancakeSwap V2 will increase. More retail capital entering DEX pools means more capital available for extraction. In a bull market scenario, weekly extraction figures could return to the W3-W5 range ($38M-$53M per week), pushing the 20-week total toward $800M-$900M.

Bear Market Scenario

Sustained market decline reduces retail participation in speculative DeFi activity. The W16-W19 pattern – four consecutive low weeks averaging $15M – represents what a low-sentiment environment looks like. In a bear market scenario, the next 20-week total could fall to $250M-$350M.

The Conservative Certainty

Regardless of market direction, one conclusion is near-certain: rug pulls will continue to extract hundreds of millions of dollars from retail investors in the next 20 weeks. The fraud infrastructure exists, is profitable, and faces no meaningful deterrent. The floor established by the W17-W19 data ($12.6M-$15.1M per week) implies a minimum 20-week extraction of approximately $250M under the most pessimistic scenario.

The only variable the industry controls is how many investors check tokens and pools before buying – and how accurate those checks are. That is the market for Rug Pull Detector V3.

The Complete Protection Stack for DApps and Retail Investors

Rug pull detection is one layer of a complete Web3 fraud protection stack. Understanding where it sits relative to other security tools helps both retail investors and DApp teams build comprehensive protection rather than relying on any single tool.

For Retail Investors: The Three-Check Protocol

Before committing capital to any new token or pool, a thorough retail investor runs three checks. First, they use ChainAware’s Rug Pull Detector to assess the pool or token’s fraud risk – covering both creator behavior and contract analysis. Second, if the rug pull check flags concerns, they use the Fraud Detector to drill into the specific wallets associated with the token deployment. Third, before sending funds to any individual wallet address, they use the Wallet Auditor to assess the receiving address’s behavioral profile and AML status.

This three-check approach takes less than five minutes per investment decision and provides protection against the most common forms of DeFi fraud. It will not catch every sophisticated attack – nothing will – but it filters out the vast majority of the 103,695 rug pull events in our dataset, which are predominantly straightforward enough to be detected by V3’s behavioral and contract analysis.

For a complete understanding of the crypto security landscape and how different tools protect against different threat vectors, the guide to crypto wallet security in 2026 covers hardware wallets, behavioral intelligence, and fraud prevention in a single comprehensive framework.

For DApps: Pre-Connection Screening

DApps face a different version of the rug pull problem: they are not the ones buying potentially fraudulent tokens, but they are being used as distribution channels by users who may have funded their activity through fraud proceeds. A DApp that allows a rug pull operator to use its interface for withdrawals or swaps becomes part of the fraud infrastructure – and faces potential compliance exposure under FATF guidelines and MiCA regulations.

ChainAware’s DApp protection layer screens connecting wallets at the moment of wallet connection – before any transaction is submitted. Wallets associated with known rug pull contracts, flagged behavioral patterns, or AML-positive addresses are identified at the connection stage and can be blocked, flagged for review, or routed to restricted functionality automatically. The full architecture of this pre-connection screening is covered in our guide to Web3 fraud detection for DApps in 2026.

For DApps operating under MiCA requirements, ChainAware’s compliance layer provides 70-75% MiCA coverage at approximately 1% of the cost of traditional compliance solutions from Chainalysis or Elliptic. The complete comparison of DeFi compliance tools and costs is available in our DeFi compliance tools comparison for 2026.

The AML Layer: Complementary, Not Overlapping

AML screening and rug pull detection address different risk vectors. AML screening asks: is this wallet associated with known illicit activity – sanctions lists, mixer usage, dark web transactions? Rug pull detection asks: is this contract creator likely to extract liquidity before investors can exit?

These questions are complementary. A wallet can be AML-clean but behaviorally likely to rug – a fresh wallet with no prior illicit associations but a clear deployment pattern matching rug pull operators. Conversely, a wallet can trigger AML flags without being involved in rug pulls – a legitimate DeFi user who passed through a mixer for privacy reasons, for instance.

Running both checks provides the most comprehensive protection. For the complete technical architecture of AML and KYT compliance for DeFi, our guide to blockchain compliance, KYT, and AML for DeFi in 2026 covers the regulatory obligations and implementation options for protocols of all sizes. Additionally, for protocols evaluating predictive AI versus traditional rule-based approaches for compliance, our analysis of predictive AI for crypto KYC, AML, and transaction monitoring provides a direct comparison.

PancakeSwap V2 Specifically: Why BNB Chain Is Ground Zero for Rug Pulls

PancakeSwap V2 on BNB Chain represents an ideal operational environment for rug pull schemes. Understanding why helps investors calibrate their risk exposure appropriately when interacting with BNB Chain DeFi specifically.

BNB Chain gas fees are among the lowest of any major EVM-compatible chain. Deploying a token contract, creating a PancakeSwap V2 pool, and seeding initial liquidity can cost less than $5 in total gas fees. This near-zero barrier to entry means that fraud operators can deploy hundreds of rug pull setups simultaneously at negligible marginal cost. A single successful extraction – even of a few thousand dollars – covers the cost of dozens of attempted schemes.

PancakeSwap V2 also benefits from extremely high organic retail traffic. Hundreds of thousands of retail investors use PancakeSwap V2 daily, creating a large pool of potential victims for each fraudulent token. The PancakeSwap interface itself presents tokens without any fraud risk warnings – it is a neutral trading interface, not a security layer. The responsibility for fraud detection falls entirely on the investor.

Token aggregators like DexTools and DexScreener surface newly created pools with real-time price charts, trading volume, and holder counts – all of which can be manipulated through bot trading and wash volume. A fresh pool with manufactured trading activity looks identical to a legitimate new project on these interfaces. Retail investors using aggregators as their primary research tool are working with data that fraud operators have specifically optimized to deceive.

CertiK’s 2025 security data placed BNB Chain consistently among the top chains for exit scam and rug pull activity, a position it has held across multiple annual reporting periods. The combination of low costs, high traffic, and minimal native protection makes BNB Chain the most active venue for the rug pull industry globally.

This is not a criticism of BNB Chain or PancakeSwap as infrastructure. Both are legitimate, high-quality platforms. The fraud problem is an emergent consequence of their success – high retail traffic and low costs that serve legitimate users equally serve fraudulent ones.

What the Rug Pull Industry Looks Like at Scale

$569M across 20 weeks. 103,695 individual events. These numbers only make sense at the scale of an organized industry, not at the scale of individual bad actors. Consider the operational requirements to produce this output.

At an average of 5,185 rug pull events per week, operators must be deploying thousands of token contracts weekly. Each contract requires wallet funding, deployment, pool creation, liquidity seeding, marketing (to attract retail buyers), and eventually liquidity removal. The automation required to manage this volume is sophisticated – these are not manual operations but scripted, bot-driven pipelines that handle the entire lifecycle with minimal human intervention.

The diversity of fraud values also tells a story. The same week that produced the maximum fraud value ($53.4M in W4) contained individual rug pulls ranging from a few hundred dollars to millions. This range reflects an ecosystem with multiple tiers: small-scale operators running low-value schemes alongside professional operations running high-value targeted campaigns. The industry has a hierarchy, with the most sophisticated operators at the top extracting the most per event while the smallest operators run volume plays at low margins.

Understanding rug pulls as an industry – not as isolated frauds – changes how we think about protection. Blacklists of known bad actors are largely ineffective against industrial-scale operations that create fresh wallets continuously. Reactive forensics – identifying fraud after it happens – provide no protection to the retail investors who lost money. Only predictive, behavioral approaches that identify fraud operators before they extract value offer meaningful protection at this scale.

This is the core thesis behind ChainAware’s approach. For context on how predictive AI compares to forensic analytics in practical terms, and why the shift from reactive to predictive is the fundamental security challenge facing Web3 in 2026, our comparison of forensic versus AI-powered blockchain analysis provides the complete framework.

The Role of Token Holder Quality in Identifying Rug Pull Risk

One additional signal that Rug Pull Detector V3 incorporates – particularly for tokens that have already launched and have a holder base – is token holder quality analysis. ChainAware’s Token Rank system assigns every token a rank based on the median Wallet Rank of its holders. Legitimate tokens with real communities tend to attract wallets with diverse, experienced behavioral profiles. Rug pull setups, which attract retail speculators and bots, produce distinctive holder quality signatures.

A token where the holder base consists predominantly of fresh wallets with no prior DeFi history, created in the days immediately preceding the token launch, is a warning sign that the holder base was manufactured rather than organically acquired. Bot-driven trading activity similarly produces holder clusters with synchronized creation dates and homogeneous transaction histories – patterns that stand out clearly in a holder quality analysis.

For investors conducting due diligence on tokens with existing holder bases, ChainAware’s Token Rank guide covers the complete methodology for assessing holder quality as part of investment due diligence. Combined with Rug Pull Detector V3’s contract and creator analysis, holder quality analysis provides a third independent signal layer – and convergent warnings across all three layers are among the strongest indicators of fraudulent intent available in the DeFi ecosystem today. This deployer- and holder-level scoring is the same methodology behind ChainAware’s specialised ready-made agents, which combine token risk with holder and deployer screening in a single call.

P2P Transactions: The Rug Pull Risk Outside DEX Pools

The $569M we measured operates entirely within the DEX pool context – tokens and liquidity pools on PancakeSwap V2. However, rug pull risk also exists in peer-to-peer payment contexts that do not involve DEX pools at all.

Approximately 50% of on-chain transaction volume consists of direct peer-to-peer transfers – one wallet sending assets directly to another, with no DApp interface in the flow. This volume includes legitimate payments, OTC trades, escrow arrangements, and investment contributions to projects that have not yet launched on a DEX. It also includes fraud: investors sending funds to project team wallets that subsequently disappear, or OTC trades where the receiving party does not fulfill their side of the arrangement.

For the 50% of transactions that happen wallet-to-wallet, the protection question is not “is this pool safe?” but “is this wallet safe?” ChainAware’s free Wallet Auditor addresses exactly this use case – providing a complete behavioral profile and fraud risk assessment for any wallet address before you send irreversible on-chain funds to it. The Wallet Auditor complete guide walks through every parameter the audit covers and how to interpret the results for P2P transaction due diligence.

What Comes Next: ChainAware’s Rug Pull Research Roadmap

This dataset – 103,695 rug pulls and $569M in confirmed extraction – is the foundation of an ongoing research program. Publishing this data is the beginning, not the conclusion.

The next phases of ChainAware’s rug pull research and product development address several open questions that this initial dataset raises but does not answer.

Expanding to Complex Rug Pull Detection

As noted throughout this article, the $569M figure covers only basic liquidity extraction. Adding LP token transfer rug pulls, unlocked token sell-offs, and associated wallet extraction to the detection methodology will require additional algorithmic development – but the training data now exists in our confirmed dataset. V3.1 and subsequent versions will incrementally expand coverage to these more complex patterns.

Multi-Chain Expansion

This dataset covers PancakeSwap V2 on BNB Chain. ChainAware already operates across 8 blockchains – ETH, BNB, BASE, POLYGON, SOL, TON, TRON, and HAQQ. Expanding the rug pull dataset to include Ethereum DEXes (Uniswap V2/V3), Solana meme token launchpads, and BASE chain activity will produce a comprehensive multi-chain picture of rug pull extraction that does not currently exist anywhere in the industry.

Solana’s pump.fun – where an estimated 99% of tokens launched end in loss events for buyers – is a particularly important next target for this analysis framework. The structural characteristics of pump.fun token launches share significant overlap with PancakeSwap V2 rug pulls, but the technical analysis requires adaptation to Solana’s account-based architecture and SPL token standard.

Continuing Algorithm Improvement

The 90.1% accuracy of V3 is a milestone, not a ceiling. The algorithm team continues iterating on both the behavioral and smart contract analysis pipelines. Each confirmed rug pull event from our ongoing monitoring adds to the training dataset, and each fraud industry adaptation that our current model misses provides labeled false negative examples for the next training cycle.

The target is 95%+ prediction accuracy. Reaching that threshold requires solving the core challenge of sophisticated operator evasion – fraud operators who invest significantly in maintaining clean behavioral profiles and deploying contracts that pass automated inspection. ChainAware’s research team is actively working on graph-based analysis of funding networks and deployment clustering to address this remaining gap.

Rug Pull Red Flags: What to Look for Before Investing in Any New Token

While automated tools like V3 do the heavy lifting, investors who understand the underlying red flags make better decisions – both by interpreting V3’s output intelligently and by performing manual checks that complement automated analysis. The following red flags are drawn directly from our analysis of the 103,695 rug pull events in the dataset and from ChainAware’s behavioral research across 20M+ wallet profiles.

Red Flag 1: Unrenounced Contract Ownership

Contract ownership allows the deployer to call privileged functions – modifying transfer fees, adding transfer restrictions, minting additional supply, and pausing trading. A legitimate project with long-term intentions almost always renounces ownership or transfers it to a time-locked multisig. A contract where the deployer retains full ownership indefinitely is structurally set up for the owner to modify conditions after retail investors have bought in.

Checking ownership renouncement takes 30 seconds on BscScan or Etherscan – search the contract address, look for the “Contract” tab, and check whether owner() returns the zero address (renounced) or an active wallet address (retained). This single check eliminates a significant fraction of the most blatant rug pull setups.

Red Flag 2: Unlocked Liquidity Pool Tokens

When a creator seeds liquidity into a PancakeSwap V2 pool, they receive LP (Liquidity Provider) tokens representing their share of the pool. Legitimate projects lock these LP tokens in a time-lock contract – preventing liquidity removal for a defined period (commonly 6-24 months). Unlocked LP tokens held in the deployer’s wallet can be redeemed for the underlying liquidity at any moment, making rug pull execution a one-transaction event.

LP lock verification can be performed manually on platforms like Mudra or Team Finance, which maintain records of locked LP tokens on BNB Chain. The absence of a lock is not automatically fraudulent – some legitimate projects rely on other mechanisms – but it is a significant red flag that requires additional due diligence before committing capital. V3’s smart contract analysis flags unlocked LP positions automatically.

Red Flag 3: Fresh Deployer Wallet with No History

Professional rug pull operators often maintain separate deployer wallets for each scheme – fresh addresses with no prior on-chain history. This is a deliberate evasion tactic: behavioral analysis tools that look at deployer history return a clean result, because there is no history to analyze. V3 handles this by examining the funding source of the deployer wallet (where the ETH or BNB originated from), not just the deployer wallet itself. However, a fresh deployer wallet with no history should still independently raise an investor’s suspicion level, particularly when combined with other red flags.

Red Flag 4: Suspiciously High Maximum Transaction or Wallet Limits

Many rug pull contracts include maximum transaction size or maximum wallet balance limits that restrict how much any individual buyer can purchase. These limits are presented as anti-whale measures – preventing any single buyer from acquiring too large a share. In practice, they often serve a different purpose: ensuring that no single buyer has enough exposure to justify the gas cost of legal action, and ensuring that the token requires extended time to accumulate retail capital before the rug can be executed. Combined with gradual price increases driven by bot activity, these limits produce a slow accumulation of widely distributed retail capital that is then extracted in a single pull event.

Red Flag 5: Concentrated Token Allocation

Token distribution matters enormously. If the top 10 wallets hold more than 50% of the total supply, and those wallets are connected to the deployer or hold unlocked tokens, they represent a latent supply overhang that can be sold into any retail buying pressure. ChainAware’s Token Rank analysis reveals the quality and concentration of holder distribution for any token with an existing holder base – a concentrated, low-quality holder base is one of the strongest predictors of eventual rug pull or dump events. The complete methodology is explained in the Token Rank guide.

Red Flag 6: Anonymous Team With No Verifiable Presence

Full anonymity is the norm in crypto, not the exception – many legitimate projects have anonymous teams. However, the combination of full anonymity with the absence of any verifiable prior project history, a project launched in the previous week with no audit, and an aggressive social media presence focused entirely on price expectations is a signature pattern of rug pull operations. Legitimate anonymous projects typically have verifiable GitHub commit histories, prior community involvement in legitimate projects, and at minimum a third-party security audit. The absence of all three simultaneously is a meaningful red flag.

Red Flag 7: Extremely High Early Price Performance

A token that gains 500%-2,000% in its first 24-48 hours of trading is an appealing investment narrative. It is also the characteristic signature of a pump phase that precedes a rug pull. Organic price discovery – driven by genuine retail demand for a real product – produces growth curves that are steep but not parabolic. Parabolic early gains are typically produced by bot-driven wash trading that manufactures artificial volume and price momentum to attract FOMO-driven retail buyers. The parabolic chart is the marketing material for the rug. When the price is high enough to make liquidity removal maximally profitable, the rug executes.

How Rug Pull Operators Evade Detection: An Adversarial Analysis

Understanding how sophisticated fraud operators attempt to evade detection is as important as understanding the detection methods themselves. The 9.9% of rug pull events that V3 does not catch are concentrated in operations that specifically invest in evasion. Publishing this analysis serves retail investors by explaining what the highest-risk events look like, and serves the research community by documenting the evasion tactics that future algorithm versions must address.

Wallet Aging and History Manufacturing

The most sophisticated operators maintain aged deployer wallets – addresses that have months or years of legitimate-looking transaction history before being used for fraud. These wallets interact with legitimate DeFi protocols, make small token purchases across diverse projects, and accumulate behavioral signals that behavioral analysis models associate with legitimate users. When such a wallet eventually deploys a fraudulent contract, the behavioral layer returns a low-risk signal. Only the smart contract analysis layer can catch fraud from these operators – and only if the contract itself contains detectable risk patterns.

Countering this tactic requires tracking the clustering of aged wallets that share funding sources or that appear in coordinated deployment patterns – even when each individual wallet’s history appears clean. This graph-based analysis is part of ChainAware’s ongoing algorithm development roadmap.

Contract Code Obfuscation

Professional fraud operators increasingly deploy contracts with obfuscated code – transfer restrictions hidden within complex modifier chains, mint functions embedded in proxy contract architectures, and ownership retention disguised as multi-sig governance mechanisms that are controlled entirely by the deployer. These obfuscation patterns specifically target the limitations of automated smart contract analysis tools.

V3’s bytecode inspection – which operates on compiled contract code rather than requiring readable source code – provides partial protection against source code obfuscation. However, novel obfuscation patterns that have not yet appeared in the training dataset represent genuine blind spots. Regular model updates and the continuous addition of newly confirmed rug pull events to the training dataset are the primary mechanism for closing these gaps as they are discovered.

Delayed Execution

Some operators run long-duration schemes – maintaining active development activity, social media presence, and liquidity for weeks or months before executing the rug pull. These delayed execution schemes are specifically designed to outlast the attention spans of initial investors who may have checked V3 at launch and seen a clean result. By the time the rug executes, many initial investors have already forgotten the risk assessment they saw weeks ago and have added to their position based on the apparent ongoing legitimacy of the project.

Protecting against delayed execution requires ongoing monitoring rather than a single point-in-time check. ChainAware’s Transaction Monitoring Agent, which continuously rescreens connecting wallets on every DApp visit, provides this ongoing monitoring layer for DApps. For individual retail investors, re-running V3 checks periodically on held positions – particularly when planning to add to an existing position – is the equivalent individual protection behavior.

Legitimate-Looking Audits

A concerning development in the rug pull industry is the emergence of fraudulent security audits – certificates from obscure or non-existent “audit firms” that create the appearance of third-party verification without the substance. A token that displays an “audited” badge from an unrecognizable firm – or from a legitimate-sounding name that does not correspond to any established security company – provides no real protection against rug pull risk.

Legitimate audits from established firms like CertiK, Trail of Bits, Consensys Diligence, or OpenZeppelin are verifiable on the auditing firm’s own website and are associated with published audit reports. An audit badge that cannot be verified against the auditing firm’s own published report list should be treated as fabricated. V3’s smart contract analysis provides an independent assessment that does not rely on audit claims – it examines the code directly, regardless of what audit certificate the project displays.

The Market Infrastructure Gap: Why DeFi Needs Better Fraud Data

The $569M figure in this report exists not just as a fraud statistic but as a market infrastructure data point. DeFi cannot mature into a mainstream financial system while retail investors lose hundreds of millions of dollars per quarter to a fraud mechanism that could be largely prevented with better tooling and better data.

Traditional financial markets have infrastructure specifically designed to protect retail investors from comparable fraud: prospectus requirements, securities registration, market maker oversight, exchange listing standards, and regulatory enforcement. These mechanisms are not perfect – traditional markets have their own fraud problems – but they represent decades of accumulated institutional knowledge about how to structure market access to minimize retail harm.

DeFi has none of this infrastructure by design – permissionless access is a core feature, not a bug. The trade-off is that permissionless access enables both the extraordinary innovation of the DeFi ecosystem and the extraordinary fraud of the rug pull industry. Building protective infrastructure that preserves permissionlessness while reducing retail harm requires data-driven tools that operate at the protocol layer – not regulatory gatekeeping that would undermine DeFi’s fundamental architecture.

ChainAware’s approach – behavioral AI that flags risk without blocking access, tools that inform investor decisions without requiring permission from any central authority – represents one model for how this protective infrastructure can be built. Publishing the $569M dataset is part of the broader argument that this infrastructure is urgently needed and that the data to build it exists.

For DApp teams specifically, building fraud resistance into their platform architecture is becoming a competitive differentiator. Users who have been burned by rug pulls – and statistically, a significant fraction of active DeFi users have been – actively seek platforms with visible security measures. A DApp that visibly screens connecting wallets, displays behavioral security ratings for tokens listed on its interface, and provides transparent fraud risk data builds trust with the retail user base that DeFi needs to grow beyond its current audience.

The DeFi onboarding problem – why 90% of connected wallets never transact – is partly a product problem, partly a UX problem, and significantly a trust problem. Users who don’t trust that their capital is safe don’t commit capital. Solving fraud at the infrastructure level directly addresses the trust component of the conversion problem. For the complete analysis of why the 90% non-transacting wallet problem is DeFi’s most critical growth challenge, and how behavioral intelligence addresses it, see our comprehensive guide on DeFi onboarding and why connected wallets don’t transact.

Building that trust requires two things simultaneously: making fraud harder to execute and making fraud more visible when it does execute. V3 contributes to making fraud harder to execute – at 90.1% prediction accuracy, it prevents a significant fraction of rug pull investments before they happen. Publishing this dataset contributes to making fraud more visible – giving the industry, regulators, and researchers the empirical foundation to understand and respond to the true scale of the problem.

Together, these two contributions represent ChainAware’s core thesis: that Web3 grows faster and serves users better when behavioral intelligence is embedded into the infrastructure of every DApp interaction. The $569M figure is not just a warning – it is the business case for why predictive fraud detection is one of the most important infrastructure investments any Web3 platform can make in 2026. For the complete framework of how behavioral intelligence powers Web3 growth beyond security, the Web3 agentic economy guide covers the full stack from fraud prevention through personalized growth. The full 19-category forensic methodology behind the Fraud Detector is documented on the Fraud Detector learn page.

Frequently Asked Questions

What exactly is a rug pull?

In the context of this dataset, a rug pull is defined as a liquidity event where the contract creator of a token pool removes more liquidity than they originally added. A creator deposits funds (Mint event), retail investors buy the token and add value to the pool, and then the creator withdraws all liquidity (Burn event). The difference between what they removed and what they added – when removal exceeds addition – is the rug pull value. The token price drops to zero instantly upon liquidity removal, leaving holders with worthless assets. For a full comparison of rug pulls versus pump-and-dump schemes, see our dedicated guide on rug pull vs pump and dump.

How does ChainAware Rug Pull Detector V3 work?

V3 runs two parallel analysis pipelines. The first examines the behavioral history of the contract creator’s wallet – their deployment history, funding sources, prior rug pull associations, and wallet age. The second inspects the smart contract code itself for dangerous patterns: hidden transfer restrictions, uncapped mint functions, unrenounced ownership, and unlocked LP tokens. Both pipelines produce independent risk scores that are combined through an ensemble model trained on 103,695+ confirmed rug pull events. The combined model achieves 90.1% prediction accuracy on the held-out test set.

Is the Rug Pull Detector free?

Yes. The web interface at chainaware.ai/rugpull is completely free for retail investors, with no account creation required. Businesses that need API access for automated, high-volume token screening can subscribe to the API at chainaware.ai/subscribe. AI agents can access the tool through the X402 micropayment protocol, paying per analysis without requiring a subscription.

What is the difference between V2 and V3?

V2 relied exclusively on behavioral analysis of contract creator wallets, achieving approximately 68% prediction accuracy. V3 adds a full smart contract analysis layer – inspecting contract code for dangerous patterns regardless of the deployer wallet’s history. This combination closes the gap that sophisticated fraud operators exploited in V2 by maintaining clean deployer wallet histories. The combined V3 model achieves 90.1% prediction accuracy – a 32.5% relative improvement over V2.

Does V3 work on tokens that have not yet launched?

Yes. V3 can analyze any deployed smart contract – including contracts that have been deployed but have not yet attracted liquidity. Smart contract analysis runs regardless of whether there is an active trading pool. Creator behavioral analysis also runs at any point after contract deployment. For pre-launch tokens, smart contract analysis is particularly valuable because it does not require any trading history to return a risk assessment.

Can a rug pull still happen even if V3 gives a low risk score?

Yes. V3 achieves 90.1% accuracy, meaning approximately 9.9% of rug pull events will not be flagged. These false negatives are concentrated in the most sophisticated fraud operations – those that invest in maintaining clean deployer profiles and deploy contracts that pass automated inspection. No automated tool can guarantee 100% detection. V3 should be used as a risk filter, not as a guarantee, and combined with human judgment on tokenomics, team identity, and project fundamentals for high-value investment decisions.

Why does $569M in losses generate almost no media coverage?

Rug pull losses are distributed across hundreds of thousands of small transactions affecting individual retail investors, rather than concentrated in a single event affecting an institution. Distributed losses are structurally invisible to media coverage, which requires a single dramatic event with a named victim and a named perpetrator. The victims of rug pulls are anonymous retail investors with no media presence. The perpetrators are anonymous wallet operators with no attributable identity. The structural invisibility of rug pull losses is one of the primary reasons this form of fraud operates at scale without triggering the industry-wide response that dramatic exchange hacks generate.

What chains does ChainAware support for rug pull detection?

ChainAware currently supports 8 blockchains across its full product suite: Ethereum (ETH), BNB Smart Chain (BNB), Base (BASE), Polygon (POLYGON), Solana (SOL), TON, TRON, and HAQQ. Rug Pull Detector V3 is optimized for BNB Chain and Ethereum in its current version, with Solana and Base coverage expanding in upcoming releases. For the complete multi-chain capability overview, ChainAware’s complete product guide covers which tools are available on which chains.

How can AI agents use Rug Pull Detector V3?

AI agents access Rug Pull Detector V3 through ChainAware’s X402 micropayment protocol – paying per analysis in real time without requiring pre-approved API keys. Agents can also access the full suite of ChainAware tools through the Model Context Protocol (MCP) server at prediction.mcp.chainaware.ai/sse. The complete integration guide for AI agents is available at our Prediction MCP guide, and the GitHub repository at github.com/ChainAware/behavioral-prediction-mcp provides open-source agent definitions that any AI framework can deploy directly.

The post $569M+ in Rug Pulls on PancakeSwap V2 in 20 Weeks – Rug Pull Detector V3 Launched With 90.1% Accuracy first appeared on ChainAware.ai.

Last Updated: 2026

The fastest-growing Web3 protocols in 2026 aren’t hiring bigger teams. They’re deploying more agents.

This isn’t a future prediction. It’s a structural shift already underway. DeFi protocols are replacing compliance officers with AML agents that screen every transaction in real time. Growth teams are being augmented – and in some cases replaced – by wallet marketing agents that generate personalized campaigns for 100,000 users simultaneously. Customer success managers are giving way to onboarding routers that detect a new wallet’s experience level in milliseconds and serve the right first experience automatically.

Welcome to the Web3 Agentic Economy.

This article defines the shift, explains why Web3 is uniquely suited for agentic infrastructure, maps the seven core agent roles replacing human functions in DeFi, and shows exactly which ChainAware agents power each role – with real examples of how protocols are deploying them today. We also address the risks honestly, because uncritical automation in financial systems is how catastrophic failures happen.

If you’re building a Web3 protocol, DeFi product, or AI agent pipeline in 2026, this is the strategic context you need to operate in.

What Is the Web3 Agentic Economy?

The Web3 Agentic Economy describes the emerging economic model in which AI agents – not human employees – serve as the primary operators of blockchain protocols, DeFi products, and on-chain financial systems.

In a traditional protocol, a team of humans handles critical functions: compliance officers review suspicious transactions, growth marketers run campaigns, fraud analysts investigate anomalies, customer success teams onboard new users, and treasury managers monitor large holder positions. Each function requires expertise, operates on human timescales (hours, days), and costs significant ongoing salary.

In an agentic protocol, these functions are executed by AI agents: autonomous software programs that observe on-chain data, make decisions based on behavioral models, execute actions (approve, flag, route, message, alert), and improve their performance over time without manual intervention. They operate at machine speed – sub-100ms for most decisions – and at machine scale – millions of wallets simultaneously.

The transition is being enabled by two converging technologies. First, large language models (LLMs) have reached the capability threshold where they can reason about complex, multi-step financial decisions with high accuracy. Second, Model Context Protocol (MCP) – the open standard introduced by Anthropic – has solved the tool integration problem, allowing any AI agent to call blockchain intelligence APIs, databases, and analytics systems in natural language without custom integration work. For the complete infrastructure overview of how AI agents interact with blockchain data, see the ChainAware For AI Agents overview.

The result is what economists would recognize as a factor substitution at the infrastructure layer: human labor in protocol operations is being substituted by agent capital. This is not a gradual process. The protocols that build agentic stacks in 2026 will operate at fundamentally different cost structures and response speeds than those that don’t – and the gap compounds over time.

According to McKinsey’s analysis of generative AI’s economic potential, financial services is one of the sectors with the highest automation potential – with compliance, fraud detection, and customer engagement among the top functions. Web3 sits at the intersection of financial services and fully digitized data, making it the ideal first sector for full agentic deployment.

Why Web3 Is Uniquely Built for AI Agents

Web2 companies struggle to deploy AI agents at scale because their data is fragmented, partially digitized, and locked in proprietary silos. A customer’s purchase history is in one database, their support tickets in another, their email behavior in a third. Building agents that can act across all of these requires enormous integration work, and the data quality is often poor.

Web3 has none of these problems. Three structural properties make blockchain the ideal operating environment for AI agents:

1. Fully digitized from day one. Every transaction, every protocol interaction, every asset movement is recorded on-chain automatically. There is no paper trail to digitize, no legacy system to integrate with. The data exists in a machine-readable format that AI agents can query directly. A wallet’s entire financial history – every DEX trade, every lending position, every bridge transaction – is available in a single on-chain query.

2. Transparent and verifiable. Unlike Web2 behavioral data, which can be fabricated, corrupted, or biased by the platform collecting it, blockchain data is cryptographically verified. An agent can trust that vitalik.eth made 19,972 transactions over 3,730 days because the blockchain is the source of truth, not a company’s analytics database. This makes agent decisions more reliable and auditable.

3. Programmable by design. Smart contracts are machine-readable agreements that execute automatically when conditions are met. AI agents don’t need to negotiate with human counterparts or work through bureaucratic approval processes – they interact directly with protocol logic. An agent that detects a suspicious large withdrawal can automatically trigger a smart contract circuit breaker, not file a ticket for human review.

These three properties mean Web3 didn’t need to be retrofitted for AI agents. It was architected in a way that makes agentic operation a natural evolution. The protocols that recognize this earliest will gain the most durable competitive advantages. See our AI-Powered Blockchain Analysis guide for the technical foundations this is built on.

7 Human Roles Being Replaced by AI Agents in Web3

The agentic transition in Web3 is not about wholesale elimination of human judgment. It is about substituting human execution of repetitive, data-intensive, high-volume decisions with agents that make those decisions faster, more consistently, and at lower cost. Here are the seven core functions already undergoing this transition.

Role 1: Compliance Officer → Transaction Monitoring Agent

Traditional compliance in Web3 requires humans to review flagged transactions, maintain sanctions lists, file Suspicious Activity Reports (SARs), and stay current with evolving regulations across multiple jurisdictions. A senior crypto compliance officer costs $120,000-$200,000 per year and can meaningfully review perhaps 50-100 cases per day.

A transaction monitoring agent screens every transaction in real time – 24/7, across all blockchains – cross-referencing against OFAC SDN lists, mixer interactions, known fraud addresses, and behavioral AML models. It auto-approves clean transactions in under 100ms, escalates medium-risk cases for human review with a pre-written analysis report, and auto-blocks high-risk transactions with documented justification for regulators. Volume processed: unlimited. Cost: a fraction of one compliance officer salary.

This is exactly the function ChainAware’s aml-scorer and fraud-detector agents power – read the full regulatory context in our Blockchain Compliance for DeFi guide. The full catalogue of compliance and fraud agents is documented at the Security & Fraud Agents learn guide.

Role 2: Fraud Analyst → Fraud Detection + Rug Pull Detection Agents

Human fraud analysts in Web3 work reactively: they investigate after something goes wrong. By the time a human identifies a fraud pattern, analyzes wallet history, checks network connections, and issues a warning, the damage is done. Blockchain transactions are irreversible. Post-incident documentation doesn’t help the users who lost funds.

The fraud-detector agent operates predictively – assessing fraud probability before a transaction executes. The rug-pull-detector agent monitors new protocol deployments and token contracts continuously, flagging behavioral patterns that match historical rug pull signatures before users deposit funds. According to TRM Labs’ 2026 Crypto Crime Report, $158 billion in illicit crypto volume was processed in 2025 – the vast majority of which could have been intercepted with predictive behavioral screening that didn’t exist at scale. It exists now. See our Forensic vs AI-Powered Blockchain Analysis comparison for the accuracy difference.

Role 3: Growth Marketer → Wallet Marketing + Onboarding Router Agents

Web3 growth teams spend enormous budgets on campaigns that acquire the wrong users. The fundamental problem: they can’t tell the difference between a high-LTV power trader and a zero-retention airdrop farmer until weeks after acquisition. By then, the CAC is sunk and the user is gone.

The wallet-marketer agent generates personalized engagement campaigns for each wallet based on behavioral profile: experience level, risk tolerance, protocol preferences, predicted intentions. The onboarding-router agent instantly classifies a new wallet and routes it to the right first experience – expert users go straight to the pro dashboard, newcomers get guided tutorials, high-risk wallets get additional verification before access. Our Web3 User Segmentation guide documents protocols achieving 35% → 62% onboarding completion and 40% → 22% churn reduction using these agents.

Role 4: Security Analyst → Trust Scorer + Reputation Scorer Agents

Security analysts in Web3 protocols spend most of their time doing the same thing: evaluating whether a counterparty, user, or protocol is trustworthy enough to interact with. This involves checking wallet history, looking for red flags, assessing track records. It’s time-consuming, inconsistent across analysts, and doesn’t scale.

The trust-scorer agent returns a forward-looking trust probability (0-100%) in under 100ms for any wallet – enabling tiered access decisions at login time. The reputation-scorer agent builds a holistic on-chain reputation profile that captures community standing, governance behavior, and protocol interaction quality over time. Together, they replace the judgment calls that security analysts make manually – consistently, at scale, and with full audit trails.

Role 5: Investment Research Analyst → Token Analyzer + Analyst Agents

Crypto fund research teams spend 3-5 days manually evaluating each new protocol: reading whitepapers, analyzing tokenomics, checking on-chain metrics, assessing team credibility. At 50+ new protocols per week in a bull market, this is humanly impossible to do thoroughly.

The token-analyzer agent evaluates whether a token’s volume is genuine or wash-traded, assesses holder distribution and concentration risk, and flags behavioral patterns that match historical failures. The analyst agent synthesizes all ChainAware data into narrative investment committee reports. What takes a human team 3 days takes an agent pipeline 2 hours – for all 50 protocols simultaneously. For methodology, see our Wallet Rank Guide and Token Rank explainer.

Role 6: Customer Success Manager → Onboarding Router + Wallet Marketer Agents

Customer success in Web3 has always been an impossible problem: users are pseudonymous, there’s no support ticket system, and CSMs have no behavioral data on who their users are. Most protocols don’t even know which users are at risk of churning until they’re already gone.

The onboarding-router agent ensures every user gets the right first experience, dramatically reducing the most common churn trigger: confusion in the first session. The wallet-marketer agent monitors behavioral signals that predict churn – declining activity, shift in protocol preferences, whale exit preparation – and triggers automated re-engagement before the user leaves. This is the entire customer success function running autonomously. See our Behavioral User Segmentation guide for the segmentation logic underpinning these agents.

Role 7: Treasury / Risk Manager → Whale Detector + Wallet Ranker Agents

Protocol treasury managers spend significant time monitoring large holder positions – watching for signs that a whale is preparing to exit, tracking concentration risk, stress-testing liquidity against large withdrawal scenarios. This is reactive work that human managers can only do during business hours.

The whale-detector agent monitors all significant holders 24/7, identifying unusual activity patterns that historically precede large exits – and alerting the team before execution, not after. The wallet-ranker agent provides continuous quality scoring across the entire user base, enabling treasury teams to understand their protocol’s actual user composition, not just its headline TVL number. Our Web3 Business Intelligence guide covers the analytics layer these agents surface.

Agent-by-Agent Examples: When to Use Which

Understanding which agent to deploy for which situation is the practical heart of building an agentic Web3 stack. Here are concrete, real-world scenarios for each ChainAware agent.

fraud-detector – When to use it

Use fraud-detector any time a wallet is about to receive meaningful trust – before approving a large withdrawal, before granting governance rights, before allowing leverage access, before processing a crypto payment. The agent returns a fraud probability score and behavioral red flags in under 100ms.

Example 1: A DeFi lending protocol deploys fraud-detector at the borrow initiation point. Any wallet requesting a loan above $10,000 is automatically screened. Wallets with fraud probability above 15% are required to complete additional verification. Wallets above 40% are automatically declined with a documented reason for regulatory records. Result: fraud losses reduced 78% in the first quarter.

Example 2: A crypto payment processor uses fraud-detector to screen every incoming USDC payment before releasing goods. The agent’s 98% accuracy means near-zero false positives for legitimate customers while catching the fraud cases that previously slipped through blocklist-only screening. Try it yourself: ChainAware Fraud Detector – free.

aml-scorer – When to use it

Use aml-scorer for regulatory compliance screening – any situation where you need to demonstrate Know Your Transaction (KYT) compliance to regulators. Returns sanctions status, mixer interactions, AML risk score, and documentation suitable for regulatory filing.

Example: A regulated crypto exchange operating under MiCA requirements deploys aml-scorer for every withdrawal above €1,000. The agent auto-generates the KYT documentation required by their compliance program, flags cases requiring SAR consideration, and maintains an audit trail for regulators. Cost: 95% less than manual compliance review. Speed: real-time vs 2-5 day human review cycles.

transaction-monitoring-agent – When to use it

Use the Transaction Monitoring Agent for continuous, real-time screening of all protocol activity – not just individual wallet checks but ongoing behavioral monitoring across your entire user base. Detects structuring patterns, velocity anomalies, and coordinated suspicious activity that single-wallet checks miss.

Example: A DEX notices a cluster of wallets executing high-frequency small swaps across multiple accounts – a classic structuring pattern for AML evasion. The transaction monitoring agent identifies the coordinated behavioral pattern across wallets and flags the cluster for review. A human analyst would have seen individual transactions as normal; the agent sees the network pattern. Learn more about our Transaction Monitoring Agent.

rug-pull-detector – When to use it

Use rug-pull-detector before recommending any new protocol, token, or liquidity pool to users. Also use it for ongoing monitoring of protocols where your users have deposited funds.

Example 1: A DeFi aggregator deploys rug-pull-detector as a pre-listing gate. Any new protocol must pass behavioral screening before appearing in their interface. Protocols where developer wallet patterns match historical rug pull signatures are automatically excluded, with the reason documented. Users trust the aggregator more; fewer support escalations from users who lost funds.

Example 2: A portfolio management agent monitors all active LP positions daily using rug-pull-detector. When a protocol’s behavioral pattern shifts – treasury wallet suddenly becomes active, team allocation moves, liquidity lock approaches expiry – the agent alerts users before they can be caught in an exit.

wallet-ranker – When to use it

Use wallet-ranker whenever you need to assess overall user quality – token distributions, governance weighting, acquisition channel evaluation, anti-Sybil screening, and lending credit assessment. Wallet Rank (0-100) is the single best predictor of user LTV in Web3. Read the full methodology: ChainAware Wallet Rank Guide.

Example 1 – Token distribution: A protocol distributes governance tokens to 50,000 early users. Instead of equal distribution (which rewards Sybil farmers equally with genuine users), they use wallet-ranker to weight allocations: Rank 70+ receives 5× allocation, Rank 30-70 receives 1× allocation, Rank below 30 receives 0.1× allocation. Result: 90% of tokens go to Rank 50+ users; post-TGE selling pressure reduced 60%.

Example 2 – Acquisition channel ROI: A growth agent scores every inbound wallet from each marketing channel using wallet-ranker in real time. Discord outreach average rank: 68. Twitter campaign average rank: 25. The agent automatically shifts 70% of the ad budget to Discord-style community channels and away from Twitter mass campaigns. Same total spend, 3× the quality of acquired users.

wallet-marketer – When to use it

Use wallet-marketer to generate personalized engagement content for any wallet – re-engagement campaigns, feature announcements, educational content, governance proposals. The agent analyzes behavioral profile and generates messaging that resonates with that specific wallet’s interests, experience level, and predicted intentions.

Example: A protocol has 80,000 wallets that connected but haven’t transacted in 30 days. Instead of one mass email (which gets 2% open rate), they deploy wallet-marketer to generate segmented messaging: expert DeFi traders receive yield optimization content, NFT collectors receive upcoming drop announcements, newcomers receive simplified tutorials. Result: 340% improvement in re-engagement click-through rate. See our Web3 Marketing Analytics guide for measurement methodology.

onboarding-router – When to use it

Use onboarding-router at the moment any new wallet connects to your product for the first time. The agent classifies the wallet’s experience level, primary activity focus, and risk profile in under 100ms – enabling dynamic routing to the right onboarding flow before the user sees a single screen.

Example: A DeFi protocol has three user types: beginners who need guided education, intermediate traders who need feature discovery, and experts who need immediate access to advanced functionality. Previously, all three saw the same onboarding – and 65% dropped off in the first session. After deploying onboarding-router, each type sees a tailored first experience. Overall onboarding completion: 35% → 67%. Day-30 retention: 28% → 51%.

growth-agents – When to use them

ChainAware’s Growth Agents coordinate the full acquisition-to-retention lifecycle: scoring inbound users, routing them appropriately, monitoring engagement signals, triggering re-engagement at the right moment, and continuously reporting segment economics to growth teams. They are the operational layer that makes behavioral segmentation actionable at scale, not just analytically interesting.

Example: A GameFi protocol deploys Growth Agents across their entire user funnel. Acquisition agent scores every new wallet and reports channel quality daily. Onboarding agent routes users to beginner, intermediate, or expert game tracks. Retention agent monitors play patterns and triggers personalized re-engagement when activity drops. Treasury agent monitors whale player positions and alerts the team before large asset withdrawals. Four agents. Zero additional headcount. Protocol LTV per user up 2.8× in 90 days. Learn more about our Growth Agents.

whale-detector – When to use it

Use whale-detector for protocols where a small number of large holders represent disproportionate TVL or revenue risk – which is almost every DeFi protocol.

Example: A lending protocol’s top 50 holders represent 73% of total deposits. The whale-detector agent monitors all 50 continuously, flagging when any of them shows unusual activity: increased wallet-to-wallet transfers, new bridge transactions, shifting collateral ratios. When Whale #3 starts moving assets in patterns that historically precede large withdrawals, the protocol has 6-48 hours warning to adjust liquidity reserves – rather than discovering the withdrawal in the transaction log after it executes.

trust-scorer – When to use it

Use trust-scorer for tiered access control – adjusting feature access, leverage limits, withdrawal caps, or governance rights based on a wallet’s forward-looking trust probability. Unlike fraud detection (which screens for bad actors), trust scoring enables positive discrimination toward trustworthy users.

Example: A derivatives protocol offers three leverage tiers: 5×, 20×, and 50×. Instead of requiring all users to complete KYC for high leverage (which 60% abandon), they use trust-scorer: Trust 85+ → 50× automatically, Trust 60-85 → 20× with soft verification, Trust below 60 → 5× or full KYC for higher access. Conversion to high-leverage trading up 40%. KYC abandonment down 70%.

reputation-scorer – When to use it

Use reputation-scorer for community quality decisions: governance weight, grant allocation, ambassador identification, DAO membership gating. Reputation score captures community standing and constructive participation – metrics that wallet rank and trust score don’t fully cover.

Example: A DAO receives 400 grant applications. Instead of reading 400 applications manually (weeks of work), the governance agent runs reputation-scorer on every applicant wallet automatically, producing a ranked shortlist of the 30 applicants with the strongest on-chain track records. Human reviewers focus on the top 30. Process time: days → 2 hours.

token-analyzer – When to use it

Use token-analyzer before listing, partnering with, or building yield strategies around any token. Surfaces whether volume is genuine vs wash-traded, holder concentration risk, and behavioral quality of the community.

Example: A yield aggregator evaluates 20 new liquidity pools per week for inclusion in their strategies. Token-analyzer automatically screens each pool: genuine vs wash-traded volume, holder quality, smart money presence, and concentration risk. Pools with more than 40% wash-traded volume or whale concentration above 60% are automatically excluded. Human review time reduced from 3 days to 45 minutes per week.

The Infrastructure Layer: What Agents Need to Operate

AI agents are only as capable as the data and tools they can access. An agent that can reason brilliantly but has no access to real-time behavioral data produces confident-sounding but empty outputs. The infrastructure layer – the behavioral data, prediction models, and tool APIs – is what separates agents that actually improve protocol operations from agents that generate plausible-sounding noise.

For Web3 agents specifically, the infrastructure requirements are:

Behavioral data at wallet level. Not just transaction counts or balance – full behavioral profiles including risk willingness, experience level, protocol preferences, interaction history, and predictive scores. ChainAware maintains this for 14M+ wallets across 8 blockchains, updated continuously.

Prediction models, not just data retrieval. Raw blockchain data is available to anyone. The intelligence is in the models that interpret it: what does this transaction pattern predict about future behavior? Is this wallet likely to churn, to commit fraud, to become a power user? ChainAware’s ML models, trained on years of on-chain behavioral data, provide this predictive layer at 98% fraud prediction accuracy.

Agent-native tool interfaces. This is where MCP changes everything. Before MCP, connecting an agent to blockchain intelligence required writing custom API client code, maintaining schemas, handling authentication – all of which is developer work, not agent work. With ChainAware’s MCP server, any LLM agent can call fraud detection, AML scoring, wallet ranking, and behavioral analytics in natural language. The agent reads the tool description and knows how to call it. See our complete MCP Integration Guide for technical setup, and the Prediction MCP learn guide for the full tool reference.

Real-time inference. Protocol operations can’t wait for batch processing. When a user is in the middle of a withdrawal flow, the fraud check needs to complete in under 100ms – or the UX breaks. ChainAware’s inference latency is sub-100ms for all agents, enabling truly real-time agentic decision-making at transaction points.

This stack – behavioral data + prediction models + MCP tool access + real-time inference – is what ChainAware calls Agentic Growth Infrastructure. It’s the layer that sits between your AI agent (Claude, GPT, or custom LLM) and the blockchain behavioral intelligence it needs to act intelligently on your protocol’s behalf.

The Economics: Agent Stack vs Human Team

The economic case for agentic Web3 operations is not subtle. Here is a direct comparison for a mid-sized DeFi protocol handling $50M-$500M TVL:

The human team cost estimate is conservative – it excludes benefits, recruitment, training, management overhead, and the opportunity cost of senior founders spending time on operational functions instead of product. The agent stack cost covers ChainAware MCP subscription, LLM API costs, and basic infrastructure.

The performance comparison is equally stark. Human compliance processes 50-100 cases per day; the agent processes unlimited cases in real time. Human fraud analyst catches patterns within days; the agent catches them before execution. Human growth marketer sends one campaign to all users; the agent sends 100,000 personalized messages simultaneously. For Web3 credit scoring context, see our Web3 Credit Scoring guide – the same behavioral models power creditworthiness assessments.

This doesn’t mean eliminating all humans. It means redirecting human judgment to where it’s genuinely irreplaceable: strategic decisions, edge case review, regulatory relationship management, and product direction. The agent handles the execution volume; the human handles the exceptions and strategy.

Multi-Agent Protocol Architecture: Three Real Deployments

The most powerful applications of agentic infrastructure come from multiple agents working in coordination – each calling different ChainAware capabilities, passing outputs to each other, and collectively replacing entire operational teams. Here are three real deployment architectures.

Architecture 1: The Fully Agentic DeFi Lending Protocol

A DeFi lending protocol handling $200M TVL deploys five coordinating agents that replace what would have been a 12-person operations team:

Gate Agent (fraud-detector + aml-scorer): Every new wallet attempting to borrow is screened in real time. Fraud probability above 20% → declined with documented reason. AML risk above medium → additional verification required. Processes 10,000 applications per day in under 100ms each.

Credit Agent (wallet-ranker + trust-scorer): For approved wallets, calculates maximum loan size and interest rate tier based on Wallet Rank and Trust Score. Rank 80+, Trust 90+ → best rates and highest limits. Rank 40-60, Trust 60-80 → standard terms. Below thresholds → conservative terms or collateral requirement. Replaces the credit committee function.

Monitoring Agent (transaction-monitoring-agent + whale-detector): Continuously monitors all active loan positions. Flags unusual repayment patterns, collateral movements, and large position changes. Alerts risk team to whale exit preparation 24-48 hours before execution.

Growth Agent (wallet-marketer + onboarding-router): Routes new borrowers to the right onboarding experience, generates personalized follow-up based on borrowing behavior, identifies upsell opportunities when wallet profiles suggest readiness for additional products.

Research Agent (token-analyzer + rug-pull-detector): Continuously screens all collateral assets accepted by the protocol for quality degradation – falling holder quality, rising wash trading, rug pull behavioral patterns – and alerts the team to reduce collateral ratios before a crisis.

Architecture 2: The Agentic Exchange Compliance Stack

A regulated crypto exchange operating under MiCA compliance deploys a three-tier compliance architecture that handles 95% of cases without human intervention. The complete framework for this tiered approach is documented in the Autonomous Compliance Screening use case:

Tier 1 – Fast Path (trust-scorer): Runs in under 100ms at transaction initiation. Trust score 85+ → auto-approve, no further review. Handles 70% of all transactions instantly.

Tier 2 – Standard Review (aml-scorer + fraud-detector): For Trust 50-85, runs full AML and fraud screen. Auto-approves if both pass with documented results. Escalates if either flags risk. Handles 25% of transactions in under 5 seconds.

Tier 3 – Enhanced Review (analyst + reputation-scorer): For Trust below 50, generates a complete compliance report and reputation assessment. Human compliance officer reviews this pre-built report rather than conducting their own analysis. Handles 5% of transactions – the ones that genuinely need human judgment. Human review time per case: 5 minutes (vs 45 minutes without the analyst agent’s pre-built report).

Architecture 3: The Full-Stack Growth Protocol

A Web3 gaming protocol deploys end-to-end agentic growth infrastructure:

At acquisition: wallet-ranker scores every inbound user in real time by channel, reporting daily quality metrics. Growth team reallocates budget weekly based on agent data, not gut feel.

At activation: onboarding-router detects experience level and routes new players to beginner, intermediate, or expert game tracks. Tutorial completion: 35% → 71%.

At retention: wallet-marketer monitors play patterns and sends personalized re-engagement when activity drops – tailored to each player’s preferred game modes and asset preferences. D30 retention: 24% → 47%.

At monetization: whale-detector identifies high-value players early and flags them for VIP treatment – special access, early features, personal outreach from the team. Top 10% of players contribute 80% of revenue; identifying them in week 1 instead of month 3 compounds LTV dramatically. See our AI Marketing in the Privacy Era guide for the cookie-free methodology underlying this approach.

The Risks: What Agents Get Wrong

The Web3 Agentic Economy is not without serious risks. Protocols that deploy agents without understanding their failure modes will create new categories of harm – potentially at a scale and speed that human-operated systems never could. Responsible agentic deployment requires honest accounting of where agents fail.

Hallucination in financial decisions. LLMs can generate confident-sounding but factually wrong outputs. In a marketing context, a hallucinated recommendation wastes budget. In a compliance context, a hallucinated approval of a sanctioned wallet creates legal liability. The mitigation is architectural: agents making compliance or fraud decisions should call verified data sources (like ChainAware’s prediction API) rather than relying on LLM reasoning alone. The agent’s role is to orchestrate tool calls and synthesize verified outputs – not to generate financial assessments from training data.

Adversarial wallets that game agent scoring. If fraud detection is known to be based on behavioral patterns, sophisticated bad actors will study those patterns and create wallets designed to pass screening. This is the same arms race that exists in traditional fraud detection – and the same mitigation applies: continuous model retraining on new fraud patterns, ensemble models that make gaming any single signal insufficient, and human review of edge cases. ChainAware’s models are retrained continuously on new fraud data specifically to stay ahead of adversarial adaptation.

Over-automation without human oversight. Agents making high-stakes decisions without any human checkpoint are brittle. A model drift, a data quality issue, or an adversarial attack can cause systematic errors at machine speed and scale before anyone notices. The architecture should be: agents handle high-volume, low-stakes decisions autonomously; agents surface high-stakes decisions for human review with pre-built analysis. Never remove the human from irreversible, high-value decisions entirely.

False positives harming legitimate users. Any screening system generates false positives – legitimate users incorrectly flagged as risky. In human-operated systems, false positives are caught and corrected through human review. In fully automated systems, they can result in users being locked out of their funds with no recourse. The mitigation: always provide an appeal pathway for flagged users, monitor false positive rates continuously, and design tiered responses (additional verification) rather than binary block decisions for medium-risk cases.

Regulatory uncertainty around agentic compliance. Regulators in most jurisdictions have not yet clarified whether AI-generated compliance documentation satisfies human review requirements. A compliance agent that auto-generates SAR filings may or may not meet the regulatory standard for “reasonable investigation.” Legal review of your jurisdiction’s specific requirements is essential before deploying agentic compliance at scale.

How to Build Your First Agentic Web3 Stack in 2026

The right approach to agentic deployment is incremental. Start with one agent, measure its impact, then expand. Here is the recommended sequence for most protocols:

Step 1: Deploy fraud-detector at your highest-risk touchpoint. If you process withdrawals, put fraud-detector there. If you have a lending product, put it at loan origination. If you’re an exchange, put it at account creation. The ROI on fraud prevention is immediate and measurable – and it builds confidence in the technology before expanding to more complex agent functions. Start free: try the Fraud Detector with any wallet address, no account required.

Step 2: Clone the GitHub repository and configure your MCP server. Visit github.com/ChainAware/behavioral-prediction-mcp, clone the repository, and follow the setup instructions. The .claude/agents/ directory contains all 12 agent definition files – copy the ones relevant to your use case into your project.

Step 3: Get your MCP API key. Subscribe at chainaware.ai/mcp. All plans provide access to all 12 agents. Configure your API key in your environment and test with natural language queries against your AI agent of choice.

Step 4: Add onboarding-router as your second agent. The ROI on personalized onboarding is fast and highly visible – completion rates improve within the first week. This is also the agent with the clearest A/B test structure: run it for half of new users, compare onboarding completion and D7 retention against the control group.

Step 5: Add wallet-ranker to your acquisition channel reporting. Instrument your inbound channels with wallet ranking and let your growth team see quality scores alongside volume metrics for the first time. Most teams are shocked by how dramatically quality varies by channel. Budget reallocation follows naturally.

Step 6: Build toward full-stack multi-agent coordination. Once you’ve validated individual agents, design the coordination layer – how do agents share outputs, how does the output of wallet-ranker feed into onboarding-router’s routing decision, how does fraud-detector’s output trigger different flows in the transaction monitoring agent. This is where the compounding value of agentic infrastructure emerges.

For detailed technical implementation, including code samples, configuration files, and multi-agent orchestration patterns, see the complete MCP Integration Guide. According to a16z’s State of Crypto 2025 report, the protocols that successfully deploy agentic infrastructure in this window will have structural advantages that compound over multiple years – both in cost efficiency and in the behavioral data feedback loops that improve their models over time.

Frequently Asked Questions

Conclusion: The Infrastructure Window Is Open Now

The Web3 Agentic Economy is not a trend to watch – it’s a structural shift to build for. The protocols that deploy agentic infrastructure in 2026 will operate with fundamentally different economics, response speeds, and user experience quality than those that continue relying on human-operated functions. That gap compounds over time: better data, better models, better agent performance, lower cost per decision.

The enabling technology – capable LLMs, the MCP standard, behavioral prediction infrastructure – exists today. The 12 pre-built agent definitions in ChainAware’s GitHub repository cover the seven core functions that agentic protocols need: compliance, fraud detection, growth, onboarding, research, customer success, and treasury monitoring. The same behavioral intelligence that makes vitalik.eth’s spider chart look different from sassal.eth’s is the intelligence that tells your protocol how to treat each of those wallets differently – automatically, in real time, at any scale.

Every wallet has a unique behavioral identity. The Web3 Agentic Economy is the infrastructure that finally lets your protocol act accordingly.

About ChainAware.ai

ChainAware.ai is the Web3 Agentic Growth Infrastructure – the behavioral intelligence layer powering AI agents, DeFi protocols, exchanges, compliance teams, and enterprises. 14M+ wallets analyzed across 8 blockchains. 98% fraud prediction accuracy. 12 open-source MCP agents. Backed by Google Cloud, AWS, and ChainGPT Labs.

→ chainaware.ai | MCP: chainaware.ai/mcp | GitHub: behavioral-prediction-mcp | Free audit: chainaware.ai/audit

The post The Web3 Agentic Economy: How AI Agents Are Replacing Web3 Growth Teams first appeared on ChainAware.ai.

Traditional crypto AML tools answer one question: where did these funds come from? ChainAware’s Transaction Monitoring Agent answers a different and more operationally urgent question: which of your active users are likely to commit fraud in the future – and when did that risk change?

This guide explains what crypto transaction monitoring is, why AML alone is not sufficient for fraud protection, how ChainAware’s monitoring agent works, and how to integrate it into your Dapp in minutes via Google Tag Manager – no engineering required.

In This Guide

• What Is Crypto Transaction Monitoring?
• AML vs Transaction Monitoring: A Critical Distinction
• Why AML Alone Is Not Enough to Fight Fraud
• The Regulatory Mandate: Both Are Required
• How ChainAware Transaction Monitoring Works
• Reading the Predicted Fraud Probabilities Dashboard
• Continuous 24×7 Monitoring: Beyond First Connection
• Telegram Alerts: Real-Time Notifications When Risk Changes
• What to Do When Fraud Is Detected
• Integration: Google Tag Manager, No Code Required
• Ecosystem: How It Connects to ChainAware’s Other Tools
• Use Cases by Platform Type
• FAQ

What Is Crypto Transaction Monitoring?

Crypto transaction monitoring is the continuous, real-time process of analyzing wallet addresses that interact with a platform – screening them for fraud risk, tracking changes in their behavioral profiles over time, and triggering alerts or automated actions when risk thresholds are crossed.

In traditional finance, transaction monitoring is mandatory and universal. Every bank, payment processor, and financial institution routes 100% of transactions through real-time monitoring systems before settlement. These systems analyze the parties involved, the transaction amounts, timing patterns, historical behavior, and dozens of other signals simultaneously. The goal is both reactive (detect fraud that is occurring) and proactive (prevent fraud before it completes).

In the crypto context, transaction monitoring faces a different data environment: pseudonymous addresses, no personal data, no device fingerprints. What exists is a complete, public, immutable on-chain transaction history for every address – and it is precisely this behavioral history that predictive AI can analyze to identify fraud risk patterns.

According to the FATF (Financial Action Task Force) guidance on virtual assets, effective crypto compliance requires not just AML controls but ongoing transaction monitoring that identifies suspicious behavioral patterns – not just the provenance of funds. The regulatory direction is clear: transaction monitoring is becoming as mandatory in crypto as it is in traditional finance.

AML vs Transaction Monitoring: A Critical Distinction

AML (Anti-Money Laundering) and transaction monitoring are frequently conflated in crypto compliance discussions, but they address fundamentally different problems and provide different types of protection.

What Crypto AML Does

AML focuses on the origin of funds. Its core task is verifying that money entering a financial service comes from declared, legal sources – the distinction between “white money” (funds with a verifiable legal origin) and “black money” (funds derived from criminal activities or undeclared income).

In practice, crypto AML tools trace the on-chain history of funds through a network of prior transactions – identifying whether any funds in a wallet’s history have passed through sanctioned entities, darknet markets, ransomware payment addresses, exchange hack proceeds, or other criminal sources. The scale of money laundering that AML addresses is substantial: according to the United Nations FACTI Panel report, global money laundering flows are estimated at 2.7% of global GDP annually.

AML looks backward: it asks where money came from.

What Transaction Monitoring Does

Transaction monitoring focuses on predicting future behavior. Rather than asking where funds originated, it asks: based on this wallet’s behavioral patterns, is it likely to commit fraud against our platform or its users?

Transaction monitoring is not a one-time check at the point of connection. It is a continuous process that runs against every wallet in your user base – screening for behavioral changes that indicate elevated fraud risk, even in wallets that passed AML checks when they first connected.

Transaction Monitoring looks forward: it asks what a wallet will do next.

The Key Difference in Operational Scope

AML is typically run once, at onboarding. Transaction monitoring is continuous – it keeps running after a wallet has been admitted. A wallet that passes AML screening today can develop fraudulent behavioral patterns tomorrow. Without ongoing monitoring, the platform has no visibility into this change until the fraud has already occurred.

Why AML Alone Is Not Enough to Fight Fraud

The most important and underappreciated truth in crypto fraud protection is this: fraud is frequently committed with clean funds.

Sophisticated fraudsters understand that using funds with any connection to criminal activity is operationally dangerous – it creates a traceable link that can alert AML systems, trigger exchange flags, and expose their identity. So they don’t. Professional fraud operations use clean wallets funded through legitimate sources, often with carefully constructed transaction histories designed to appear legitimate.

This is the fundamental limitation of AML as a fraud prevention tool: it is designed to catch money laundering, not fraud. A scammer who has carefully funded their wallet through legitimate channels will pass any AML check. The AML system will show clean funds – because the funds are clean. The fraud hasn’t happened yet.

Transaction monitoring catches what AML misses. It does not look at where funds came from – it looks at how the wallet behaves. The behavioral patterns of a fraud operator – wallet preparation sequences, interaction patterns with known risky protocols, timing of fund movements, relationships with other flagged addresses – are identifiable through predictive AI analysis even when the funds themselves are clean.

According to Elliptic’s DeFi risk research, the most sophisticated crypto fraud operations specifically invest in creating clean-funded, operationally legitimate-appearing wallets as part of their attack infrastructure. These wallets are invisible to AML tools and only identifiable through behavioral pattern analysis.

The conclusion is clear: AML and transaction monitoring are not alternatives – they are complements. AML ensures funds are clean. Transaction monitoring protects against fraudsters who operate with clean funds. A complete security posture requires both.

The Regulatory Mandate: Both Are Required

Regulators around the world are increasingly explicit that crypto platforms must implement both AML controls and ongoing transaction monitoring – not as optional best practices but as compliance requirements.

The FATF’s updated guidance for virtual asset service providers (VASPs) explicitly requires risk-based transaction monitoring as part of a compliant AML/CFT program. The EU’s Markets in Crypto Assets (MiCA) regulation, which took effect in 2024, incorporates transaction monitoring requirements alongside AML obligations for crypto businesses operating in Europe. The US Financial Crimes Enforcement Network (FinCEN) applies similar requirements to money services businesses dealing in crypto.

For DeFi protocols and Dapp teams, the regulatory direction is clear even if specific mandates are still evolving: the standard of care is moving toward the requirements already applied to traditional financial services, which have always mandated both fund source verification (AML) and ongoing behavioral monitoring (transaction monitoring).

Implementing ChainAware’s Transaction Monitoring now – before regulatory mandates are finalized – positions Dapp teams ahead of the compliance curve rather than scrambling to catch up. For a complete view of how ChainAware’s tools map to compliance requirements, see the guide to using ChainAware as a business.

How ChainAware Transaction Monitoring Works

ChainAware’s Transaction Monitoring Agent is built on the same predictive AI engine as the Fraud Detector – but applied continuously and at scale to every wallet that interacts with your Dapp.

Step 1: Integration via ChainAware Pixel

Integration starts with the ChainAware Pixel – a lightweight tracking snippet deployed through Google Tag Manager. No engineering work is required: the Pixel is added to your GTM container in the same way as any analytics tag. Once deployed, it automatically detects wallet connection events on your Dapp and registers every connecting address with the ChainAware monitoring system.

This no-code integration means that security teams and product managers can deploy transaction monitoring without waiting for developer resources. From GTM setup to active monitoring typically takes less than 30 minutes.

Step 2: Initial Fraud Screening on Every New Connection

The moment a wallet connects to your Dapp, the Transaction Monitoring Agent runs it through the Fraud Detector. This generates an initial Trust Score (1 minus Fraud Score) for the address, drawing on ChainAware’s Predictive Data Layer of 14M+ pre-calculated wallet profiles. If the address is already in the database, the result is instant. If it’s a new address requiring fresh analysis, the real-time calculation completes in seconds.

This initial screening gives you an immediate fraud risk signal for every new user – before they have taken any significant action on your platform.

Step 3: Continuous 24×7 Re-Screening

This is where transaction monitoring differs fundamentally from one-time fraud checks. After the initial screening, every address that has ever connected to your Dapp is continuously re-screened – 24 hours a day, 7 days a week. The monitoring agent regularly re-runs the Fraud Detector analysis on your entire connected wallet database, not just new connections.

This continuous re-screening catches behavioral changes that occur after initial connection – the wallet that looked clean at signup but has since begun exhibiting fraudulent interaction patterns, the address whose Trust Score has dropped significantly, the user who has started transacting with known fraudulent counterparties.

Step 4: Aggregate Analytics Dashboard

The Transaction Monitoring dashboard aggregates the fraud probability distribution across your entire connected wallet base. The Predicted Fraud Probabilities view visualizes what percentage of your users fall into each risk category – giving your team an immediate read on the overall security health of your user base.

For a full breakdown of the 10-dimension analytics dashboard – including experience distribution, risk willingness, wallet intentions, and protocol categories – see the Web3 Behavioral Analytics complete guide.

Reading the Predicted Fraud Probabilities Dashboard

The Predicted Fraud Probabilities chart is the core security health metric of the Transaction Monitoring dashboard. It shows the distribution of Trust Scores across your entire connected wallet base, bucketed into risk tiers.

A healthy Dapp user base typically shows the vast majority of wallets in the low-risk bucket (Trust Score above 70%), a small proportion in the medium-risk watch zone, and a very small tail of high-risk addresses. If your distribution shows an unusually high proportion of wallets in the elevated-risk buckets, this signals either that your acquisition channels are attracting low-quality wallet traffic or that your platform has been specifically targeted by fraud operations.

The distribution also changes over time – monitoring the trend of your fraud probability distribution is as important as the snapshot. A distribution shifting toward higher risk over weeks indicates emerging fraud exposure that needs to be addressed before it manifests in actual attacks.

This aggregate view connects directly to ChainAware’s Web3 User Analytics platform, which provides the full behavioral intelligence picture: not just fraud probability distribution but also wallet experience levels, risk willingness, predicted intentions, protocol categories, and Wallet Rank distribution – giving Dapp teams a complete picture of who is actually using their platform.

Continuous 24×7 Monitoring: Beyond First Connection

The most operationally significant feature of ChainAware’s Transaction Monitoring is its continuous re-screening capability. Most fraud detection implementations check wallets once – at connection or registration – and never revisit them. This creates a critical blind spot: a wallet’s risk profile is not static.

Consider these scenarios that one-time screening would miss entirely:

A wallet connects to your lending protocol with a Trust Score of 85% – clean, established, apparently legitimate. Over the following three weeks, this wallet begins accumulating positions with other DeFi protocols in a pattern consistent with a coordinated liquidity attack. Its Trust Score drops to 42%. Without continuous monitoring, your platform has no visibility into this change until the attack executes.

A wallet connects to your NFT marketplace with a moderate Trust Score. Two months later, it begins engaging with known wash-trading rings, and its behavioral profile shifts significantly. A continuous monitoring system catches this change and flags the wallet for review. A one-time screen never would.

This is the fundamental value proposition of 24×7 monitoring: fraud risk is a dynamic property of wallets, not a static one. The monitoring system that only checks at connection will always be behind the threat. Continuous re-screening keeps your platform’s risk intelligence current.

According to research from the Bank for International Settlements on crypto market surveillance, behavioral patterns that precede fraud typically develop over days to weeks before the fraud executes – making continuous monitoring the only approach capable of catching risk before harm occurs.

Telegram Alerts: Real-Time Notifications When Risk Changes

Continuous monitoring is only actionable if it generates timely alerts when risk thresholds are crossed. ChainAware’s Transaction Monitoring Agent delivers alerts via Telegram – a channel that Dapp teams are already using for community management and operational communications.

When a wallet’s Trust Score drops below a configured threshold – or changes significantly from its last recorded score – the monitoring agent sends an immediate Telegram notification to the designated channel or user. The alert includes the wallet address, the current Trust Score, the direction of change, and the network.

This alert architecture means your security team has real-time visibility into risk changes across your entire user base, regardless of whether they are actively monitoring the dashboard. A wallet that went from 78% Trust Score to 31% overnight triggers an alert the moment the re-screening detects the change – giving your team time to act before the wallet has taken any harmful action on your platform.

Configuring Telegram integration is straightforward – connect your Telegram bot to the ChainAware dashboard and set your risk threshold preferences. Alerts can be configured for different severity levels: a watch alert for moderate Trust Score declines, and a critical alert for wallets crossing into high fraud risk territory.

What to Do When Fraud Is Detected

When the Transaction Monitoring Agent identifies a high-risk wallet – either at initial connection or through continuous re-screening – your team has three options. Each has different operational implications.

Option 1: Shadow Ban

A shadow ban allows the flagged wallet to continue using your platform normally from their perspective – they can browse, interact, and navigate as usual. However, behind the scenes, the platform blocks or delays their ability to execute transactions. This is the most operationally nuanced option: it prevents harm without alerting the potentially fraudulent actor that they have been flagged, which can prevent them from immediately switching to a new wallet and reconnecting.

Shadow banning is particularly useful when you have a moderate-confidence fraud signal (Trust Score in the elevated-risk range but not conclusively high) and want to limit exposure while gathering more information.

Option 2: Ban

An outright ban blocks the flagged wallet from accessing the platform entirely. This is the appropriate response to high-confidence fraud signals – wallets with Trust Scores indicating very high fraud probability or wallets that have already triggered transaction-level fraud alerts.

The justification for banning is straightforward: if your monitoring system has identified that a wallet is highly likely to commit fraud, and you have that information, the responsible action is to prevent access. Continuing to allow a known high-risk wallet to interact with your platform exposes your legitimate users to risk and may create compliance liability.

Option 3: Do Nothing

The monitoring system supports a “do nothing” action option – but it is explicitly not recommended. If your platform knows that a connected wallet has a high probability of committing fraud, taking no action means knowingly accepting that risk. This creates both direct financial exposure (the fraud your platform facilitates or suffers) and potential regulatory exposure (failure to act on known risk signals).

The appropriate use of “do nothing” is for wallets in the low-to-moderate risk range where the signal is not yet strong enough to justify restriction – combined with continued monitoring so that if the risk score increases, the automated alert pipeline triggers a review.

Integration: Google Tag Manager, No Code Required

The ChainAware Transaction Monitoring Agent integrates into any Dapp through the ChainAware Pixel, deployed via Google Tag Manager. The integration process requires no smart contract changes, no backend engineering, and no frontend code modifications.

The setup process involves: creating a ChainAware account at chainaware.ai; adding the ChainAware Pixel tag to your Google Tag Manager container; configuring the trigger (typically “Wallet Connected” events); and connecting your Telegram channel for alert delivery.

This GTM-based integration model is the same approach used for Web3 Behavioral Analytics – a single Pixel deployment activates both the analytics dashboard and the transaction monitoring system simultaneously. Teams that have already deployed the ChainAware Pixel for analytics get transaction monitoring as an additional layer at no additional integration cost.

For teams who want deeper programmatic integration – querying fraud scores via API, building custom alerting logic, or integrating behavioral profiles directly into AI agent workflows – the Prediction MCP provides full developer access to the ChainAware Predictive Data Layer. See the Prediction MCP developer guide for integration details.

Ecosystem: How It Connects to ChainAware’s Other Tools

The Transaction Monitoring Agent is one layer in ChainAware’s broader Predictive Intelligence Stack. Understanding how it connects to the other tools clarifies which to use when.

The Fraud Detector is the on-demand tool for checking individual wallet addresses – useful for manual due diligence before a specific transaction or business relationship. Transaction Monitoring is the automated, always-on version of the same capability applied to your entire user base continuously.

The Wallet Auditor provides the deepest single-wallet intelligence – Trust Score, AML status, experience level, risk willingness, intentions, and Wallet Rank – in a single view. When a Transaction Monitoring alert flags a specific wallet, the Wallet Auditor is the natural next step for deep investigation.

The Rug Pull Detector covers the contract-address dimension – assessing whether pools and contracts your users are interacting with represent rug pull risk. Together with Transaction Monitoring, it covers both the user side and the contract side of fraud exposure.

For Dapp growth teams, the same behavioral intelligence that powers fraud monitoring also powers personalization: Growth Agents use wallet behavioral profiles to deliver personalized experiences to legitimate users – the security and growth use cases share the same underlying data layer.

Use Cases by Platform Type

DeFi Lending Protocol

Lending protocols face exposure to fraudulent borrowers who take out loans with no intention to repay – particularly as undercollateralized or social-collateral lending models become more common. Transaction Monitoring screens every wallet that connects to your protocol and continuously monitors their risk profiles. When a borrower’s Trust Score drops significantly after taking a loan position, an alert triggers – giving your team early warning of potential default risk from fraudulent actors, not just creditworthiness signals.

NFT Marketplace

NFT marketplaces are targets for wash trading, fraud, and manipulation. Transaction Monitoring identifies wallets with behavioral patterns associated with wash trading rings, coordinated bid manipulation, and counterfeit collection operations – and monitors their activity on your platform continuously. Shadow banning high-risk wallets allows the platform to limit their transactional impact while gathering evidence before a full ban.

GameFi Platform

Play-to-earn and GameFi platforms attract bot farms and exploit operations that drain rewards designed for genuine players. Transaction Monitoring identifies wallet behavior inconsistent with genuine gameplay – bot-like transaction patterns, relationships with known airdrop farming operations, and low Trust Scores – and flags these wallets for review or automated restriction.

Crypto Exchange or On-Ramp

Exchanges face regulatory requirements for both AML and transaction monitoring. ChainAware’s system provides the transaction monitoring layer that complements existing AML tooling – screening depositing wallets with predictive AI and monitoring all connected accounts for risk score changes that should trigger enhanced due diligence or account restrictions.

Frequently Asked Questions

What is the difference between AML and transaction monitoring?

AML (Anti-Money Laundering) verifies the origin of funds – it asks where money came from and whether it has any connection to criminal sources. Transaction monitoring predicts future behavior – it analyzes wallet behavioral patterns to identify fraud risk before the fraud occurs. Both are required for complete protection. AML misses fraud committed with clean funds; transaction monitoring catches behavioral risk signals regardless of fund origin.

Does the ChainAware Pixel require changes to my smart contract?

No. The ChainAware Pixel is a frontend integration deployed via Google Tag Manager – it requires no changes to your smart contracts, no backend modifications, and no frontend code changes beyond adding the GTM tag. Setup typically takes less than 30 minutes.

What happens when a wallet’s risk score changes?

If you have connected your Telegram channel, you receive an immediate notification when a monitored wallet’s Trust Score drops below your configured threshold. You can then choose to shadow ban (block transactions while allowing browsing), ban (block platform access entirely), or continue monitoring. Doing nothing when a high-risk signal is detected is not recommended.

How often are wallets re-screened?

Every wallet that has connected to your Dapp is continuously re-screened 24×7. The re-screening frequency is designed to catch behavioral changes as they develop – giving you early warning before fraud executes rather than forensic information after the fact.

What is shadow banning and when should I use it?

Shadow banning allows a flagged wallet to continue using your platform normally from their perspective while blocking or delaying their ability to execute transactions behind the scenes. It is best used for moderate-confidence fraud signals where you want to limit exposure without alerting the potentially fraudulent actor – who might immediately switch to a new wallet and reconnect if they knew they were flagged.

Can I integrate this into my own AI agent or backend system?

Yes. The Prediction MCP provides full programmatic access to ChainAware’s Predictive Data Layer – including fraud scores, Trust Scores, behavioral profiles, and wallet intentions – via API. See the Prediction MCP developer guide for integration details and code examples.

Is transaction monitoring only for compliance, or does it have business value too?

Both. From a compliance perspective, transaction monitoring addresses regulatory requirements that are already in force for traditional finance and increasingly being applied to crypto. From a business perspective, protecting your platform from fraud protects your legitimate users’ experience, your platform’s reputation, and your team’s time spent on fraud remediation. The same ChainAware Predictive Data Layer that powers fraud monitoring also powers growth tools – so the security investment directly enables personalization and conversion improvements.

The post ChainAware Transaction Monitoring Agent: Complete Guide to 24×7 Dapp Fraud Protection first appeared on ChainAware.ai.

Rug pulls are the defining scam of the DeFi era. Unlike hacks or exploits that require technical sophistication, rug pulls are engineered through social manipulation: a professional operation creates a token, builds hype through paid influencers and Telegram groups, attracts liquidity from retail investors, and then exits – draining the pool and leaving holders with worthless tokens. The entire process can take days to weeks. The financial damage to investors is typically 100% of their position.

The scale of the problem is significant. Research suggests that the vast majority of new DeFi pools on high-activity chains never survive their first month. On PancakeSwap alone, 95% of pools end in rug pulls. The challenge for investors is that every rug pull looks legitimate at launch – the social engineering is professional, the messaging is compelling, and the early price action is designed to build confidence before the exit.

ChainAware’s Predictive Rug Pull Detector takes a different approach to identifying these risks: instead of analyzing smart contract source code (which requires technical expertise and can be obfuscated), it analyzes the behavioral Trust Scores of the people behind the contract – the creator and the liquidity providers. Good contracts are built by trusted actors. Bad contracts are typically built by new, anonymous, or low-trust addresses. This guide explains everything you need to know.

What Is a Rug Pull in Web3?

A rug pull is a type of exit scam specific to DeFi. The term comes from the expression “pulling the rug out” – the moment when the people behind a project withdraw all liquidity or drain the contract, leaving investors holding tokens with no backing and no exit.

Rug pulls typically follow one of two structural patterns. In a liquidity rug, the project team adds liquidity to a decentralized exchange pool to create a tradeable market for their token, attracts retail investment, and then removes all liquidity at once – crashing the token price to zero and leaving buyers unable to sell. In a backdoor rug, the smart contract itself contains a hidden function (often an unlimited mint, a privileged withdrawal, or a trading restriction for non-insiders) that allows the developers to drain funds or trap holders, regardless of the liquidity status.

What distinguishes rug pulls from other types of crypto fraud is the degree of premeditation and social engineering involved. A rug pull is not a hack or an accidental exploit – it is a deliberate plan executed by a team that builds the entire project for the purpose of the exit. According to Chainalysis’s research on crypto scam revenue, rug pulls and exit scams consistently rank among the highest-revenue fraud categories in the crypto ecosystem, with losses running into hundreds of millions annually.

How Rug Pulls Are Engineered: The Professional Scam Playbook

Rug pulling is not a cottage industry of opportunistic scammers. It is a professional operation with defined roles, repeatable playbooks, and increasingly sophisticated social engineering techniques. Understanding how rug pulls are constructed is essential to understanding why they’re so difficult to detect – and why behavioral analysis of the people behind the contract is more reliable than analysis of the contract itself.

Phase 1: Creating the Narrative

Every rug pull starts with a compelling story. The token solves a real problem, taps into a hot trend (AI, real-world assets, gaming, memecoins), and is positioned to be the “next big thing.” The narrative is designed to create urgency and FOMO. The whitepaper (if one exists) is polished and professional. The team may be anonymous but presents credible-seeming credentials.

Phase 2: Building the Hype Machine

Once the narrative is established, the hype machine activates. Paid KOLs (Key Opinion Leaders) on Twitter/X and YouTube post enthusiastic reviews. Telegram and Discord groups are seeded with thousands of members – many of them paid shills who post constantly about price targets and “100x potential.” The volume of positive messaging creates the illusion of organic community excitement. New investors see thousands of people talking about the project and interpret it as social proof.

The KOL problem in crypto is well-documented. As explored in our analysis of why influencer marketing isn’t working in Web3, many crypto KOLs promote projects for undisclosed fees without any due diligence – making them unwitting (or complicit) participants in the rug pull machinery.

Phase 3: The Price Pump

With hype established, the token price is pumped – often through coordinated buying among insiders, wash trading, and genuine retail FOMO from the social engineering in Phase 2. Early investors see rapid price appreciation, which creates additional urgency for latecomers. The pump generates screenshots of gains that are shared across social channels, amplifying the hype further.

This phase often overlaps with the pump-and-dump mechanics described in our dedicated guide – though in a rug pull, the exit mechanism is the liquidity drain rather than insiders selling their holdings.

Phase 4: The Exit

At peak hype and peak price, the rug pull executes. Liquidity is removed in a single transaction, or a backdoor function is triggered, or the team simply abandons the project and stops maintaining the contract. The token price collapses to near-zero within minutes. Holders are left with tokens they cannot sell, or can only sell at a 95-99% loss. The team moves the extracted funds through mixers or cross-chain bridges and prepares to launch the next project.

Why This Pattern Repeats

The rug pull cycle repeats because it is profitable and the barrier to entry is low. A new token can be launched in hours. A professional rug pull operation can run multiple projects simultaneously. The social engineering skills compound over time – each project is more convincing than the last. According to Immunefi’s annual Web3 security report, exit scams and rug pulls account for a significant and growing share of total crypto losses each year.

The Scale of the Problem: 95% of Pools

The most striking data point in DeFi security is this: approximately 95% of pools launched on PancakeSwap end in rug pulls. This is not a marginal problem affecting only careless investors – it is the dominant outcome for new DeFi pools on one of the world’s largest decentralized exchanges.

The implication is sobering: if you invest in a new PancakeSwap pool without any due diligence, your base rate expectation should be that it will rug pull. The 5% of legitimate projects are the exception, not the norm. Any tool that can identify even a portion of the 95% before the exit represents enormous value for investors.

This is precisely the problem the ChainAware Rug Pull Detector is designed to address. It does not claim to catch every rug pull – its 68% accuracy is honest about the limits of behavioral analysis without source code inspection. But identifying 68 out of every 100 rug pulls before they happen, from a free tool that takes seconds to use, represents a meaningful improvement over investing blind.

How the Rug Pull Detector Works

The ChainAware Rug Pull Detector is built on a core insight: a good contract can only be created by a trusted creator with trusted liquidity providers. Conversely, a bad contract will almost always have either a low-trust creator, low-trust liquidity providers, or both. By analyzing the behavioral Trust Scores of the addresses behind a contract rather than the contract’s source code, the detector identifies rug pull risk from the human pattern – not the technical one.

Step 1: Identify the Contract Creator

When you submit a contract address to the Rug Pull Detector, the first step is identifying the creator of that contract – the wallet address that deployed it. The detector runs this creator address through the ChainAware Fraud Detector to generate a Trust Score (1 minus the Fraud Score). A creator with a high Trust Score has a long, legitimate transaction history with behavioral patterns consistent with genuine builders. A creator with a low Trust Score, or a new address with minimal history, is a significant red flag.

Step 2: Trace Through Contract Creators

If the contract was deployed by another contract rather than a direct wallet address, the Rug Pull Detector traces through the chain of contracts until it reaches an underlying wallet address. Rug pull operators sometimes try to obscure their identity by routing deployment through intermediate contracts – this tracing step ensures the detector always reaches the human actor behind the contract.

Step 3: Analyze Liquidity Providers

After assessing the creator, the detector analyzes the liquidity providers (LPs) – the addresses that have added liquidity to the pool. Liquidity providers are critically important in rug pull detection because the exit mechanism in a liquidity rug pull is the LP removing their position. An LP with a low Trust Score or a new address adding significant liquidity is a strong indicator that the liquidity is “hot” – positioned for a quick exit rather than genuine market making.

Step 4: Generate the Rug Pull Risk Score

Based on the combined Trust Scores of the creator and liquidity providers, the detector generates an overall Rug Pull Risk probability. Key signals that elevate the risk score include: a new address as contract creator (new addresses have no behavioral history to establish trust); a new address adding liquidity (new LP addresses are a classic rug pull setup); low Trust Scores on creator or LPs (behavioral patterns inconsistent with legitimate actors); and lack of transparency – addresses that appear to be deliberately obscuring their history.

Conversely, risk scores are lowered when the creator has a long, clean on-chain history; liquidity providers have established Trust Scores; and the addresses are transparent – not routing through mixers or obfuscation layers.

Relationship to the Fraud Detector

The Rug Pull Detector and the Fraud Detector are complementary tools addressing different types of addresses:

The Fraud Detector analyzes regular wallet addresses (externally owned accounts) and predicts the probability that the address will commit fraud in the future. It works by identifying behavioral interaction patterns in the wallet’s transaction history that are characteristic of fraudulent activity.

The Rug Pull Detector analyzes smart contract addresses – specifically pools and protocol contracts – and predicts the probability of a rug pull. It does this by applying the Fraud Detector’s behavioral analysis to the human addresses behind the contract: the creator and the liquidity providers.

In other words: the Rug Pull Detector uses the Fraud Detector as its engine, but applies it to the people behind a contract rather than to any individual wallet. The relationship is: wallet risk = Fraud Detector; contract risk = Rug Pull Detector (which uses Fraud Detector internally).

For the full decision guide on which tool to use: checking a wallet address before a payment → Fraud Detector. Checking a contract or pool before investing → Rug Pull Detector. Full behavioral audit of a wallet → Wallet Auditor.

Accuracy: 68% Without Source Code

The current prediction accuracy of the ChainAware Rug Pull Detector is 68%. This means the algorithm correctly identifies 68 out of every 100 rug pulls based solely on address behavioral analysis – without reading or analyzing smart contract source code.

This number deserves context. 68% accuracy from behavioral analysis alone is a meaningful achievement for several reasons. First, smart contract source code can be obfuscated, copied from legitimate projects, or written to appear safe while containing hidden exploits – making source code analysis unreliable against sophisticated rug pull operators. Second, address behavioral patterns are much harder to fake: building a wallet with a legitimate-looking multi-year transaction history requires genuine time and on-chain activity. Third, the 68% figure comes from pure behavioral signal – no code inspection, no team identity verification, no social media analysis.

The honest implication is that the Rug Pull Detector is best used as a fast pre-screening tool. A high rug pull risk score is a strong signal to pause and investigate further. A low risk score is reassuring but not a guarantee – the remaining 32% of rug pulls that the tool misses are typically executed by more sophisticated operators who invest in building legitimate-looking creator histories before the exit.

According to Elliptic’s DeFi risk analysis, the most sophisticated rug pull operations specifically invest in establishing credible on-chain histories before deploying scam contracts – which is precisely the category the 32% miss rate captures. For high-value investments, combining the Rug Pull Detector with source code analysis from specialized audit tools provides the most complete risk picture.

Key Red Flags the Detector Identifies

New contract creator address. If the wallet that deployed the contract was created recently with few prior transactions, there is no behavioral history to assess. Legitimate builders typically deploy from wallets with established on-chain histories. A fresh deployment address is one of the strongest rug pull signals, because rug pull operators routinely create new wallets for each project to avoid connecting their new scam to their previous exit history.

Low Trust Score on the creator. A creator address with an established but low Trust Score is arguably even more dangerous than a new address – it means the wallet has a behavioral history, and that history includes patterns associated with fraudulent activity. This is the profile of a repeat rug pull operator who has built some on-chain history but whose interaction patterns still betray their intent.

New liquidity provider addresses. Liquidity added by freshly-created addresses is a classic rug pull setup. New LP addresses have no behavioral track record, and their liquidity is statistically likely to be “hot” – intended for rapid removal rather than genuine market making. The Rug Pull Detector flags new LP addresses prominently because the liquidity removal is the mechanism of the exit.

Low Trust Score on liquidity providers. LPs with established but low Trust Scores suggest that the liquidity is being provided by entities with fraudulent behavioral histories – potentially the same rug pull ring operating under different addresses.

Hidden or obfuscated creator chain. When the contract was deployed through a chain of intermediate contracts that obscures the ultimate creator, this is itself a red flag. Legitimate builders have no reason to obscure the chain of contract creation. The Rug Pull Detector notes when it has had to trace through multiple layers to find the underlying creator address.

How to Use the Rug Pull Detector

Navigate to chainaware.ai/rug-pull-detector. Connect your wallet for free access. Enter the contract address of the pool or token you want to assess and select the appropriate blockchain network.

The detector returns a Rug Pull Risk score alongside the individual Trust Scores of the contract creator and key liquidity providers. Review the scores in context: a single low-trust LP among several high-trust LPs is less alarming than a low-trust creator – the creator is the most important signal, followed by the largest liquidity providers.

Use the result as a pre-screening filter. A high rug pull risk score (above 0.7) should prompt you to either avoid the investment entirely or conduct significantly deeper due diligence before committing. A low risk score (below 0.3) is encouraging but not a guarantee – remember the 32% miss rate for sophisticated operators.

For any wallet address in the results that you want to investigate further, use the Wallet Auditor for a full behavioral profile including Trust Score, AML status, experience level, risk willingness, and Wallet Rank.

Why Address Analysis vs Source Code Analysis?

Most rug pull detection tools on the market analyze smart contract source code – looking for specific dangerous patterns like unlimited mint functions, trading restriction mechanisms, or privileged withdrawal functions. This approach has real value but significant limitations.

Source code analysis requires the source code to be available and verified. Many rug pull contracts are not verified on-chain, making code analysis impossible. Even when verified, professional rug pull operators copy audited, legitimate contract code as a base – hiding exploits in subtle modifications that automated tools miss. Code analysis also requires technical expertise to interpret meaningfully; most retail investors cannot read Solidity.

Address behavioral analysis sidesteps all of these limitations. The behavioral history of a wallet cannot be faked in real-time – it is the accumulated record of every transaction that address has ever made. A rug pull operator cannot instantly create the on-chain profile of a legitimate builder. This is the core advantage of ChainAware’s approach: the signal is in the people, not the code.

The two approaches are complementary. For maximum security on high-value investments, combine the Rug Pull Detector’s behavioral screening with source code analysis from a specialized audit service. For rapid pre-screening of new pools before allocating capital, the Rug Pull Detector’s free, instant, no-technical-expertise-required analysis provides actionable signal that most investors currently have no access to.

Where It Fits in the ChainAware Ecosystem

The Rug Pull Detector sits at the intersection of ChainAware’s fraud intelligence and its broader Predictive Data Layer. It uses the same underlying Trust Score engine as the Fraud Detector, applied specifically to the contract context. The 14M+ wallet behavioral profiles in ChainAware’s Predictive Data Layer power the instant Trust Score lookups that the Rug Pull Detector relies on for creator and LP assessment.

For token-level due diligence – assessing the quality of a token’s existing holder base rather than its pool creator – the Token Rank provides a complementary signal: a token whose holders have high average Wallet Ranks is less likely to be a rug pull operation than one dominated by low-quality wallets.

For Dapp teams who want to integrate rug pull risk screening into their own products, the full Predictive Data Layer is accessible via the Prediction MCP – enabling AI agents to query Trust Scores, fraud probabilities, and behavioral profiles programmatically in real time.

Real-World Use Cases

1. New Pool Investor: Pre-Investment Screening

You’ve seen a new token trending on Telegram and Twitter/X. Before committing any capital, run the contract address through the Rug Pull Detector. If the creator is a new address or has a low Trust Score, the hype is almost certainly manufactured. Close the Telegram tab and move on. If the creator and LPs have high Trust Scores and established histories, you have one positive signal among several you should gather before investing.

2. Liquidity Provider: Before Adding to a New Pool

Providing liquidity in a pool where one of the other LPs has a low Trust Score exposes you to coordinated liquidity removal risk – where insiders drain the pool before you can react. Checking the Trust Scores of existing LPs before adding your own liquidity takes seconds and can prevent significant losses.

3. Token Project Team: Establishing Legitimacy

Legitimate project teams can use the Rug Pull Detector proactively – sharing their high Trust Score results publicly as evidence that the contract creator and LPs have established, legitimate behavioral histories. In a market where 95% of pools rug pull, a verifiable low rug pull risk score is a genuine competitive differentiator for attracting cautious investors.

4. DeFi Aggregator or Launchpad: Automated Screening

Platforms that list new tokens or pools can integrate the Rug Pull Detector’s behavioral screening as an automated gate – surfacing risk scores alongside pool listings to help users make more informed decisions. For automated API integration, see the Prediction MCP developer guide.

5. Portfolio Manager: Ongoing Monitoring

The behavioral profiles of contract creators and LPs can change over time as they interact with more protocols. Periodic re-screening of pools you’re already invested in – particularly if you notice unusual price or volume behavior – can provide early warning of elevated rug pull risk before the exit executes.

Frequently Asked Questions

What is the difference between the Rug Pull Detector and the Fraud Detector?

The Fraud Detector analyzes regular wallet addresses and predicts the probability of fraud. The Rug Pull Detector analyzes smart contract addresses (pools, token contracts) and predicts the probability of a rug pull – it does this by applying the Fraud Detector’s Trust Score analysis to the contract’s creator and liquidity providers.

Does the Rug Pull Detector read smart contract source code?

No. The Rug Pull Detector analyzes address behavioral patterns only – the Trust Scores of the contract creator and liquidity providers. It does not inspect, read, or analyze smart contract source code. This makes it accessible to non-technical users and effective even when source code is not publicly verified.

What does 68% accuracy mean in practice?

It means the algorithm correctly identifies 68 out of every 100 rug pulls based on behavioral signals alone. The 32% it misses are typically from more sophisticated operators who invest in building legitimate-looking creator histories. Use the detector as a fast pre-screening tool: a high risk score is a strong red flag; a low risk score is encouraging but not a guarantee.

Why is a new creator address a red flag?

Because rug pull operators routinely create fresh wallets for each project to disconnect their new scam from their previous exit history. A new address has no behavioral history, making Trust Score assessment impossible – and statistically, new deployment addresses are strongly associated with rug pull activity versus legitimate builders who deploy from established wallets.

Is the Rug Pull Detector free?

Yes – completely free. Connect your wallet for access and run as many checks as you need. No subscription, no credits, no fee per lookup.

Can I use this on any blockchain?

The Rug Pull Detector supports the same networks as the Fraud Detector: Ethereum, Binance Smart Chain, Base, Polygon, Haqq, Solana, TON, and Tron.

What should I do if a pool shows high rug pull risk?

Treat it as a strong signal to avoid the investment or conduct significantly deeper due diligence before committing capital. Check the individual wallet addresses flagged using the Wallet Auditor for full behavioral profiles. Consider combining with source code analysis from a specialized audit service for high-value investments.

The post ChainAware Rug Pull Detector: Complete Guide to AI-Powered DeFi Contract Risk Detection first appeared on ChainAware.ai.

Most crypto fraud detection tools work by looking backwards. They maintain databases of known bad addresses – addresses already caught committing fraud, flagged by exchanges, or listed in blockchain forensics databases. If an address appears on the list, it’s flagged. If it doesn’t, it passes.

The problem with this approach is obvious: every fraudster starts with a clean address. By the time an address makes it onto a forensic database, the damage is done.

ChainAware’s Predictive Fraud Detector works differently. Instead of checking whether an address is already known to be bad, it analyzes the address’s on-chain transaction history to identify behavioral patterns characteristic of fraudulent activity – and predicts whether fraud is likely to occur in the future. The result is a fraud risk score that flags dangerous addresses before they cause harm, not after.

This guide covers everything you need to know: how the Fraud Detector works, what makes it different from AML and traditional forensics, when to use it, and where it fits in the broader crypto security stack.

What Is the ChainAware Fraud Detector?

The ChainAware Fraud Detector is a free, real-time predictive AI tool that analyzes any regular wallet address on supported blockchain networks and outputs a fraud probability score between 0 and 1. A score close to 0 indicates low fraud risk. A score close to 1 indicates high fraud risk.

The current predictive accuracy of the underlying AI model is 98% – meaning the algorithm correctly identifies 98 out of every 100 fraud cases. This is not a forensic algorithm based on already-listed bad addresses or blockchain analytics flags. It is a predictive algorithm trained to recognize the on-chain behavioral patterns that precede fraudulent activity.

Key facts about the Fraud Detector: it is free to use (connect your wallet and run the check); real-time (reads live blockchain history, analyzes it, and returns results instantly); predictive, not forensic (identifies future risk from behavioral patterns, not past database entries); part of the Predictive Data Layer with 14M+ wallets pre-calculated; and supports 8 networks – Ethereum, Binance Smart Chain, Base, Polygon, Haqq, Solana, TON, and Tron.

How It Works: Predictive AI vs Forensic Lookup

Understanding the distinction between predictive fraud detection and forensic fraud detection is essential to understanding the Fraud Detector’s value.

Forensic Fraud Detection (Traditional)

Traditional blockchain fraud detection tools are forensic: they maintain curated databases of addresses that have already been linked to fraudulent activity – stolen funds, sanctioned entities, phishing operations, exchange hacks, and other known criminal incidents. When you query an address, the tool checks whether that address appears in its database. If yes, flagged. If no, clean.

The fundamental limitation is temporal: every fraudster starts with a fresh address. Before they commit fraud, they are invisible to forensic tools. The database only catches them after the harm is done – and only if the incident was reported, investigated, and added to the relevant database, which can take weeks or months.

Predictive Fraud Detection (ChainAware)

ChainAware’s Fraud Detector takes a fundamentally different approach. It does not check a database of known bad actors. Instead, it reads the entire transaction history of the address being queried – every interaction, every counterparty, every timing pattern – and runs that history through a predictive AI model trained to recognize the behavioral signatures of fraudulent activity.

The core insight is this: every scam is unique, but scammers follow recognizable interaction patterns. Fraud is not random. It involves specific sequences of behavior – wallet preparation patterns, interaction with mixing services, timing of fund movements, relationships with other flagged addresses, protocol interaction patterns, and dozens of other behavioral signals that appear consistently in the transaction histories of addresses that eventually commit fraud.

The ChainAware AI model was trained on two data sets: confirmed fraud addresses (with known fraudulent histories) and confirmed legitimate addresses (with verified clean histories). By learning to distinguish the behavioral patterns of these two sets, the model can classify new addresses based on their behavioral fingerprint – before any fraud has been publicly reported.

According to Chainalysis’s crypto crime research, illicit on-chain activity follows identifiable behavioral patterns that persist across different types of fraud and different market cycles. Predictive models trained on these patterns consistently outperform purely forensic approaches in early fraud detection.

Pre-Calculated vs Real-Time Results

The ChainAware Predictive Data Layer contains pre-calculated fraud scores for over 14 million wallet addresses. When you query an address that’s already in the database, the result is returned instantly – the last calculated score is shown immediately. Users can choose to request a fresh real-time recalculation. For addresses with extensive transaction histories, this real-time analysis typically takes 3-4 seconds as the algorithm reads the full blockchain history and runs the predictive model against it.

Fraud Detector vs AML: Understanding the Difference

Crypto AML (Anti-Money Laundering) and fraud detection are often conflated, but they address fundamentally different problems with different methods and different objectives.

What Is Crypto AML?

AML focuses on verifying the origin of funds – specifically, ensuring that money entering a financial service or protocol has come from declared, legal sources. The distinction AML enforces is between “white money” (funds with a verifiable, legal origin) and “black money” (funds derived from criminal activities or hidden from tax authorities).

The scale of the problem AML addresses is significant. According to the United Nations’ FACTI Panel report, global money laundering flows are estimated at approximately 2.7% of global GDP annually – trillions of dollars flowing through financial systems while disguising their criminal origins.

AML looks backwards: it asks where money came from.

What Is Fraud Detection?

Fraud detection focuses on predicting whether an address is likely to engage in fraudulent behavior in the future – not whether its funds are clean in the present. The ChainAware Fraud Detector is not asking “are these funds from a legal source?” It is asking “based on this address’s behavioral history, is it likely to commit fraud?”

Fraud Detection looks forward: it asks what an address will do next.

AML and fraud detection are complementary rather than substitutable. A complete crypto security posture requires both: AML ensures funds are clean, fraud detection identifies dangerous counterparties before you transact with them. The ChainAware Wallet Auditor combines both dimensions – showing Predicted Trust (the inverse of Fraud Score), AML status, and the full behavioral profile – in a single view.

What Is Crypto Transaction Monitoring?

Transaction monitoring is a compliance and security discipline that applies both AML and fraud detection continuously to every transaction in real time. In traditional financial institutions, every transaction is routed through real-time monitoring systems before settlement – analyzing the parties involved, the amount, the timing, and historical patterns of both sender and receiver.

Crypto transaction monitoring faces a different data environment: pseudonymous addresses, no personal data, no device fingerprints, no declared income. What it does have is a complete, public, immutable transaction history for every address – which is precisely what ChainAware’s predictive AI uses. The behavioral fingerprint encoded in an address’s on-chain history is, in many respects, more reliable than self-reported identity data.

The ChainAware Fraud Detector is a core component of crypto transaction monitoring. The relevance of this use case is substantial: according to Artemis Analytics’ analysis of Ethereum transactions, approximately 50% of all Ethereum transactions are stablecoin payment transactions – real-world value transfers between parties. Most fraud detection tools focus on protocol interactions. The ChainAware Fraud Detector focuses specifically on the payment transaction layer: verify the recipient before you send.

How to Use the Fraud Detector – Real Example: vitalik.eth

Using the ChainAware Fraud Detector is straightforward. Navigate to chainaware.ai/fraud-detector, connect your wallet, and enter the address you want to check. Here’s a real example using vitalik.eth – Vitalik Buterin’s public Ethereum address, one of the most analyzed wallets on-chain.

Step 1 – Connect your wallet. The Fraud Detector is free but requires wallet connection for access. This is a one-time step per session.

Step 2 – Enter the address and select the network. Paste the wallet address or ENS name (e.g. vitalik.eth) and select Ethereum.

Step 3 – View the result. The screenshot below shows the live ChainAware analysis of vitalik.eth. You can run the same check yourself at chainaware.ai/fraud-detector/eth/vitalik.eth.

The result for vitalik.eth illustrates the algorithm at work: a wallet with years of legitimate, high-volume, multi-protocol interaction produces a very low fraud score. The behavioral fingerprint – diverse protocol usage, long wallet age, consistent interaction patterns, no suspicious counterparty clusters – is the opposite of what fraudulent addresses typically show.

Step 4 – Request a real-time recalculation (optional). You can request a fresh recalculation at any time. For addresses with extensive transaction histories like vitalik.eth, this takes approximately 3-4 seconds as the algorithm reads the full current blockchain history and runs the predictive model in real time.

Step 5 – Interpret the result. A score close to 0 indicates low predicted fraud risk. A score close to 1 indicates high predicted fraud risk. Use the score as one input in your risk assessment alongside other available data.

Limitations: When the Fraud Detector Does Not Apply

The Fraud Detector is a powerful tool, but it has specific use conditions that are important to understand.

Contract Addresses

The ChainAware Fraud Detector works exclusively on regular wallet addresses (externally owned accounts / EOAs). It does not work on smart contract addresses. If you need to assess the risk of a smart contract or liquidity pool, use the ChainAware Rug Pull Detector instead.

New Addresses with Fewer Than 10-15 Transactions

The predictive AI model requires a minimum transaction history to generate a reliable score. Addresses with fewer than 10-15 transactions do not have sufficient behavioral data for the model to identify meaningful patterns. Treat new low-activity addresses with appropriate caution by default.

Already-Flagged Forensic Addresses

If an address has already been flagged in forensic databases as a confirmed fraud address, the Fraud Detector will surface this forensic flag. At this point, the predictive value is moot – the address is already a known bad actor. The tool is most valuable for addresses that have not yet been forensically flagged – the vast majority of potentially dangerous addresses – where the predictive AI’s forward-looking analysis provides actionable risk intelligence that no forensic database can.

Contract Addresses: Use the Rug Pull Detector

While the Fraud Detector covers wallet addresses, ChainAware’s Predictive Rug Pull Detector covers smart contract addresses – specifically liquidity pools, DeFi protocol contracts, and token contracts that may be designed to execute a rug pull.

A rug pull occurs when the developers of a DeFi project withdraw all liquidity or exploit a contract backdoor to drain user funds – typically after attracting significant investment through promotion and artificial price appreciation. According to Immunefi’s Web3 security research, rug pulls and exit scams account for a significant share of total crypto losses annually – making pre-investment contract screening one of the highest-ROI security practices available.

The Rug Pull Detector analyzes contract-level behavioral patterns – ownership concentration, liquidity lock status, contract upgrade mechanisms, wallet interaction patterns around the contract – to predict the probability of a rug pull before it occurs.

Use case guidance: checking a wallet address before sending payment → Fraud Detector. Checking a smart contract / liquidity pool before investing → Rug Pull Detector. Full behavioral audit of a wallet → Wallet Auditor. For more on rug pulls vs other fraud types, see our guide on Pump and Dump vs Rug Pull.

Supported Networks

The ChainAware Fraud Detector currently supports eight blockchain networks covering the vast majority of active on-chain transaction volume: Ethereum (ETH) – approximately 50% of all transactions are stablecoin payments, making fraud detection here particularly high-value; Binance Smart Chain (BNB) – high-volume, low-cost transactions with a large retail user base; Base – Coinbase’s L2 network, growing rapidly for DeFi and payments; Polygon (POL) – widely used for gaming, NFTs, and DeFi; Haqq – Islamic finance-aligned blockchain; Solana (SOL) – high-throughput network with significant payment and DeFi activity; TON – Telegram’s blockchain with rapidly growing payment activity; and Tron (TRX) – one of the largest stablecoin transfer networks by volume, particularly for USDT.

Where Fraud Detector Fits in the ChainAware Ecosystem

The Fraud Detector is one component of ChainAware’s broader Predictive Intelligence Stack. The Wallet Auditor is the most comprehensive single-wallet intelligence tool – it includes Predicted Trust (= 1 minus Fraud Score) alongside AML status, experience level, risk willingness, behavioral intentions, and Wallet Rank. The full AML and Transaction Monitoring suite combines forensic fund-flow tracing with predictive behavioral scoring into a continuous monitoring layer. The Rug Pull Detector is the contract-address counterpart to the wallet-focused Fraud Detector.

For Dapp teams, the fraud intelligence also powers the conversion tools: Web3 Behavioral Analytics uses aggregate fraud scores as one of its 10 dashboard dimensions, and the Prediction MCP allows AI agents to query fraud scores programmatically in real time. For the complete product overview, see the ChainAware complete product guide.

Real-World Use Cases

1. Payment Sender: Verifying a New Counterparty

You’re about to send USDT to an address you’ve never transacted with before – a new supplier, service provider, or trading counterparty. Before confirming, run the address through the Fraud Detector. A high score (close to 1) is a strong signal to pause and ask more questions. Given that the tool is free and takes seconds, this is one of the highest-ROI security checks available in crypto.

2. Exchange / Protocol: Screening Depositing Wallets

Exchanges, lending protocols, and payment processors face significant exposure to fraudulent wallets that deposit funds, exploit services, and withdraw before detection. Integrating the Fraud Detector API into deposit workflows provides a real-time risk signal on every depositing wallet. For automated integration, see the Prediction MCP developer guide.

3. DeFi Investor: Assessing Liquidity Partners

In DeFi liquidity pools, co-investors matter. A pool with a significant share of high-fraud-risk liquidity providers is a potential target for coordinated exit attacks. Checking the fraud scores of major LPs before committing capital provides meaningful intelligence about pool composition and counterparty risk.

4. NFT Buyer: Verifying Seller Addresses

NFT marketplace fraud – wash trading, counterfeit collections, fraudulent royalty manipulation – often involves addresses with recognizable behavioral patterns. Running a fraud check on a seller address before a significant purchase provides a fast, objective risk signal.

5. Airdrop Campaign: Filtering Farmers

Airdrop farming – where bad actors create multiple wallets to claim incentive distributions – is one of the most common fraud patterns in Web3. Fraud scores provide one filtering dimension: wallets with high fraud scores should be excluded from incentive eligibility. For the full framework, see our guide on using Wallet Rank to identify low-quality wallets.

Frequently Asked Questions

Is the Fraud Detector really free?

Yes – the ChainAware Fraud Detector is free to use. You need to connect your wallet for access, but there is no subscription, no credit card, and no fee per lookup. The Rug Pull Detector is also free.

How accurate is the fraud score?

The current predictive accuracy of the AI model is 98% – meaning it correctly identifies 98 out of every 100 fraud cases in testing. No model is 100% accurate; use the fraud score as a strong probabilistic signal rather than a definitive verdict.

Can I use the Fraud Detector on a contract address?

No. The Fraud Detector works exclusively on regular wallet addresses (EOAs). For smart contract addresses, use the Rug Pull Detector.

What happens if an address has very few transactions?

Addresses with fewer than 10-15 transactions do not have sufficient behavioral history for the model to generate a reliable score. New addresses should be treated with appropriate caution by default.

How is this different from checking an address on Etherscan?

Etherscan is a block explorer – it shows transaction history but has no predictive capability and no AI-powered behavioral analysis. The ChainAware Fraud Detector adds a predictive risk score on top of the raw transaction history – the analysis layer that Etherscan doesn’t provide.

How is the Fraud Score related to Predicted Trust in the Wallet Auditor?

Predicted Trust = 1 − Predicted Fraud Score. A wallet with a Fraud Score of 0.15 has a Predicted Trust of 0.85 (85%). The Wallet Auditor displays both alongside the full behavioral profile, AML status, experience level, and Wallet Rank.

Can I integrate the Fraud Detector into my platform?

Yes – ChainAware exposes the full Predictive Data Layer via API and MCP. The Prediction MCP allows AI agents and developers to query fraud scores programmatically in real time.

The post ChainAware Fraud Detector: The Complete Guide to Predictive Crypto Fraud Detection first appeared on ChainAware.ai.

Last Updated: February 2026

In traditional business, a business card tells people who you are. It shows your name, your title, your company, your contact details. It is a compressed credential – a starting point for trust. When you hand someone a business card, you are saying: here is verifiable proof that I am who I say I am.

In Web3, wallets are pseudonymous. Anyone can create a wallet address, give themselves any name, and present any credentials. There is no central authority verifying who anyone is. This creates a fundamental trust problem that affects every Web3 interaction: how do you know the KOL promoting a token has genuine DeFi experience? How do you know the business partner proposing a deal has a legitimate track record? How do you know the contractor you are hiring has the on-chain credentials they claim?

The answer is already on the blockchain. Every wallet address carries a complete, immutable, publicly verifiable record of every on-chain decision its owner has ever made – every protocol interacted with, every risk taken, every loan repaid or defaulted, every liquidity position managed. This history cannot be faked, cannot be deleted, and cannot be misrepresented. It is the most reliable credential in Web3.

ChainAware’s Share My Audit turns this history into a shareable trust passport. Connect your wallet at chainaware.ai/audit/my, receive a unique link associated with your wallet address, and share it with any counterparty as verifiable proof of your Web3 identity, experience, and trustworthiness. One link. Complete transparency. No lies possible.

The Trust Problem in Web3

Trust is the foundational resource in any economic system. In traditional finance, trust is built through institutional intermediaries – banks verify identities, credit bureaus track payment histories, professional licensing boards certify credentials, and contracts are enforced by legal systems. These systems are slow, expensive, and centralized – but they work because they provide verifiable claims about who someone is and how they have behaved.

Web3 eliminates the intermediaries. This is its greatest innovation and its most significant challenge simultaneously. Without banks, there is no central identity verification. Without credit bureaus, there is no standardized credibility scoring. Without licensing boards, there are no verified professional credentials. The result is a system where anyone can claim anything and the social cost of being wrong is low.

The consequences are visible everywhere in Web3. KOLs promote tokens they have never researched to audiences who trust their apparent expertise. Business partners claim development experience they don’t have. Contractors present GitHub profiles that don’t represent real work. Lenders have no way to assess borrower credibility without requiring overcollateralization so extreme it defeats the purpose of borrowing.

According to FTC research on crypto fraud, trust-based scams – where the fraud depends on the victim trusting the identity or credentials of the scammer – are the dominant category of crypto losses. The solution is not more trust; it is verifiable transparency. And verifiable transparency is exactly what on-chain transaction history provides.

The blockchain solves the trust problem in a way no intermediary can: it makes behavior permanently visible. You don’t need to trust what someone says about their DeFi experience – you can see their exact protocol interactions, loan history, trading behavior, and risk management decisions on-chain. You don’t need to trust their claimed Wallet Rank – you can verify it against 14 million+ profiled wallets. You don’t need to trust their word that they are a legitimate actor – you can check their fraud probability score with AI accuracy of 98%.

Share My Audit makes this verification frictionless. Instead of requiring every counterparty to know how to read blockchain data, it packages the complete analysis into a single shareable link that anyone can read in seconds.

The Wallet Audit: What Your On-Chain History Reveals

Before understanding Share My Audit, it helps to understand what the underlying Wallet Auditor actually measures. The Auditor takes any wallet address across 8 supported blockchains and applies ChainAware’s AI behavioral analysis – trained on 14 million+ wallet profiles – to generate a comprehensive behavioral and risk assessment.

The result is not a simple score. It is a multi-dimensional behavioral profile that captures who this wallet’s owner actually is based on what they have actually done with real capital on-chain. No self-reporting. No claimed credentials. Only demonstrated behavior.

Experience Level measures how sophisticated and active the wallet’s DeFi engagement has been – the breadth of protocols used, the complexity of strategies executed, the duration of active participation. A wallet that has interacted with 20+ protocols across multiple chains over 3 years is categorically different from a wallet created last month with 5 transactions.

Risk Willingness captures the wallet’s demonstrated risk appetite from its actual financial decisions – not what the owner says about their risk tolerance, but what they have actually done. High leverage use, volatile yield farming, aggressive small-cap trading, and complex multi-step DeFi strategies all indicate high risk willingness.

Predicted Intentions use behavioral AI to forecast what the wallet is likely to do next: probability of borrowing, staking, trading, bridging, or providing liquidity. For potential partners evaluating alignment, this signals whether the wallet owner is currently in accumulation mode, yield-seeking mode, or active trading mode.

Wallet Rank is the composite quality score that places the wallet among all 14M+ profiled wallets globally. A Wallet Rank in the top 5% identifies a verified power user of Web3 – someone whose on-chain activity places them among the most active and sophisticated participants in the ecosystem.

Protocols Used and Transaction Categories show the specific DeFi protocols, DEXs, NFT platforms, and blockchain bridges the wallet has interacted with – giving a counterparty a detailed picture of where the wallet owner actually operates in Web3. Someone claiming to be a DeFi expert whose wallet shows no Aave, Uniswap, or Compound interactions is immediately exposed.

Fraud Probability and AML Status complete the picture: what is the AI-assessed probability that this wallet has or will commit fraud, and have its funds passed through sanctioned or criminal addresses? As covered in our Fraud Detector complete guide, the fraud probability score operates at 98% AI accuracy across 8 networks.

Share My Audit: How It Works

Share My Audit is built on a simple but powerful insight: proving that you own a wallet is easy (connect it to a dApp), but packaging the resulting audit into a form that anyone can verify has historically been cumbersome. Share My Audit removes that friction entirely.

The process has three steps. First, go to chainaware.ai/audit/my and connect your Web3 wallet (MetaMask, WalletConnect, or any supported wallet). The connection proves you are the owner of that wallet address – without revealing your private keys, without any KYC, and without any registration. Second, ChainAware runs the full Wallet Auditor analysis on your connected wallet, generating your complete behavioral profile across all tracked on-chain activity. Third, you receive a unique shareable link permanently associated with your wallet address.

The link is wallet-bound. Because it was generated through a wallet connection that proves ownership, anyone viewing the link knows they are seeing the verified profile of the wallet’s actual owner – not a profile someone claimed to have, but one they demonstrably own. This is the verification layer that transforms a Wallet Audit from an analytical output into a trust credential.

The profile is live – it updates as your on-chain activity evolves. This means your Share My Audit link always reflects your current behavioral status, not a static snapshot. As you build more experience, your Experience Level improves. As you maintain clean behavior, your Fraud Score stays low. The link is always current.

What Your Audit Shows: The Complete Profile

When a counterparty opens your Share My Audit link, they see your complete Wallet Auditor profile – the same analysis available to any Wallet Auditor user, but with the critical addition that this profile is verified as belonging to the person sharing it. The profile includes your Experience Level and Wallet Rank – where you sit among 14M+ profiled wallets globally. Your Risk Willingness – the demonstrated risk profile from your actual financial decisions. Your Predicted Intentions – what behavioral AI assesses you are likely to do next. The Protocols and Categories you have interacted with – a complete map of your Web3 activity. Your Fraud Probability Score and AML Status. And the Networks covered: Ethereum, BNB Chain, Base, Polygon, Solana, TON, Tron, and Haqq.

The counterparty reading this profile gets an immediate, objective assessment of who they are dealing with – with no possibility of the data being fabricated. Unlike a LinkedIn profile or a CV, a Wallet Audit cannot be inflated with false experience or misleading credentials. Either the on-chain activity is there, or it isn’t.

As explained in the broader context of our Web3 behavioral segmentation guide, on-chain data is the highest-quality behavioral signal in Web3 precisely because it represents actual decisions made with actual capital – not declared preferences or self-reported credentials.

10 Real Use Cases: When to Ask for Share My Audit

The Share My Audit link is most powerful as a standard expectation in Web3 business interactions. Here are ten specific situations where asking for – or sharing – a Wallet Audit link creates genuine value.

1. Evaluating a KOL or Influencer. A KOL approaches your project offering promotion to their 200,000 Twitter followers. Before engaging, ask: “Can you share your Wallet Audit?” A genuine DeFi KOL with real expertise will have an on-chain history that reflects years of active protocol engagement. A fake KOL or paid shill may have a wallet with no genuine DeFi activity – or worse, a wallet linked to pump-and-dump operations. See our analysis of why KOL marketing in Web3 underperforms for the broader context.

2. New business partnership. A company proposes a joint venture, liquidity partnership, or protocol integration. In Web3, the equivalent of financial due diligence is the Wallet Audit: verify the proposing team’s on-chain track record, assess their experience level and risk profile, and check their fraud probability before committing to any financial relationship.

3. Hiring a crypto-native contractor or developer. A developer claims 5 years of DeFi protocol experience. Their Share My Audit link will confirm or refute this: do they have years of active on-chain engagement across relevant protocols? On-chain credentials cannot be falsified.

4. Evaluating a marketing candidate. You are hiring a Web3 marketing manager who claims expertise in DeFi user acquisition. Ask for their Share My Audit. A marketer who genuinely understands DeFi from the user perspective will have a wallet that reflects real DeFi participation – not just familiarity with the language.

5. DeFi lending and borrowing counterparty. For undercollateralized lending protocols, the borrower’s creditworthiness is the key risk variable. A borrower who shares their Wallet Audit demonstrates their complete financial behavior history: loan repayment track record, risk management approach, and cash flow patterns. This is what the ChainAware Credit Score formalizes – Share My Audit is the human-readable version of the same underlying data.

6. NFT deal or high-value P2P transaction. You are buying or selling a high-value NFT through direct negotiation. The counterparty claims to be a serious collector. Their Share My Audit – showing NFT transaction history, wallet quality, and fraud probability score – tells you whether you are dealing with a legitimate collector or a potential scammer.

7. DAO contributor or governance participant verification. A DAO is considering giving significant governance weight or funding to a contributor who claims expertise in DeFi protocol design. Share My Audit verifies their actual on-chain engagement with the types of protocols they claim expertise in.

8. Investment syndicate or group participation. You are joining or forming a crypto investment group where members pool resources or share alpha. Requiring Share My Audit from all participants establishes a baseline of verified experience and risk profile alignment – and flags any member whose wallet shows fraud risk signals.

9. Vendor or service provider assessment. A crypto-native service provider – a trading desk, an OTC broker, a yield management service – claims institutional-grade experience. Their Wallet Audit reveals the actual on-chain behavior behind the claim.

10. Personal trust-building in the Web3 community. If you are building a reputation in Web3 – as a developer, researcher, trader, or community leader – sharing your Wallet Audit proactively is a powerful credibility signal. It says: I have nothing to hide. My on-chain behavior speaks for itself.

KOL Vetting: Why Share My Audit Matters for Influencer Marketing

KOL vetting deserves its own section because it is one of the highest-value and most widely applicable use cases for Share My Audit – and because the cost of trusting the wrong KOL in Web3 is enormous.

The Web3 influencer ecosystem is heavily populated with accounts that have large followings but no genuine DeFi expertise. Some promote tokens they have never researched in exchange for payment, without disclosure. Some are coordinated networks of accounts that amplify each other’s content to create artificial social proof. Some are outright scam operations that build followings specifically to exploit them in pump-and-dump schemes.

Identifying genuine KOLs from fake ones is notoriously difficult using social metrics alone – follower counts can be purchased, engagement can be bot-generated, and the language of DeFi expertise can be convincingly mimicked by anyone who reads the right blogs. What cannot be mimicked is on-chain history.

A genuine DeFi KOL who has spent years in the space will have a wallet that reflects it: multiple DeFi protocols used over an extended period, a Wallet Rank in the upper percentiles of the 14M+ profile database, an Experience Level consistent with their claimed tenure, and a fraud probability score that confirms they are not connected to known scam operations. When you ask a KOL to share their Wallet Audit link and they can produce one with genuine credentials, you can engage with confidence.

According to McKinsey research on marketing ROI, influencer marketing campaigns with verified audience quality significantly outperform campaigns based purely on follower count metrics. In Web3, Share My Audit is the verification tool that makes quality-first KOL selection operationally possible.

The Fraud Detector: The Other Side of Trust Verification

Share My Audit is the tool you use to share your own credentials. The Fraud Detector is the tool you use to verify the credentials of anyone sharing with you.

Even when a counterparty shares their Wallet Audit voluntarily, running their address through the Fraud Detector adds a critical layer: behavioral AI analysis that detects fraud patterns the surface-level Wallet Audit profile might not immediately surface. The Fraud Detector is trained on confirmed fraud cases across 14M+ wallet profiles and predicts fraud probability based on behavioral signals – not just whether the wallet has been previously flagged, but whether its behavioral patterns match known fraud typologies.

The combination of Share My Audit and Fraud Detector covers both directions of trust verification: the counterparty voluntarily shares their credentials (Share My Audit), and you independently verify those credentials against behavioral AI analysis (Fraud Detector). This is the complete due diligence stack for any significant Web3 interaction.

For the complete picture of how fraud detection, AML screening, and transaction monitoring work together as a compliance and trust stack, see our guide on Crypto AML vs Transaction Monitoring. For context on how trust score metrics work across the ChainAware product suite, see our Crypto Trust Score guide.

Web3 Business Card vs Traditional Business Card

The business card analogy is useful but understates how much better the Share My Audit profile is as a trust credential compared to its traditional equivalent.

A traditional business card contains: your name, title, company, email, phone number, and sometimes a LinkedIn URL. All of this information is self-reported. There is no verification of any claim on a business card – anyone can print any title they want. The business card creates a starting point for investigation, not a verification of claims.

A Share My Audit link contains: your verified wallet address (proven through wallet connection), your Experience Level calculated from actual on-chain activity, your Risk Willingness derived from actual financial decisions, your Wallet Rank among 14M+ real wallets, your Fraud Probability score from AI behavioral analysis, your AML Status from fund origin screening, the specific protocols you have genuinely interacted with, and your transaction category history. None of this information is self-reported. All of it is derived from verifiable on-chain data that cannot be altered.

According to Harvard Business Review research on trust in business relationships, verified credentials create faster relationship formation and lower transaction costs. In Web3, where pseudonymity creates friction in every new relationship, a Share My Audit link achieves exactly this: it collapses the verification process that would otherwise take hours of independent research into a 30-second link review.

The Share My Audit link is also persistent and updatable. A traditional business card becomes stale when you change roles or companies. Your Share My Audit link always reflects your current on-chain status – because it is generated live from your evolving blockchain history. As your experience grows, your profile improves. As you maintain clean behavior, your fraud score stays low. The credential grows with you.

As the ChainAware complete product guide explains, the Wallet Auditor and Share My Audit are part of a comprehensive Web3 intelligence suite – tools that together make trust verifiable, fraud detectable, and user behavior predictable in a way that no traditional credential system can match. According to Deloitte research on trust and customer experience, businesses that successfully signal trustworthiness see significantly higher engagement and conversion rates. In Web3, Share My Audit is that trust signal.

Frequently Asked Questions

What is Share My Audit?

Share My Audit is a ChainAware feature that allows wallet owners to generate a unique shareable link at chainaware.ai/audit/my by connecting their wallet. The link is permanently associated with the connected wallet and displays the wallet’s complete Auditor profile — Experience Level, Risk Willingness, Predicted Intentions, Wallet Rank, Fraud Probability, AML Status, and Protocols Used. Because the link is generated through a verified wallet connection, anyone viewing it knows the profile belongs to the person sharing it.

How is Share My Audit different from a regular Wallet Audit?

A regular Wallet Audit allows anyone to analyze any wallet address — but the analysis alone doesn’t prove that the person sharing it actually owns the wallet. Share My Audit adds wallet ownership verification through the wallet connection process. This turns the audit from an analytical output into a verified credential: the viewer knows they are seeing the profile of the wallet’s actual owner, not a profile someone is borrowing or fabricating.

Is it safe to share my Wallet Audit?

Yes. The Wallet Audit only reveals information that is already publicly visible on the blockchain — your transaction history, protocol interactions, and behavioral patterns are public data by the nature of blockchain technology. Sharing your audit does not reveal your private keys, your identity, or any non-public information. The wallet connection to generate your link is read-only and does not grant ChainAware or any viewer any access to your funds.

What blockchains are covered?

Ethereum, BNB Chain, Base, Polygon, Solana, TON, Tron, and Haqq — covering the major networks where DeFi activity and on-chain credentials are most meaningful.

Can someone fake a Share My Audit link?

No. The Share My Audit link is generated by connecting a wallet — which cryptographically proves ownership. Someone cannot generate a Share My Audit link for a wallet they do not own, because the connection process requires a cryptographic signature from the wallet’s private key.

How does Share My Audit help with KOL vetting?

When a KOL shares their Wallet Audit link, you can immediately verify whether their claimed DeFi expertise is reflected in their on-chain history. A genuine DeFi KOL will have years of active protocol engagement, a high Wallet Rank, and a low fraud probability. A paid promoter with no genuine expertise will have minimal on-chain DeFi activity inconsistent with their claimed knowledge.

How is this related to the ChainAware Credit Score?

The ChainAware Credit Score uses the same underlying Wallet Auditor data to generate a formal creditworthiness score (0-1000) for DeFi lending decisions. Share My Audit is the human-readable, relationship-focused version of the same underlying data — designed for trust-building across all Web3 interactions, not just lending.

The post ChainAware Share My Audit: Your Web3 Business Card and Trust Passport first appeared on ChainAware.ai.