A $3-5 trillion market is forming around one unsolved problem: how do you know whether to trust an AI agent before it touches your funds? Six distinct approaches have emerged in 2026 to answer that question. They carry similar names – trust scores, reputation scores, behavioral scores – but they answer fundamentally different questions, protect against different threat models, and leave very different blind spots.

Choosing the wrong approach does not mean you get a slightly worse score. It means the specific fraud pattern you face is exactly the one your chosen platform cannot detect. An operator running a Sybil farm of 50 agents will not be caught by a review-quality platform scoring each agent individually. A serial rug puller launching agents under a fresh wallet will not be caught by a platform that scores wallet age but ignores creation history. Understanding which approach catches which threat is the most important infrastructure decision in agentic commerce right now.

This guide maps every significant agent trust platform in 2026 – their methodology, their real strengths, their genuine blind spots, and the specific signals that separate them. It is written for three audiences: DeFi protocol builders integrating agents and choosing a trust gating system, agent creators who want to understand how their agents get scored across platforms, and investors evaluating the agent trust infrastructure market as a sector.

Table of Contents

1. Why the Approach Matters More Than the Score
2. The Four Questions Agent Trust Platforms Answer
3. Platform 1 – ERC-8004 Native Reputation Registry
4. Platform 2 – RNWY: Review Quality and Sybil Detection
5. Platform 3 – SkyeProfile: Multi-Attestation Wallet Trust
6. Platform 4 – AXIS T-Score: Runtime Performance Scoring
7. Platform 5 – DJD Agent Score: Wallet Activity Scoring
8. Platform 6 – ChainAware: Behavioral Fraud Intelligence
9. The Five Signals Only One Platform Provides
10. Head-to-Head Comparison Table
11. Decision Matrix: Which Platform for Which Use Case?
12. The White Space: Five Capabilities Nobody Has Built Yet
13. The Investor Lens: What Makes Agent Trust Infrastructure a Durable Market
14. Frequently Asked Questions

Why the Approach Matters More Than the Score

Every agent trust platform in 2026 returns a number. The number is not the product – the threat model behind it is. Two platforms can both return a score of 72 for the same agent and disagree completely about what that score means, because they measured entirely different things to compute it.

RNWY’s score of 72 tells you: the agent’s peer reviews show limited sybil activity and the reviewer wallets are moderately established. ChainAware’s score of 72 tells you something different: the owner wallet has a moderate fraud probability, the feeder address is unknown, and no criminal record signals are present. SkyeProfile’s assessment tells you something different again: the wallet passes certain solvency and governance checks but shows limited behavioral depth across attestation providers.

Each score is internally consistent. However, each one answers a different question about the same agent. Consequently, the correct question for any DeFi protocol builder, agent creator, or investor is not “which platform gives the highest scores?” It is “which platform’s threat model matches the risk I am actually trying to prevent?”

For context on how this same problem appears at the wallet intelligence layer, see our complete guide to Web3 Wallet Auditing Providers in 2026 – the same principle applies there, where raw data providers, descriptive profilers, and predictive intelligence systems each answer fundamentally different questions about the same wallet address.

The Four Questions Agent Trust Platforms Answer

Before comparing platforms, mapping the question each approach addresses clarifies the landscape considerably. Every platform in the 2026 agent trust market falls into one of four categories based on what it actually measures.

Question 1: Have other agents endorsed this agent?

This is the peer review / reputation registry approach. The ERC-8004 native system operates here. Additionally, RNWY’s core methodology operates here – with the significant enhancement of reviewing the quality of the reviewers rather than simply counting the reviews. The fundamental limitation of this approach is that endorsement and trustworthiness are not the same thing. Any operator who controls multiple agents can engineer endorsements between them at near-zero cost.

Question 2: Has this agent performed tasks well?

This is the runtime performance approach. AXIS T-Score operates exclusively in this category, measuring 11 behavioral dimensions of agent task execution – completion rate, instruction adherence, error recovery, security posture, and similar metrics. The limitation here is that runtime performance and financial trustworthiness are orthogonal. An agent that executes tasks reliably can still be controlled by a fraud operator using it as a front for financial extraction.

Question 3: What does the agent’s wallet history look like?

This is the wallet activity approach. DJD Agent Score operates here, scoring seven wallet dimensions including transaction history, partner diversity, and account age. SkyeProfile’s solvency layer also operates here. The limitation is that wallet history describes the agent wallet itself – which is frequently a fresh address created specifically for the agent, with minimal history by design. A fresh agent wallet with no history is not the same as a fraudulent one, but wallet-only scoring treats them identically.

Question 4: Who controls this agent, and what have they done on-chain?

This is the behavioral fraud intelligence approach. ChainAware operates here – scoring the owner wallet that controls the agent, the feeder address that funded the owner, and cross-referencing both against a database of confirmed rug pulls and honeypot token creations. The threat model this addresses is the one that matters most for autonomous financial execution: a sophisticated fraud operator registering a new agent identity to continue activities previously conducted under different wallet identities.

Each of these four approaches is internally valid. Furthermore, they are not mutually exclusive – DeFi protocols can layer multiple approaches. However, understanding which question each one answers is essential before choosing which to gate on.

Platform 1 – ERC-8004 Native Reputation Registry

What it is

The ERC-8004 standard includes a built-in Reputation Registry as an optional component of the agent identity specification. The registry provides a standard interface for posting and fetching feedback signals. Critically, the standard explicitly does not define a scoring algorithm – aggregation and scoring are intentionally delegated to third parties. The protocol is infrastructure. Every other platform in this comparison is a third-party scoring layer on top of it.

Methodology

Any wallet can submit a feedback signal to the Reputation Registry for any registered agent. The signal includes a rating and optional metadata. The registry stores it on-chain. Reading platforms aggregate these signals according to their own methodology – which means the “ERC-8004 reputation score” is not a single consistent number but rather different outputs from different aggregation strategies across different platforms reading the same underlying data.

Strengths

The registry is permissionless, transparent, and composable. Any smart contract can read it. Furthermore, on-chain storage means the feedback history is permanent and verifiable. For building a decentralised reputation system in principle, the architecture is sound.

Blind spots

The fundamental blind spot is that the registry cannot distinguish manufactured reviews from genuine ones without an external intelligence layer on top. An operator controlling 50 agents can give each one a 5-star review from the other 49 at a cost of a few dollars in gas. Additionally, the native registry provides no information about who controls the agent, no feeder analysis, no fraud prediction, and no criminal record check. It answers only “what have other agents said about this agent?” – which is the weakest possible trust signal in a system where agents can be created and coordinated freely.

Who it is for

The native registry is appropriate as an additional data layer for platforms that have already implemented stronger trust signals. It should not serve as a primary trust gate for any DeFi protocol permitting autonomous financial execution.

Platform 2 – RNWY: Review Quality and Sybil Detection

What it is

RNWY (rnwy.com) is the most established third-party agent trust platform operating on ERC-8004 in 2026. RNWY positions itself as the trust layer for an economy where participants might not be human, with 185K+ agents scored and every score showing its math – the same door for humans and AI alike. The platform is notable for its transparency: all scoring methodology is published, including exact signal weights.

Methodology

RNWY’s trust score uses six input signals combined with additive modifier stacking, logarithmic value scaling, buffer zones, and evaluator softening to produce a score out of 95 across five tiers. The six signals weight toward reviewer quality rather than raw review count.

RNWY’s sybil detection applies four signals with explicit weights: common funder (6×), inhuman velocity (5×), sweep pattern (3×), and score clustering (1×). The weighted score produces severity levels: Low (0-2), Moderate (3-9), Elevated (10-19), and Heavy (20+). This makes RNWY’s sybil detection notably rigorous – it specifically targets the coordinated-review attack that would compromise naive review counting.

Since v1.1.0 (April 2026), RNWY also returns an owner wallet score, commerce summary (provider jobs, counterparty count, commerce tenure), and transaction-backed review percentage in the API response. However, these are additional intelligence fields – they appear in the response but do not affect the tier calculation or the primary trust score. This is the critical distinction from ChainAware: RNWY surfaces the owner wallet score as informational context; it does not integrate it into the scoring formula.

RNWY also indexes 1.7 million commerce jobs across Olas, Virtuals ACP, and SATI – making it the most comprehensive commerce activity tracker in the agent ecosystem. Trust scores live on Base mainnet, meaning any smart contract can read an agent’s score, tier, and sybil severity mid-transaction without an API call or oracle fee. This on-chain accessibility is a significant technical advantage for DeFi protocols that want to gate at the smart contract level rather than the application layer.

Strengths

RNWY’s strengths are transparency, on-chain accessibility, and commerce job history depth. The published methodology with exact signal weights means any relying party can independently verify a score calculation. The on-chain trust oracle on Base enables smart contract-level gating. The 1.7M commerce job index provides genuine economic activity context that no other platform matches. Additionally, the sybil detection is genuinely sophisticated – the common funder signal (weighted 6×) specifically targets the attack pattern of one operator funding multiple reviewer wallets from a single source.

Blind spots

RNWY’s primary blind spot is the boundary it draws at the review layer. The owner wallet score is surfaced but does not affect the tier. Feeder address analysis does not exist. Prior token creation history – rug pulls, honeypots – is not queried. Farm detection operates only at the reviewer level, not at the fleet level. Consequently, a fresh wallet that has never received a review (no positive signals, no negative signals) scores the same as an established operator in RNWY’s primary score calculation – both lack review history. Furthermore, a serial rug puller who has never participated in the ERC-8004 review ecosystem will not trigger any RNWY detection signal, because their fraud history exists in token creation, not in agent reviews.

Who it is for

RNWY is the strongest choice for platforms where agent reputation is displayed to users (marketplaces, directories, leaderboards) and where the primary threat model is manufactured peer endorsements. It is a compelling addition to any trust stack as a review quality layer. However, it is not sufficient as a standalone gate for DeFi protocols where the primary threat is a fraud operator using agents as the execution vehicle for financial crimes.

Platform 3 – SkyeProfile: Multi-Attestation Wallet Trust

What it is

SkyeProfile (skyemeta.com) is a multi-attestation wallet trust profile that orchestrates nine specialised attestation providers and returns one unified signed profile per wallet. The system uses a dual-score model with Signal Depth (behavioral observability) and Risk Intensity (sybil and fraud risk) as independent axes, covering 150K+ agents across ERC-8004, Olas, Virtuals, and SATI registries.

Methodology

SkyeProfile works on a general contractor model – eight dimensions, eight independent providers, eight verifiable signatures. One API call returns ten independently verifiable attestations, each with a JWKS URI so relying parties can verify any dimension offline without trusting SkyeMeta itself. The dimensions span solvency (wallet holdings across 33 chains), governance participation, behavioral trust, identity, security posture, compliance, performance, and settlement track record.

Notably, SkyeProfile uses RNWY as its behavioral trust provider – RNWY maintains the dual-score model across 150K+ agents spanning twelve EVM chains and Solana within the SkyeProfile attestation framework. This means SkyeProfile inherits RNWY’s methodology for the behavioral dimension, including both RNWY’s strengths (sybil detection, review quality analysis) and RNWY’s blind spots (no feeder analysis, no criminal record check, owner wallet informational only).

Strengths

SkyeProfile’s primary strength is breadth and verifiability. By aggregating nine specialised providers and returning independently verifiable signatures, it gives relying parties a comprehensive wallet profile that no single provider can match across all dimensions. The cryptographic verifiability (ES256 or EdDSA signatures with JWKS-published keys) is technically rigorous and appropriate for high-stakes autonomous execution contexts. The 33-chain solvency layer is the most comprehensive wallet holdings analysis in the market.

Blind spots

SkyeProfile scores the agent wallet – the address registered with the ERC-8004 identity. Since it delegates behavioral trust to RNWY, it inherits RNWY’s blind spots on feeder analysis and criminal record checking. Furthermore, because SkyeProfile is built as a wallet profiling system rather than an agent-specific fraud intelligence system, it does not perform fleet-level farm detection or trust delegation from owner to agent wallet. The platform also scores 150K agents across multiple registries – which is valuable breadth, but means its ERC-8004 specific coverage is thinner than RNWY’s 185K ERC-8004-specific indexed agents.

Who it is for

SkyeProfile is strongest for use cases requiring verifiable, multi-dimensional wallet attestations – particularly in contexts where cryptographic proof of each assessment matters, such as compliance audit trails or high-stakes DeFi credit decisions. For the broader DeFi credit scoring context, see our DeFi Credit Score Platform comparison. SkyeProfile is not a standalone agent trust gate – it is a comprehensive wallet profiling layer that serves agent trust as one of several use cases.

Platform 4 – AXIS T-Score: Runtime Performance Scoring

What it is

AXIS T-Score (axistrust.io) operates in an entirely different category from every other platform in this comparison. While all other platforms score the agent’s identity and on-chain history, AXIS scores the agent’s runtime behavior – how well it performs tasks, follows instructions, and operates within defined guardrails during actual execution.

Methodology

AXIS measures 11 behavioral dimensions: task completion rate, instruction adherence, data handling, transparency, error recovery, consistency, scope compliance, resource efficiency, communication clarity, security posture, and audit trail quality. All of these metrics are off-chain – they measure what the agent does during task execution, not what its controlling wallet has done on-chain. Scores run from 0 to 1,000 across five tiers (T1-T5), using the same 0-1,000 scale as ChainAware’s Agent Trust Score but measuring completely different inputs.

Strengths

AXIS addresses a genuinely different problem: does this agent do what it claims to do? An agent that claims to be a compliance screener but routinely fails to flag sanctioned addresses will score low on AXIS – regardless of how trustworthy its owner wallet is. That quality assurance dimension is valuable and not addressed by any on-chain behavioral platform. For enterprise contexts where agents are deployed for specific task categories, AXIS provides the most rigorous evaluation of task quality available.

Blind spots

AXIS scores runtime performance, not financial trustworthiness. An agent can score T5 on AXIS (top-tier task execution) and be controlled by a serial rug puller who has stolen millions. The two assessments are orthogonal – they address completely different threat models. For DeFi protocols where the primary concern is financial fraud rather than task quality, AXIS provides no relevant signal. Additionally, AXIS is entirely off-chain, which means it has no chain coverage, no wallet analysis, and no on-chain verifiability. Scores cannot be read by smart contracts and cannot be cryptographically verified against on-chain data.

Who it is for

AXIS is most valuable for enterprise deployments where agents perform specific workflow tasks – research, content generation, data analysis – and where task quality rather than financial fraud is the primary concern. Layering AXIS with an on-chain identity trust system (ChainAware for fraud intelligence, RNWY for review quality) produces the most complete agent evaluation stack: you verify both who controls the agent and how well the agent performs.

Platform 5 – DJD Agent Score: Wallet Activity Scoring

What it is

DJD Agent Score is the smallest and most narrowly focused platform in this comparison. It returns a 0-100 behavioral trust score for any wallet, combining seven dimensions – transaction history, partner diversity, volume patterns, account age, balance stability, activity consistency, and USDC usage – with sybil detection and gaming velocity checks. Scores feed directly into the ERC-8004 Reputation Registry as off-chain attestations, and the service is monetised via x402 micropayments in USDC on Base.

Methodology and coverage

DJD scores the agent wallet address across those seven dimensions. The scoring approach is transparent and the seven dimensions are reasonable wallet activity signals. However, coverage is Base-only – the platform does not index agents on Ethereum mainnet, BSC, or Avalanche. Furthermore, like SkyeProfile’s solvency layer and the ERC-8004 native registry, DJD scores the agent wallet rather than the owner wallet. This means it faces the same fresh wallet problem: a newly created agent wallet with no transaction history will score near zero on all seven dimensions regardless of the owner’s reputation.

Strengths and limitations

DJD’s x402 integration is technically interesting – it demonstrates a viable micropayment-based business model for agent trust scoring that does not require API keys or subscription agreements. The seven-dimension wallet scoring is simple, auditable, and directly verifiable. However, the Base-only coverage and agent-wallet focus rather than owner-wallet focus significantly limit DJD’s utility as a primary trust gate. It is best understood as an early-stage product demonstrating one viable approach rather than a production-ready trust infrastructure system.

Platform 6 – ChainAware: Behavioral Fraud Intelligence

What it is

ChainAware’s Agent Trust Score approaches agent trust from the opposite direction of every other platform. Rather than starting from the agent and asking what signals the agent produces (reviews, task performance, wallet history), ChainAware starts from the human behind the agent and asks what that human has done on-chain across their entire history – including activities completely unrelated to the current agent registration.

This inversion is the foundation of every signal that differentiates ChainAware from the rest of the market. For a full technical explanation of the scoring formula, see the Agent Trust Score methodology page.

Core formula

The Agent Trust Score builds on the same Wallet Reputation Score formula used across ChainAware’s products:

ReputationScore = (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability)
Maximum: 1,000

This formula runs separately on the owner wallet and the agent wallet. Furthermore, it runs on the feeder address when traceable. The results are then combined using trust delegation logic, farm detection modifiers, and criminal record hard caps to produce the final Agent Trust Score. The 0-1000 scale is consistent with the Wallet Reputation Score – meaning a protocol that already uses ChainAware’s wallet intelligence can compare agent trust and wallet trust on the same axis without recalibration.

Coverage and infrastructure

ChainAware indexes 240,000+ ERC-8004 agents across Ethereum mainnet, BSC, Base, and Avalanche – the widest chain coverage in the market for a predictive fraud intelligence approach. The underlying wallet persona database covers 20M+ addresses across 8 blockchains, trained on behavioral data accumulated over multiple years. The fraud prediction model achieves 98% accuracy on held-out test data, as documented in our AI-Powered Blockchain Analysis guide. Additionally, scores are available via the Prediction MCP server, meaning any Claude-based DeFi agent can query agent trust scores as a native tool call without custom API integration.

The Five Signals Only One Platform Provides

Five signals in the Agent Trust Score are not replicated by any other platform currently operating in the ERC-8004 agent trust market. Each one addresses a specific threat model that the other approaches structurally cannot reach.

Signal 1: Feeder address analysis

The feeder address is the wallet that funded the agent’s owner wallet. Tracing and scoring it is the single most distinctive capability in the ChainAware Agent Trust Score. No other platform – not RNWY, not SkyeProfile, not DJD – performs feeder analysis.

Why it matters: an experienced fraud operator rotates owner wallets between campaigns. Wallet A runs a rug pull, gets flagged, and is abandoned. Wallet B is freshly created and funded from Wallet A. Wallet B then registers 40 agents on ERC-8004. Every platform that scores only the agent or the agent’s direct owner wallet will see a clean Wallet B with no fraud history. ChainAware traces the funding path and scores Wallet A – the feeder – which carries the fraud record. Wallet B’s agents receive hard-capped scores regardless of how clean Wallet B’s own history appears.

ChainAware covers feeder analysis for approximately 38% of indexed agents – the ones with a traceable single-hop funding source. For agents where the feeder is a verified CEX withdrawal address (Binance, Coinbase, Kraken, OKX), the platform flags this as FEEDER_CEX_VERIFIED – a positive trust signal that implies the owner wallet was funded via a KYC’d exchange withdrawal. For agents where the feeder is unknown or obfuscated, the platform applies a penalty reflecting the information asymmetry.

Signal 2: Criminal record – rug pull history

ChainAware maintains a database built from one year of on-chain liquidity pair history. That database records which wallet addresses created pools that subsequently exhibited rug pull patterns – rapid liquidity removal after price appreciation, following the operational signature documented in our Rug Pull vs Pump and Dump guide.

Before computing the Agent Trust Score, ChainAware cross-references both the owner wallet and the feeder address against this database. A single confirmed rug pull in the owner’s history generates a hard cap on the Agent Trust Score – a ceiling no other signal can override. This is the signal that connects yesterday’s token fraud to today’s agent deployment. An operator who rugged three pools on PancakeSwap in Q4 2025 and registered 40 agents in Q1 2026 is caught by this check. No other agent trust platform makes that connection, because no other platform maintains a paired rug pull database and cross-references it against agent registry data.

Signal 3: Criminal record – honeypot token history

Separately from rug pull detection, ChainAware maintains token audit data identifying honeypot contracts – tokens with embedded code that prevents buyers from selling. The creator wallet for each identified honeypot token is recorded. Cross-referencing agent owner wallets against this database produces a second criminal record dimension: has the agent’s controller previously created trap tokens that extracted funds from retail investors?

Honeypot creation and rug pull creation are related but distinct fraud patterns. Some operators specialise in one or the other; some use both. Having both databases cross-referenced produces a more complete criminal record than either alone. Together with rug pull history, this gives ChainAware the only criminal record check available in the agent trust market. For more on how token auditing produces these signals, see our Token Audit methodology.

Signal 4: Trust delegation

Trust delegation is ChainAware’s mechanism for handling the fresh agent wallet problem without penalising legitimate new agents. Agent payment wallets are frequently created specifically for an agent deployment – they are fresh addresses with no transaction history. A scoring approach that treats wallet age as a primary negative signal would incorrectly assign low trust to every newly deployed agent from a legitimate operator.

ChainAware’s trust delegation sets a floor for the agent wallet’s effective score based on the owner wallet’s Reputation Score. A strong owner (Sovereign tier, 800+) partially transfers credibility to the fresh agent wallet, resulting in a significantly higher Agent Trust Score than the agent wallet alone would produce. A fraud-flagged owner, by contrast, cannot delegate any meaningful trust – the delegation factor collapses to near zero. This means fresh wallets from reputable operators score correctly high, and fresh wallets from fraud operators score correctly low – which is the right outcome for both cases.

Signal 5: Fleet-level farm detection

Every other platform in this comparison scores agents individually. ChainAware maintains an owner profile database – tracking how many agents each owner controls across all indexed chains and whether those agents were registered in the same block (indicating automated bulk registration). This fleet-level view enables detection of agent farms that individual agent scoring cannot surface.

An operator running a farm of 50 agents will have each individual agent score independently on RNWY, SkyeProfile, or DJD. Nothing in those individual scores reveals the coordinated nature of the fleet. ChainAware sees the fleet. Owners controlling anomalously large numbers of agents receive a suppression modifier that applies to every agent in their fleet – including agents that individually might score cleanly. This is the signal that catches the specific agentic commerce attack pattern identified in our Blockchain Data Providers guide: one operator manufacturing ecosystem depth through controlled agent populations.

Head-to-Head Comparison Table

The following table compares all six approaches across every dimension relevant to DeFi protocol builders and investors evaluating the space. Each row describes a specific capability, not a general category, to make the comparison as concrete as possible.

Decision Matrix: Which Platform for Which Use Case?

No single platform is the correct choice for every context. The right stack depends on what you are trying to prevent, what signals matter for your specific use case, and what integration constraints you are working within. The following matrix maps use cases to recommended platform combinations.

DeFi protocol gating autonomous financial execution

Primary: ChainAware Agent Trust Score – owner fraud probability, feeder analysis, criminal record check, and farm detection are all directly relevant to the threat model. Set tier thresholds based on transaction risk: Trusted (600+) for high-value operations, Provisional (400+) for lower-risk flows with monitoring.

Secondary: RNWY for reputation display – show the RNWY score in your protocol’s agent directory alongside the ChainAware score. They answer different questions and the combination is more informative than either alone.

Optional: SkyeProfile attestations if your compliance framework requires cryptographically verifiable attestations as audit evidence. For the compliance context, see our DeFi Compliance and AML guide.

Agent marketplace or directory

Primary: RNWY – the on-chain trust oracle on Base enables smart contract-level minimum score requirements for job listing. The commerce job history (1.7M jobs) is directly relevant to marketplace quality filtering. The transparent published methodology means marketplace users can understand exactly why an agent scores as it does.

Secondary: ChainAware Agent Trust Score – surface it as a fraud intelligence layer alongside RNWY’s reputation score. The two scores are complementary: RNWY tells users whether the agent’s reviews are genuine; ChainAware tells users whether the human behind the agent has a history of financial fraud.

Enterprise workflow agent deployment

Primary: AXIS T-Score – for enterprise agents performing specific workflow tasks (research, compliance screening, content generation), task quality assurance is the primary concern. AXIS is the only platform that evaluates whether an agent does what it claims to do.

Secondary: ChainAware if the agent has financial execution permissions. Task quality and financial trustworthiness are both relevant for agents with write permissions to financial systems.

Agent creator wanting to understand their score

Agent creators interact with multiple trust systems simultaneously. Your agents are scored by every platform a buyer chooses to query. Understanding all five is therefore more important for creators than for buyers. Specifically:

• RNWY score: ensure your agent has genuine reviews from established reviewer wallets. Avoid requesting reviews from wallets that bulk-review across many agents – they will be detected as sybil reviewers and suppress your score
• ChainAware score: your owner wallet’s history is the primary input. A wallet with 12+ months of diverse DeFi activity scores significantly higher than a fresh wallet. If your feeder is a CEX withdrawal, this is a positive signal that surfaces automatically
• SkyeProfile: ensure your owner wallet holds governance tokens and participates in established protocols – the solvency and governance dimensions reward breadth of DeFi participation
• AXIS: if you want T-Score evaluation, ensure your agent returns reliable, consistent outputs and maintains audit trail quality across repeated task executions

The White Space: Five Capabilities Nobody Has Built Yet

The current agent trust infrastructure market is six months old. Consequently, significant white space remains – capabilities that no platform currently provides but that the market will almost certainly require as agentic commerce scales. The following five gaps represent the next investment and product opportunities in this category.

Gap 1: Agent-to-agent trust propagation

No platform currently answers this question: if Agent A scores Sovereign and has completed 10,000 successful interactions with Agent B, does that interaction history update Agent B’s trust score? In human systems, ongoing positive relationships build trust over time. In agent systems, every score is computed from static inputs without accounting for the accumulated interaction history between specific agent pairs. Building trust propagation that flows through agent interaction graphs – raising Agent B’s score based on verified positive interactions with high-scoring agents – would fundamentally change how trust compounds in the agentic economy.

Gap 2: Cross-registry agent identity resolution

An operator may deploy agents across ERC-8004, Olas, Virtuals, and SATI simultaneously. Currently, each registry treats these as separate identities. No platform provides unified entity resolution – grouping agents across registries that share the same owner wallet into a single entity profile. This matters because fleet-level behavior visible at the entity level (100 agents across 4 registries controlled by one owner) is invisible at the per-registry level (25 agents on each).

Gap 3: MCP server trust scoring

Every agent trust platform scores the agent itself. None score the MCP servers the agent calls. An agent connecting to a malicious or compromised MCP server is a trusted agent performing untrusted actions. As the MCP ecosystem grows – Smithery already indexes thousands of MCP servers – the trust question extends naturally from “who is the agent?” to “what tools is the agent using?”

Gap 4: Trust score-based insurance underwriting

No DeFi insurance protocol currently uses agent trust scores as an underwriting input. A protocol granting autonomous execution access to a Sovereign-tier agent (800+) takes on less risk than one granting the same access to a Provisional-tier agent (400-599). Insurance premiums, coverage limits, and deductibles could all be parameterised on agent trust scores – creating a financial market that prices the residual risk after trust gating rather than treating all agent access as equally risky.

Gap 5: Dynamic trust scores updating in real time

Current trust scores are computed at query time from static inputs and cached. None update continuously as new on-chain events occur. An agent whose owner wallet executes a suspicious transaction pattern at 14:00 UTC will not have its trust score updated until the next scoring cycle. Real-time trust score streaming – where scores update within seconds of relevant on-chain events – would enable dynamic access control that responds to emerging fraud signals rather than lagging behind them.

The Investor Lens: What Makes Agent Trust Infrastructure a Durable Market

For investors evaluating the agent trust infrastructure category, several structural dynamics shape the market’s long-term economics.

The TAM compounds with agent adoption

Agent trust infrastructure is a derived demand market – its TAM scales directly with agentic commerce adoption. McKinsey’s $3-5 trillion agentic commerce estimate implies that every dollar of economic activity flowing through autonomous agents creates a corresponding demand for trust verification of those agents. As Morgan Stanley projects , nearly half of online shoppers will use AI shopping agents by 2030. Each one of those agents represents a trust decision for every protocol or merchant it interacts with.

Consequently, market growth in agent trust infrastructure is structurally tied to the overall growth of agentic AI – a market with multiple large tailwinds including regulatory pressure (Know Your Agent protocols emerging from the EU AI Act framework), enterprise adoption (agents handling financial workflows requiring documented risk controls), and protocol incentives (DeFi protocols facing liability exposure from agent-initiated fraud).

Data network effects favour early movers with behavioral databases

Agent trust platforms that rely on behavioral databases – rather than purely algorithmic or review-based scoring – accumulate a compounding data advantage. A platform with one year of on-chain pair history knows which wallets created rug pools. A platform with two years knows which wallets have repeat patterns across multiple fraud campaigns. That historical depth cannot be compressed – a competitor starting today cannot buy the historical database that an early mover has built through continuous operation.

This dynamic differentiates behavioral fraud intelligence platforms from review-quality platforms. RNWY’s review quality algorithm could theoretically be replicated by a well-resourced team in months. The underlying behavioral database and fraud prediction model trained on years of on-chain data cannot. For context on how machine learning model development timelines apply to this space, see our AI-Powered Blockchain Analysis guide.

Complementary rather than winner-takes-all

The four distinct approaches in the market address different threat models that do not fully substitute for each other. RNWY’s review quality signal and ChainAware’s behavioral fraud intelligence are complementary – a protocol using both is better protected than a protocol using either alone. This means the agent trust market is likely to support multiple sustainable businesses serving different parts of the trust stack, rather than converging to a single dominant platform.

The parallel is the credit rating market – Moody’s, S&P, and Fitch coexist because rating agencies with complementary methodologies provide more value to the market than a single monopoly. Agent trust infrastructure may evolve similarly, with different platforms serving different trust dimensions in a layered stack. For investors, this implies that both the review quality layer (RNWY) and the behavioral fraud intelligence layer (ChainAware) have independent market positions rather than competing for the same slot in every protocol’s integration.

Regulatory tailwinds

The EU AI Act , which takes full effect in August 2026, creates documentation and risk assessment requirements for high-risk AI systems. Autonomous agents with financial execution permissions are a clear candidate for high-risk classification under this framework. Protocols operating in EU-regulated markets will need demonstrable risk controls for agent interactions – a requirement that agent trust scoring infrastructure directly satisfies. Additionally, Know Your Agent (KYA) protocols are emerging as the agent-layer equivalent of KYC, creating a compliance-driven pull for trust verification infrastructure beyond pure product adoption.

Frequently Asked Questions

Can I use multiple agent trust platforms simultaneously?

Yes – and for high-value use cases, this is the recommended approach. RNWY and ChainAware answer different questions about the same agent. Using RNWY for review quality and ChainAware for owner fraud intelligence produces a more complete picture than either alone. The integration is straightforward: make two API calls per agent and combine the results in your access control logic. DeFi protocol builders can set independent thresholds for each score – for example, requiring RNWY tier 3+ (genuine review history) AND ChainAware Trusted tier (600+) for full autonomous execution access.

Which platform is best for displaying trust to end users?

RNWY is the strongest choice for trust display because its methodology is fully published and each score shows its math. End users can understand exactly why an agent scored as it did – which reviewer wallets were flagged, which sybil patterns were detected, what the address age contributed. Transparency builds user confidence. ChainAware’s score is complementary but its weights are private (to prevent gaming), making RNWY more appropriate for user-facing display where explainability matters.

How do the different score scales compare?

The score scales are not directly comparable across platforms. RNWY scores out of 95 (not 100 – their maximum is 95 due to scoring mechanics). ChainAware and AXIS both use 0-1,000. DJD uses 0-100. SkyeProfile uses two independent axes rather than a single number. Converting between scales requires understanding what each platform actually measures, which is why the comparison table above focuses on capabilities rather than score values. An agent scoring 72/95 on RNWY and 650/1,000 on ChainAware is not inconsistent – those numbers describe entirely different assessments.

Does RNWY’s owner wallet score compete with ChainAware?

Not meaningfully. RNWY’s v1.1.0 update added owner wallet score as an informational field in the API response – but explicitly does not affect tier calculation or the primary trust score. The field surfaces the owner wallet’s RNWY-defined score as context for relying parties who want to incorporate it into their own decision logic. ChainAware makes the owner wallet score the primary input to the Agent Trust Score formula, combines it with feeder analysis and criminal record data, and applies trust delegation. The two approaches share the observation that owner wallet matters – but diverge completely on how to score it and how much weight it should carry.

What is ERC-8183 and how does it relate to agent trust?

ERC-8183 is a commerce protocol that gives AI agents trustless commerce capabilities – handling escrow, state transitions, and evaluator attestation for agent-to-agent job markets. The spec is intentionally minimal – it handles the commerce mechanics but explicitly does not handle trust scoring, discovery, or fraud detection. RNWY has built a marketplace and trust scoring layer on top of ERC-8183. ChainAware’s Agent Trust Score is compatible with ERC-8183 job markets as a pre-interaction trust gate – protocol teams can require a minimum Agent Trust Score before an agent can claim a job or receive escrowed funds.

How often do trust scores update?

Update frequencies vary by platform. ChainAware’s fraud prediction model retrains daily – meaning the fraud probability feeding into owner wallet scores updates continuously as new on-chain patterns emerge. Scores for specific agents update when new relevant events are detected (new agent registrations, owner wallet activity, feeder transactions). RNWY scores update as new reviews are submitted to the ERC-8004 Reputation Registry and as sybil analysis runs on reviewer wallets. AXIS T-Score updates based on runtime task execution data. None of the current platforms offer real-time streaming score updates – that remains a white space capability described above.

Is the ChainAware Agent Trust Score relevant for non-ERC-8004 agents?

Partially. The owner wallet and feeder address scoring works for any wallet address, regardless of whether it is associated with an ERC-8004 registration. A protocol that receives agent-initiated transactions from wallets not registered on any standard identity registry can still query ChainAware’s Fraud Detection API for the controlling wallet’s behavioral intelligence. The ERC-8004-specific signals (farm detection, trust delegation from registry data) require an ERC-8004 registration to function. However, the owner fraud probability, feeder analysis, and criminal record check work on any wallet regardless of registry status. For protocols on chains not yet covered by ERC-8004 registries, this means ChainAware provides partial Agent Trust Score functionality even before full ERC-8004 adoption on those chains.

Where can I read ChainAware’s full scoring methodology?

The complete methodology – including the five scoring layers, all flag definitions, score tier descriptions, and the trust delegation formula – is documented at chainaware.ai/learn/agent-trust-score. The signal categories are published. The exact weights and model coefficients remain private to prevent gaming. The equivalent documentation for the underlying Wallet Reputation Score (which feeds into the Agent Trust Score formula) is at chainaware.ai/learn/for-individuals/wallet-auditor.

Further Reading

• Agent Trust Score – Complete Methodology – the five scoring layers, all flags, tier definitions, and trust delegation formula
• The First Step in Agentic Commerce Isn’t Integration. It’s Trust. – the companion article covering the trust gap in DeFi protocol agent integrations
• Web3 Wallet Auditing Providers in 2026 – the same three-layer framework applied to the wallet intelligence market
• Web3 Analytics Tools for Dapps: Complete Comparison – where agent trust scoring fits in the broader DeFi analytics stack
• AI-Powered Blockchain Analysis for Crypto Security – the machine learning methodology behind ChainAware’s 98% fraud detection accuracy
• Rug Pull vs Pump and Dump – the fraud patterns that generate ChainAware’s criminal record database
• DeFi Compliance: KYT and AML Guide 2026 – regulatory context for DeFi agent integration compliance
• DeFi Credit Score Platforms Compared – how agent trust scoring combines with borrower creditworthiness assessment
• Prediction MCP Setup Guide – add ChainAware behavioral intelligence including Agent Trust Score to any Claude agent
• 32 Ready-Made Agents – pre-built Claude agents including agent verification, fraud detection, and compliance screening

ChainAware.ai is the Web3 Agentic Growth Infrastructure – behavioral intelligence for DeFi protocols, AI agents, and individual crypto users. 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency across 8 blockchains. Try free at chainaware.ai.

The post The Agent Trust Infrastructure Race: Who Is Building the Trust Layer for Agentic Commerce? first appeared on ChainAware.ai.

Your DeFi protocol is ready to integrate AI agents. You have evaluated the frameworks, chosen your ERC-8004 registry, mapped the wallet flows, and written the integration spec. Yet one question remains unanswered in that spec – a question that determines whether your agentic integration scales safely or becomes a fraud vector the moment it hits production volume.

Who is actually behind the agent you are about to trust with your users’ funds?

Agentic commerce is accelerating at a pace that has outrun the trust infrastructure supporting it. McKinsey estimates the model could redirect $3-5 trillion in global financial flows by 2030 . Meanwhile, 78% of financial institutions already expect fraud to spike specifically because of AI agents operating autonomously in commercial systems. The gap between “agent integration complete” and “agent interaction verified” is where the next generation of DeFi fraud will live.

This guide covers the entire problem – from the structural gap in the ERC-8004 standard to the specific signals that distinguish a legitimate agent from a manufactured one, to the concrete integration pattern that closes the trust gap in under 100ms per transaction.

Table of Contents

1. What Agentic Commerce Actually Means for DeFi Protocols
2. The Integration Stack Has a Trust Gap
3. Why Voting-Based Agent Reputation Fails at Scale
4. Know Your Agent: The Three Questions That Matter
5. Signal 1 – The Owner Wallet: Scoring the Human Behind the Agent
6. Signal 2 – The Feeder Address: Who Funded the Controller?
7. Signal 3 – The Criminal Record: Rug Pulls, Honeypots, and Prior Fraud
8. Trust Delegation: How a Strong Owner Legitimises a Fresh Agent Wallet
9. Farm Detection: One Operator, Dozens of Agents
10. EIP-7702 Delegation: The Hidden Controller Problem
11. The Trust-Aware Agent Integration Pattern
12. The Compounding Risk of Getting This Wrong
13. How ChainAware Compares to Other Agent Trust Platforms
14. Frequently Asked Questions

What Agentic Commerce Actually Means for DeFi Protocols

Agentic commerce describes the shift from humans clicking “confirm” to AI agents executing transactions autonomously on behalf of users. In Web3, this shift is not a future scenario – it is happening now, at scale, across every DeFi protocol that accepts agent-initiated transactions.

Agents are managing DAO treasuries, executing lending strategies, routing liquidity, screening counterparties, and processing governance votes – all without a human in the approval loop for each action. The operational efficiency gains are real. Furthermore, the fraud surface that comes with them is equally real and far less discussed.

For DeFi protocol builders, the critical insight is this: if your protocol accepts transactions from external wallets today, you are already serving agent-initiated transactions. Agent wallets are indistinguishable from human wallets at the RPC layer. Therefore, you do not need to deliberately “integrate agents” to be exposed to the trust problem – you already are exposed, today, because any wallet can be controlled by an agent rather than directly by a human.

The agentic commerce numbers clarify the urgency. Morgan Stanley projects that nearly half of online shoppers will use AI shopping agents by 2030, accounting for approximately 25% of their total spending . In DeFi specifically, the transition is faster – AI is moving from the advisory layer (suggesting trades) to the execution layer (completing them). The distinction between advice and execution is the distinction between a bad recommendation and an empty wallet. Consequently, DeFi protocol builders face the urgency of solving this in 2026, not 2028.

Traditional fraud detection systems are structurally unfit for this environment. As detailed in our guide on AI-Powered Blockchain Analysis for Crypto Security, rule-based systems generate false positive rates of 30-70% – and they produce those false positives specifically on the rapid, sequential, cross-category transaction patterns that legitimate AI agents exhibit. Therefore, you need a different approach: one that evaluates the agent’s identity and the human behind it, rather than flagging agent behaviour as inherently suspicious.

The Integration Stack Has a Trust Gap

A typical agentic commerce integration in 2026 follows a well-established pattern. The agent framework (ElizaOS, Virtuals, a custom build) registers an identity on the ERC-8004 Identity Registry. Subsequently, that identity is referenced when the agent initiates interactions with DeFi protocols. The protocol’s smart contract processes the transaction. Funds move.

Every layer in that stack has tooling, documentation, and standards. Agent frameworks have deployment guides. ERC-8004 has a specification and a registry of 240,000+ agents across Ethereum, BSC, Base, and Avalanche . Smart contracts have audit firms. Yet the gap between the ERC-8004 registry lookup and the protocol interaction has no standard tooling – and it is precisely where trust decisions need to happen.

The ERC-8004 registry tells you four things about an agent: that it exists, which wallet controls it, which wallet receives its payments, and what URI points to its agent card JSON. Those four data points answer the question “does this agent have an identity?” They do not answer the question “should I trust this agent with autonomous execution?”

Specifically, the registry tells you nothing about:

• Whether the owner wallet has a history of creating rug pull pools or honeypot tokens
• Whether the owner was funded by a mixer, a sanctioned address, or a known fraud operator
• Whether this agent is one of 47 registered in the same block by the same operator running a Sybil farm
• Whether the wallet controlling this agent also controls the 46 agents that gave it positive reviews

This is the trust gap. Moreover, it is not an oversight in the ERC-8004 specification – the standard explicitly leaves scoring to third parties. As a DeFi protocol builder, you are therefore responsible for filling that gap in your own integration layer.

For context on how behavioral wallet intelligence fills similar gaps in fraud detection, see our complete guide to Web3 Wallet Auditing Providers in 2026. The same principle applies at the agent layer: raw identity data requires an intelligence layer on top before it becomes a trust signal.

Why Voting-Based Agent Reputation Fails at Scale

ERC-8004 includes a built-in Reputation Registry – a standard interface for agents to receive and query peer feedback. The design is intentionally open: any agent can leave a review, any protocol can read the scores, and the aggregation algorithm is left to third parties. On paper, this sounds like a reasonable decentralised trust mechanism. In practice, it is a manufactured-trust system waiting to be exploited.

The attack requires minimal technical sophistication. An operator deploys 50 agent wallets. Each wallet reviews every other wallet positively. All 50 accumulate reputation scores indistinguishable from agents with genuine peer endorsements. Total cost: gas fees for the review transactions, which on BSC or Base amounts to a few dollars. Total time: hours. Total manufactured trust: a full reputation history that any naive integration will treat as legitimate.

Furthermore, the problem compounds in agentic commerce contexts. When B2B agent networks operate where AI buyers negotiate directly with AI sellers in fractions of a second , the speed of manufactured-reputation exploitation is not limited by human review cycles. One fraudulent agent with a manufactured score can interact with thousands of protocol users autonomously before any human notices the pattern.

Voting-based reputation also has a specific structural blind spot: it cannot distinguish between an agent with 100 genuine endorsements and an agent whose owner simultaneously controls the 100 endorsing agents. Consequently, any trust system that reads only the Reputation Registry score is solving the wrong problem. The question is not “how many agents have endorsed this agent?” The correct question is “who controls this agent, and what have they done on-chain?”

This distinction drives the entire design of the ChainAware Agent Trust Score. Rather than reading the ERC-8004 Reputation Registry, we look behind the agent at the behavioral history of the wallets controlling it and funding its controller. The result is a trust signal that cannot be manufactured in hours and cannot be faked by a cluster of cooperating wallets.

Know Your Agent: The Three Questions That Matter

Know Your Agent (KYA) is emerging as the agent-layer equivalent of KYC. However, unlike KYC – which verifies identity documents and requires data collection – KYA for DeFi is necessarily on-chain behavioral. There are no passports in Web3. There is only transaction history, and that history is immutable, public, and available for scoring without touching any personal data.

A robust KYA check for any ERC-8004 agent answers exactly three questions. Together, these three questions generate a trust signal that is structurally difficult to fake and impossible to manufacture overnight.

Question 1: Who controls this agent?

Every ERC-8004 agent has an owner wallet – the address that holds the ERC-721 NFT representing the agent’s on-chain identity. This is the human or entity behind the agent. Scoring that wallet’s behavioral history is the foundation of any meaningful trust assessment.

Question 2: Who funded the controller?

The feeder address – the wallet that funded the owner – is the signal most agent trust platforms cannot reach. It is also the hardest signal to fake, because it requires either real capital from a legitimate source or exposure to traceable fraud infrastructure. An owner wallet can be freshly created and carefully aged. The funding source is immutable on-chain history.

Question 3: Has the controller done this before – in a bad way?

A year of on-chain pair history combined with token audit data produces a direct criminal record check for the agent controller. Has this wallet created honeypot tokens? Has it created liquidity pools and removed funds in rug pull patterns? Has the feeder funded previous rug pull operators? These questions have definitive on-chain answers – and no peer-review system can surface them.

The following three sections address each signal in depth, including how it feeds into the Agent Trust Score formula and what it means for your integration.

Signal 1 – The Owner Wallet: Scoring the Human Behind the Agent

The owner wallet is the single most important input to any agent trust score. Everything else – the agent wallet, the agent card, the reputation registry score – can be created fresh for a new fraud operation. The owner wallet’s behavioral history cannot.

ChainAware scores the owner wallet using the same three-pillar Reputation Score formula applied across 20M+ wallet personas:

ReputationScore = (1000/110) × (experience + 1) × (risk_capability + 1) × (1 − fraud_probability)
Maximum: 1,000

Each pillar captures a distinct dimension of the owner’s on-chain identity.

Experience

Experience measures how long and how actively the owner wallet has operated on-chain. A wallet with 18 months of diverse DeFi interactions – lending, trading, bridging, staking across multiple protocols – scores high on experience. Conversely, a wallet created three weeks ago that has done nothing but register agents scores near zero. Experience is hard to accelerate, because it is a function of time as much as activity. An operator cannot age a fresh wallet by transacting intensively for a week and matching the experience score of a genuinely established participant.

Risk Capability

Risk capability measures the behavioral breadth of the owner wallet. Does it interact with a range of DeFi protocols, or does it show narrow, mechanical patterns consistent with a purpose-built fraud wallet? Legitimate DeFi participants accumulate a diverse transaction graph over time – different counterparties, different protocol types, different token categories. Fraud wallets tend to exhibit concentrated patterns: high transaction frequency in a narrow activity type, often with timing patterns that indicate scripted rather than human behavior.

Fraud Probability

Fraud probability is ChainAware’s predictive AI model output – a score between 0.0 and 1.0 representing the likelihood that the owner wallet will engage in fraudulent behavior. This is not a blacklist check. Blacklists are reactive; they flag addresses after fraud has been confirmed. The ChainAware fraud model is predictive: it scores behavioral patterns against 20M+ wallet personas to estimate forward-looking risk, identifying likely fraud actors before they have generated a confirmed fraud record. For a detailed explanation of the machine learning methodology, see our AI-Powered Blockchain Analysis guide.

The Reputation Score applied to the owner wallet produces a single 0-1000 number that feeds into the Agent Trust Score formula as the primary input. A strong owner score (800+) indicates a Sovereign-tier controller with genuine on-chain history. A weak owner score (below 200) flags an Untrusted controller regardless of how clean the agent’s own wallet appears.

Signal 2 – The Feeder Address: Who Funded the Controller?

The feeder address is ChainAware’s most distinctive signal in the Agent Trust Score – and the signal that no competing agent trust platform currently reaches. RNWY surfaces the owner wallet but marks it as informational, non-scoring data. SkyeProfile performs partial operator wallet analysis. Neither traces the funding source of the controller.

ChainAware traces feeder addresses for approximately 38% of indexed agents. That 38% coverage rate reflects the on-chain reality: some owner wallets receive funds from obfuscated sources, some from multiple feeders that cannot be unambiguously attributed, and some from the native chain’s genesis or bridge infrastructure. When the feeder is traceable, the signal is highly informative.

Feeder categories and their trust implications

CEX withdrawal (Binance, Coinbase, Kraken, OKX, and others): A feeder address that is a verified CEX hot wallet implies that the owner wallet’s initial funding came from a centralized exchange withdrawal. CEX withdrawals imply the controller passed KYC somewhere upstream – not necessarily ChainAware’s KYC, but some identity verification process at deposit. This is the strongest positive feeder signal available. ChainAware flags this as FEEDER_CEX_VERIFIED and applies the maximum feeder factor in the scoring formula.

Known fraud operator or mixer: A feeder address that is a confirmed Tornado Cash wallet, ChipMixer output, or address previously flagged in ChainAware’s fraud database propagates that fraud signal directly to the agent score. An owner wallet funded by a mixer is not automatically fraudulent – there are legitimate privacy use cases – but combined with other risk signals it is a strong indicator of deliberate fund obfuscation. Mixers and confirmed fraud feeders apply a hard cap to the Agent Trust Score regardless of how clean the owner wallet’s own transaction history appears.

Unknown or obfuscated feeder: When the feeder cannot be determined, ChainAware applies a penalty to the feeder factor. Obfuscation is not neutral – the absence of a traceable funding source is itself a risk signal. Legitimate operators who funded their owner wallets via normal CEX withdrawals have nothing to hide and produce traceable feeder paths. Operators who deliberately route funds through multi-hop paths to obscure the source are doing so for a reason.

For compliance-oriented DeFi protocols, the feeder analysis also connects directly to AML obligations. Our guide on Blockchain Compliance for DeFi: KYT and AML in 2026 covers the regulatory context in detail. Notably, feeder address analysis extends the transaction monitoring horizon beyond the immediate counterparty – which is precisely what FATF’s Travel Rule guidance asks for in the context of virtual asset transfers.

Signal 3 – The Criminal Record: Rug Pulls, Honeypots, and Prior Fraud

This is the signal that makes the ChainAware Agent Trust Score genuinely unique – and the signal that matters most for DeFi protocol builders who have been operating in the space long enough to know that today’s agent creator is often yesterday’s rug pull operator wearing a fresh wallet.

ChainAware maintains a database built from one year of on-chain pair history and token audit data. Specifically, this database captures:

• Token contracts flagged as honeypots by ChainAware’s algorithmic analysis
• The creator wallet address for each honeypot token
• Liquidity pools where the creator removed funds in patterns consistent with rug pull execution
• The creator wallet address for each rug pull pool

Before computing the Agent Trust Score, ChainAware cross-references both the owner wallet and the feeder address against this database. Any match generates a hard cap on the final score – a ceiling that no other scoring signal can override.

The logic here is direct: a single confirmed rug pull or honeypot in an agent controller’s history is a disqualifying signal for autonomous execution trust. An operator who has previously stolen from retail investors through manufactured liquidity or tax-trap tokens is not a different actor simply because they have registered a new agent identity on ERC-8004. The on-chain history is permanent. The behavioral record cannot be expunged.

As we document in our guide to Rug Pull vs Pump and Dump: How Crypto Fraud Extracts Wealth from Retail Investors, approximately 95% of new pools on PancakeSwap end in rug pulls. Furthermore, the operators behind those pools are not typically first-time offenders – they are repeat actors who rotate wallets between campaigns. Connecting that historical fraud record to new agent registrations is what allows ChainAware to catch the serial fraudster who is simply moving from token launches to agent deployments as the market cycle shifts.

Feeder criminal record: the compounding signal

Criminal record analysis applies not only to the owner wallet but also to the feeder address. Consider the operational pattern of a sophisticated fraud operator:

1. Operator runs rug pull campaigns using Wallet A (primary fraud wallet, now flagged)
2. Operator creates fresh Wallet B with no fraud history
3. Wallet A funds Wallet B – the feeder relationship is recorded on-chain
4. Wallet B registers agents on ERC-8004, presenting a clean owner wallet history
5. Any platform that scores only the owner wallet (Wallet B) misses the connection entirely

ChainAware’s feeder analysis catches step 4. The funding source (Wallet A) has a confirmed rug pull history in our database. Therefore, Wallet B’s agents receive a hard cap score regardless of how clean Wallet B’s own transaction history appears. This is the operational pattern that makes the feeder signal irreplaceable – it is the signal sophisticated actors spend the most effort obscuring, precisely because it is the signal that most reliably connects new operations to old fraud records.

Trust Delegation: How a Strong Owner Legitimises a Fresh Agent Wallet

Agent wallets present a specific challenge for naive scoring approaches. These wallets are frequently created specifically for the agent – they are fresh addresses with no transaction history, no counterparty network, and no behavioral record. A scoring approach that treats wallet age and transaction history as primary inputs would therefore penalise every newly registered agent regardless of the owner’s reputation. That produces low scores for legitimate agents and renders the score less useful as a gate for agentic commerce integrations where new agents are continuously deployed.

ChainAware solves this problem with trust delegation. The owner wallet’s Reputation Score sets a floor for the agent wallet’s effective score. A strong owner partially transfers credibility to the fresh agent wallet. The exact delegation factor depends on feeder availability and the owner’s own fraud status.

# Trust delegation: owner lifts fresh agent wallet score
delegated_floor  = owner_score × delegation_factor

# Delegation factor varies by context:
# - Normal (feeder available, owner clean): 0.6
# - Feeder unknown (obfuscation signal):    0.3
# - Owner fraud-flagged:                    0.1

effective_wallet = max(wallet_score, delegated_floor)

This means a reputable developer deploying their first agent scores appropriately high – even with a fresh payment wallet – because the owner’s 18-month behavioral record delegates trust downward to the new agent wallet. A fraud-flagged owner, by contrast, cannot delegate any meaningful trust regardless of how the fresh agent wallet appears. The delegation factor collapses to near zero, and the agent score reflects the owner’s history rather than the wallet’s lack of it.

Trust delegation also captures the inverse correctly. If an agent wallet has a genuinely clean and established history (because the same operator has deployed agent wallets before), that score is used directly without needing the delegation floor. The formula takes the maximum of the two – the wallet’s own score and the delegated floor from the owner – ensuring that genuine wallet history is never penalised by the delegation mechanism.

This mechanism is unique to ChainAware among agent trust platforms operating on ERC-8004 in 2026. Competing platforms that surface the owner wallet as informational data but do not integrate it into their scoring formula cannot implement delegation – because delegation requires both the owner score and the wallet score to be computed on a comparable scale and combined algorithmically.

Farm Detection: One Operator, Dozens of Agents

Multi-agent orchestration is one of the defining architectural trends in agentic AI for 2026. Orchestrator agents coordinate specialised sub-agents working in parallel – a legitimate pattern that produces significant efficiency gains for complex workflows. However, the same architecture that enables powerful legitimate multi-agent systems also enables a specific attack pattern in agentic commerce: agent farming.

Agent farming is the practice of a single operator registering a large fleet of agents, typically in bulk during a narrow time window, with the goal of:

• Cross-endorsing each other to manufacture reputation scores
• Flooding agent marketplaces with controlled supply to manipulate pricing or availability
• Creating the appearance of ecosystem depth across multiple agent identities controlled by one bad actor
• Operating coordinated fraud campaigns across dozens of agent wallets that each individually appear to have limited exposure

ERC-8004 places no restrictions on how many agents a single owner can register. Consequently, a single wallet can register 500 agents in a single afternoon with no protocol-level friction. Individual agent scoring – which is what every competitor in this space does – is blind to the fleet-level pattern. Each agent scores independently; none of them individually triggers a threshold that reveals the fleet behavior.

ChainAware maintains an owner profile database that tracks agent fleet size per owner across all indexed chains. Owners controlling large numbers of agents receive a farm detection signal that suppresses the score for every agent in their fleet. Furthermore, the specific pattern of same-block registration – multiple agents minted in a single block – carries additional weight, because it indicates automated bulk registration rather than organic deployment over time.

The farm detection signal appears in the API response as the FARM_DETECTED flag. It does not expose the specific threshold that triggered the signal – sharing that threshold would tell operators exactly how many agents they can register before triggering detection. Instead, the flag communicates the category of signal without revealing the calibration.

From a DeFi protocol integration perspective, farm detection is the signal that turns individual agent trust scoring into a fleet-level intelligence system. Agents from the same owner share a trust destiny – if the owner’s fleet pattern is suspicious, every agent in that fleet is suspect regardless of how any individual agent scores in isolation.

EIP-7702 Delegation: The Hidden Controller Problem

EIP-7702 allows Externally Owned Accounts (EOAs) to delegate control to a secondary address for a single transaction or extended period. In the agent context, this means the wallet registered as the ERC-8004 agent owner may not be the wallet actually controlling the agent’s behavior – a secondary delegated address might be executing transactions on behalf of the nominal owner.

ChainAware detects EIP-7702 delegation for agent owner wallets. When detected, the scoring process adds the delegate address to the analysis and takes the lower of the two scores – owner and delegate – as the effective owner score feeding into the Agent Trust Score formula.

This matters because EIP-7702 delegation is a specific mechanism that sophisticated actors can use to obscure the real controlling entity behind an agent. The nominal owner wallet might have a strong reputation score built over many months. The delegate might be a fresh fraud wallet with no history. Without EIP-7702 analysis, the strong nominal owner score masks the fraudulent delegate’s risk profile. With it, the delegate’s low score pulls the effective owner score down to reflect the actual controlling entity.

Approximately 5% of indexed ERC-8004 agents have EIP-7702 delegated ownership, based on ChainAware’s current database. Agents with EIP-7702 delegation are flagged explicitly in the API response as EIP7702_DELEGATED – giving protocol builders the option to apply additional scrutiny to this category regardless of the final numerical score.

The Trust-Aware Agent Integration Pattern

A DeFi protocol that has addressed the trust gap adds one step between the ERC-8004 registry lookup and the transaction execution. That step takes under 100ms, requires one API call, and produces a structured output that the protocol’s access control layer can act on directly.

Agent initiates transaction
  ↓
Resolve agent_id → owner_address + agent_wallet (ERC-8004 registry)
  ↓
GET /erc8004/agent/{chain_id}/{agent_id}/trust-score
  ↓
Response:
  {
    "agent_trust_score": 882,
    "tier": "Sovereign",
    "flags": ["FEEDER_CEX_VERIFIED"]
  }
  ↓
score ≥ protocol_threshold → execute
score < protocol_threshold → reject or route to human review

The threshold is a protocol-level decision. Different use cases warrant different risk tolerances:

The ChainAware Agent Trust Score API integrates directly with the Prediction MCP server, meaning any Claude-based DeFi agent can call the scoring endpoint as a native MCP tool call without custom API integration code. For teams building on the MCP stack, see our Prediction MCP setup guide and our library of 32 ready-made agents that already include agent verification logic.

Additionally, the trust check does not add friction for legitimate agents. A reputable developer deploying their first agent – with a strong owner wallet history and a CEX-verified feeder – scores above 800 through trust delegation even with a brand-new agent payment wallet. The check identifies the fraudulent operator while leaving the legitimate one unrestricted. That asymmetry is the operational definition of a useful trust system.

The Compounding Risk of Getting This Wrong

Human-initiated fraud and agent-initiated fraud differ in one fundamental operational characteristic: velocity. A fraudulent human interacting with your protocol manually can execute perhaps dozens of interactions before detection. A fraudulent agent operating autonomously can execute thousands of interactions in the same period – at machine speed, without sleep, without rate-limit awareness unless you specifically implement it, and with the full behavioral sophistication of the AI model powering it.

Therefore, the cost of a single misidentified agent is not comparable to the cost of a single misidentified human user. The exposure scales with the agent’s operational capacity. A lending protocol that grants a fraudulent agent autonomous execution access for six hours faces losses that scale with the protocol’s TVL and the agent’s transaction rate – not with a single transaction amount.

Traditional fraud detection tools are particularly poorly suited to this environment for reasons we explore in detail in our DeFi Compliance and KYT guide. Rule-based systems flag agent behavior as suspicious because agents naturally exhibit the patterns those rules target: high velocity, cross-category activity, unusual timing distributions. Consequently, you end up blocking legitimate agents while missing sophisticated fraudulent ones that have been engineered to mimic human behavioral patterns.

The compounding risk calculation is straightforward. One fraudulent agent operating undetected for six hours at 100 transactions per minute generates 36,000 protocol interactions. If each interaction involves 0.1 ETH and the fraud extracts 50% of interaction value, that is 1,800 ETH in losses from a single agent integration oversight. The trust check that would have caught this agent costs one API call taking under 100ms. The return on that 100ms is measured in protocol TVL.

For protocols already implementing compliance infrastructure, the Agent Trust Score also extends the KYT monitoring timeline backward – connecting transaction monitoring at the agent level to the historical record of the human behind the agent. Our Web3 Analytics Tools comparison for 2026 covers how agent-level intelligence integrates with broader protocol analytics stacks.

The Five Agent Trust Score Tiers – What Each One Means for Your Protocol

The Agent Trust Score produces a single number between 0 and 1000, mapped to five tiers. Each tier has a distinct operational meaning for DeFi protocol builders – and a distinct set of recommended actions. Understanding what produces each tier helps protocol teams calibrate their threshold decisions correctly.

Tier 5 – Sovereign (800-1000)

Sovereign agents have an established owner wallet with strong on-chain history, a clean or CEX-verified feeder address, no criminal record signals, and no farm detection flags. Trust delegation produces a high effective wallet score even for fresh agent payment wallets. Sovereign-tier agents are suitable for the highest-risk autonomous operations – large-value lending, treasury management, governance participation with material financial consequences. Protocol teams can grant Sovereign agents the same execution permissions they would grant to established protocol participants.

Tier 4 – Trusted (600-799)

Trusted agents have a strong owner wallet, an available and generally clean feeder address, and no hard-cap signals from criminal record checks. The score may be below 800 because the owner wallet has moderate rather than extensive history, or because the agent wallet has minimal activity offset by partial trust delegation. Trusted agents are suitable for standard DeFi integrations – trading agents, yield optimisers, and automated compliance workflows – where the individual transaction risk is moderate and human monitoring is available as a backstop.

Tier 3 – Provisional (400-599)

Provisional agents show mixed signals. The owner wallet may have limited history, the feeder address may be unknown or unverified, or the agent wallet may be very fresh with insufficient trust delegation from the owner score to compensate. Provisional agents should not be granted unsupervised autonomous execution access for high-value operations. However, they are appropriate for lower-risk automated workflows with active monitoring – for example, read-only data queries, low-value token swaps, or agentic onboarding flows where individual transaction size is capped. DeFi protocols integrating Provisional agents should implement transaction volume limits and velocity monitoring as additional safeguards.

Tier 2 – Elevated Risk (200-399)

Elevated Risk agents have weak owner history, obfuscated feeder addresses, soft farm detection signals, or agent wallets that score poorly even after trust delegation. These agents should not be permitted autonomous financial execution. If a protocol needs to serve Elevated Risk agents – for example, in a permissionless DEX context – transaction size limits, velocity caps, and real-time monitoring should all be active. The FEEDER_UNKNOWN flag on an Elevated Risk agent is a particularly notable combination: it indicates both limited owner history and deliberate funding obfuscation, suggesting a higher likelihood of coordinated fraud activity.

Tier 1 – Untrusted (0-199)

Untrusted agents have active fraud signals, confirmed rug pull or honeypot history, confirmed farm detection, sanctioned address exposure, or blacklisted repeat offender status. These agents should not receive autonomous execution access under any circumstances. The score is not borderline – it reflects definitive fraud signals from immutable on-chain history. Untrusted agents attempting to access your protocol should be blocked at the access control layer before any transaction reaches the execution layer. Furthermore, DeFi teams running compliance programs may want to log Untrusted agent interaction attempts as part of their AML reporting, as these attempts represent potential fraud activity on record. For the full compliance context, see our MiCA Compliance for DeFi learn page.

How ChainAware Compares to Other Agent Trust Platforms in 2026

The agent trust scoring market emerged rapidly alongside ERC-8004’s mainnet launch in January 2026. Several platforms have moved quickly to stake positions in the space. Understanding the differentiation between them matters for DeFi protocol builders choosing integration partners.

RNWY is the most established competitor in the ERC-8004 space and uses a sophisticated review-quality analysis that detects coordinated fake review patterns. However, their core methodology solves fake reviews, not fake owners. ChainAware solves fake owners – a harder problem with higher-stakes implications for autonomous execution trust. Both signals are complementary; they are not substitutes for each other.

AXIS T-Score is entirely off-chain – it scores agent runtime performance across 11 behavioral dimensions rather than on-chain ownership identity. This makes it useful for evaluating how well an agent executes tasks, but irrelevant for trust decisions about the human behind the agent. For a protocol deciding whether to grant autonomous execution access, AXIS covers a different question than ChainAware does.

The feeder address, criminal record, and trust delegation signals are currently unique to ChainAware across all indexed agent trust platforms. Those signals require a database of over one year of on-chain pair history, a token audit data pipeline, and a predictive fraud model trained on 20M+ wallet personas – infrastructure that takes years to build and cannot be replicated quickly. Additionally, for more context on how ChainAware positions against broader analytics alternatives, see our Web3 Analytics Tools Comparison for DeFi Dapps in 2026.

The moat is the data, not the formula

ChainAware publishes the categories of signals that feed into the Agent Trust Score. However, the exact weights, thresholds, and model coefficients are not published – not because the methodology is proprietary for competitive reasons, but because publishing thresholds would allow bad actors to calibrate their behavior to stay just below each detection cap.

More importantly, the real moat is not the formula. The moat is the data. An operator who knows every weight and threshold in the Agent Trust Score formula still cannot change their on-chain history. A wallet that created a honeypot token in November 2025 cannot remove that event from the blockchain. A feeder address that funded rug pull operators throughout 2025 cannot alter its transaction graph. The formula can be known. The data cannot be changed. That asymmetry is what makes on-chain behavioral intelligence a durable trust infrastructure rather than a gameable reputation system.

Frequently Asked Questions

What chains does the Agent Trust Score cover?

ChainAware’s Agent Trust Score indexes ERC-8004 agents across Ethereum mainnet, BSC (BNB Chain), Base, and Avalanche C-Chain, with Mantle in progress. These five chains cover the majority of ERC-8004 registry activity. The owner wallet and feeder analysis draws on ChainAware’s broader behavioral intelligence database, which covers 8 blockchains total including Polygon, TON, TRON, and HAQQ.

How long does the Agent Trust Score API take to respond?

The Agent Trust Score API returns results in under 100ms for agents already in the ChainAware database. First-time scoring of a newly registered agent may take slightly longer as the owner and feeder addresses are resolved and scored. Pre-scoring of agents during indexing ensures that the vast majority of ERC-8004 agents in the registry return sub-100ms scores at query time.

Does the Agent Trust Score require any PII or KYC data?

No. The Agent Trust Score is derived entirely from public on-chain data. No personal information is collected, no identity verification is required, and no data is stored beyond what is already publicly available on the blockchain. This makes the score compatible with DeFi’s privacy-first ethos and compliant with GDPR and similar privacy regulations by design.

Can an agent improve its score over time?

Yes – through the owner wallet’s behavioral history, not through the agent wallet itself. As the owner wallet accumulates genuine on-chain experience, interacts with a broader range of protocols, and maintains a clean fraud probability score, the Reputation Score feeding into the Agent Trust Score improves. Trust delegation then carries that improved score to the agent wallet. However, criminal record signals (rug pull history, honeypot creation) are permanent hard caps – they do not improve over time because the underlying on-chain events are immutable.

What happens when an agent is transferred to a new owner?

ERC-8004 agents are ERC-721 NFTs and can be transferred between wallets. When ChainAware detects an ownership transfer, the Agent Trust Score recalculates using the new owner wallet’s behavioral history. This is intentional: the trust score tracks the current controlling entity, not the original registrant. Consequently, an agent cannot inherit a previous owner’s strong score after transfer – each new owner is scored from their own on-chain history.

How does Agent Trust Score integrate with the Prediction MCP?

The Agent Trust Score is available as a native tool through ChainAware’s Prediction MCP server. Any Claude-based agent can call agent_trust_score(chain_id, agent_id) as a natural language tool call, receiving the structured score and flags response without custom API integration code. For protocol teams building on the MCP stack, this means agent verification can be added to any existing MCP-connected workflow in minutes rather than days.

Is the Agent Trust Score different from the Wallet Reputation Score?

The Agent Trust Score uses the same 0-1000 scale and the same underlying Reputation Score formula as ChainAware’s Wallet Reputation Score. However, it applies that formula to multiple addresses simultaneously (owner wallet, agent wallet, feeder address) and combines them using trust delegation logic and fleet-level farm detection signals that do not exist in the standalone Wallet Reputation Score. The two scores are directly comparable on the same scale – a wallet Reputation Score of 750 and an Agent Trust Score of 750 represent the same trust tier.

How does ChainAware handle agents with no traceable feeder address?

When the feeder address cannot be determined – either because the owner wallet was funded through multi-hop paths that obscure the source, or through infrastructure (bridges, faucets) that does not produce an attributable single feeder – ChainAware applies a feeder-unknown penalty to the Agent Trust Score. This penalty reflects the information asymmetry: legitimate operators funded through normal CEX withdrawals produce traceable feeder paths; operators who route funds to obscure the source are doing so for a reason. The penalty is not a hard cap – a very strong owner wallet and clean criminal record can partially offset it. Nevertheless, unknown feeder remains a risk signal that appears in the API response as the FEEDER_UNKNOWN flag.

What does a DeFi credit scoring integration look like alongside Agent Trust Score?

For lending protocols specifically, Agent Trust Score and DeFi credit scoring serve complementary functions. The Agent Trust Score answers “should this agent be permitted to interact with my protocol at all?” – a gate decision. The DeFi credit score answers “given that this agent is permitted, what collateral ratio and interest rate tier should apply to its lending activity?” – a parameterisation decision. Running both checks in sequence gives lending protocols the most complete picture: a verified legitimate agent operating at its correct creditworthiness tier.

Further Reading

• Agent Trust Score – Complete Methodology – the full technical explanation of how the score is computed, including all five scoring layers and flag definitions
• Web3 Wallet Auditing Providers in 2026 – the complete landscape of wallet intelligence providers, from raw data to actionable predictions
• AI-Powered Blockchain Analysis for Crypto Security – how ChainAware’s fraud prediction model achieves 98% accuracy
• Rug Pull vs Pump and Dump – the fraud patterns that feed the Agent Trust Score criminal record database
• Blockchain Compliance for DeFi: KYT and AML Guide – regulatory context for DeFi protocol compliance in 2026
• DeFi Credit Score Platforms Compared – how to combine agent trust verification with borrower creditworthiness assessment
• Prediction MCP Setup Guide – add ChainAware behavioral intelligence to any Claude agent in minutes
• 32 Ready-Made Agents – pre-built Claude agents including agent verification, fraud detection, and compliance screening
• Web3 Analytics Tools for Dapps: Complete Comparison – where agent trust scoring fits in the broader DeFi analytics stack
• Blockchain Data Providers for AI Agents – the data infrastructure layer that feeds agent intelligence systems

ChainAware.ai is the Web3 Agentic Growth Infrastructure – behavioral intelligence for DeFi protocols, AI agents, and individual crypto users. 20M+ wallet personas, 98% fraud detection accuracy, <100ms API latency across 8 blockchains. Try free at chainaware.ai.

The post The First Step in Agentic Commerce Isn’t Integration. It’s Trust. first appeared on ChainAware.ai.

The plateau is not good news. A $32.5M weekly floor means retail investors on PancakeSwap V2 are losing approximately $4.6M every single day – without headlines, without emergency responses, and without industry-wide concern.

The Plateau: What Two Flat Weeks Signal

The compression-then-spike-then-plateau pattern is now clearly visible in the 22-week dataset. Week 20 produced the largest WoW spike in the dataset (+179.9%). Week 21 saw the fraud value pull back slightly while rug events hit an 8-week high. Week 22 is essentially identical to Week 21 – both in fraud value and event count direction. This is how extraction cycles end: not with a dramatic collapse but with a gradual compression toward a new operating baseline.

Reading the Plateau

The removed-to-added liquidity ratio held steady at 1.48x in W22 vs 1.46x in W21. Both are well above the 1.0x break-even threshold – creators continue extracting 48% more than they seed on average. Pool creation is stable at 11,300 vs 11,371. Every metric points to operational steadiness rather than either expansion or contraction.

The 5-week trailing average (W18-W22) now stands at $26.4M – still below the 22-week mean of $28.9M, but climbing steadily as the low-extraction weeks of W17-W19 drop further back in the rolling window. By W23 the trailing average will cross $27M unless extraction drops significantly. The 22-week mean of $28.9M represents the structural extraction capacity of the PancakeSwap V2 rug pull industry when operating at normal intensity. The current plateau at $32.5M is running above that mean – not below it.

Two weeks at $32.4M-$32.5M also suggests the W20 spike operators have not fully exited – they have compressed activity while maintaining elevated baseline extraction. The compression-then-spike cycle that produced W20 typically repeats. Based on the W3-W8 and W13-W20 cycle patterns, the next acceleration window opens somewhere in W24-W26. For the full cycle analysis and the original 20-week dataset, see our $569M PancakeSwap V2 analysis.

RUG PULL DETECTOR V3 – FREE

Check Any Pool Before You Invest – 90.1% Accuracy

Behavioral analysis of contract creators + smart contract code inspection. Handles pools and individual tokens. No signup required. For businesses, subscribe to the API. For AI agents, X402 protocol is enabled.

→ Run a Free Check at chainaware.ai/rugpull

22-Week Running Total: $634.8M

How to Protect Yourself

At $32.5M per week, the math is straightforward: 6,557 rug pulls across 11,300 new pools means roughly 58% of all new pools created in W22 ended in a confirmed rug pull event. Before investing in any new token or pool on PancakeSwap V2, run ChainAware’s free tools:

• Rug Pull Detector V3 – behavioral analysis of the contract creator + smart contract code inspection. 90.1% prediction accuracy. Free, no signup.
• Fraud Detector – full behavioral history of any deployer wallet. 98% fraud prediction accuracy.
• Wallet Auditor – for P2P transactions. Complete behavioral profile of any receiving wallet before sending funds.

NEXT WEEK

Week 23 Data Published Every Monday

ChainAware publishes fresh PancakeSwap V2 rug pull data every week – pool creation, rug events, fraud value, and week-over-week analysis. Follow the archive for every weekly update.

→ Follow the Rug Pull News archive

About This Tracker

The ChainAware Weekly Rug Pull Tracker measures the most basic, mathematically verifiable form of rug pull on PancakeSwap V2: a contract creator adds liquidity (Mint event), retail investors buy in, and the creator removes more than they added (Burn event). The difference is confirmed retail loss. This definition is conservative – it excludes LP token transfer rug pulls, unlocked token sell-offs, honeypot contracts, and associated wallet extraction. Numbers reported here represent the confirmed floor. For complete methodology, see chainaware.ai/resources/rugpull-verification .

The post $32.5M Extracted in Week 22 – Two Consecutive Weeks at the Same Level first appeared on ChainAware.ai.

The 21-week running total now stands at $602,689,131 – crossing the $600M milestone. On average, retail investors on PancakeSwap V2 have lost $28.7M every single week of 2026.

Week-over-Week: More Rugs, Lower Value Per Rug

The divergence between fraud value (-15.7%) and rug event count (+24.4%) is the most important signal in the W21 data. These two metrics usually move together – more events mean more extraction. When they diverge, it indicates a structural shift in who is operating and how.

What the Divergence Means

In W20, a small number of large-scale operators extracted high value per pool – the removed-to-added liquidity ratio was 1.75x, meaning creators removed $1.75 for every $1 they seeded. In W21 that ratio dropped to 1.47x, but rug event volume surged to 6,768 – the highest count since Week 13.

This pattern suggests two things happening simultaneously. First, the high-value operators from W20 partially exited or reduced activity after a high-extraction week – consistent with the compression-then-spike-then-compress cycle visible across the full 21-week dataset. Second, a new wave of lower-sophistication operators entered, attracted by the same market sentiment that drove W20’s spike. More actors, running smaller schemes, producing higher event volume but lower total extraction per event.

The 1.47x ratio is still significantly above 1.0x – creators are still removing 47% more than they add. Combined with the highest rug event count in eight weeks, W21 is not a sign of the fraud industry cooling down. It is a sign of it broadening.

RUG PULL DETECTOR V3 – FREE

Check Any Pool Before You Invest – 90.1% Accuracy

Behavioral analysis of contract creators + smart contract code inspection. Handles pools and individual tokens. No signup required. For businesses, subscribe to the API. For AI agents, X402 protocol is enabled.

→ Run a Free Check at chainaware.ai/rugpull

21-Week Running Total: $602.7M

Week 21 pushes the cumulative total past the $600M milestone – $602,689,131 extracted from retail investors on PancakeSwap V2 in 21 weeks of 2026.

The 5-week trailing average (W17-W21) sits at $22.4M – below the 21-week mean of $28.7M, but the rug event count trend is climbing. For the full methodology and the original 20-week dataset that trained Rug Pull Detector V3, see our $569M PancakeSwap V2 analysis.

How to Protect Yourself

With 6,768 rug pull events in a single week, the probability of any random new pool being fraudulent remains extremely high. ChainAware’s free tools screen any pool or token in under two minutes:

• Rug Pull Detector V3 – behavioral analysis of the contract creator + smart contract code inspection. 90.1% prediction accuracy. Free, no signup.
• Fraud Detector – full behavioral history of any deployer wallet. 98% accuracy.
• Wallet Auditor – for P2P transactions. Audit any receiving wallet before sending funds.

NEXT WEEK

Week 22 Data Published Every Monday

ChainAware publishes fresh PancakeSwap V2 rug pull data every week – pool creation, rug events, fraud value, and week-over-week analysis. Follow the archive for every weekly update.

→ Follow the Rug Pull News archive

About This Tracker

The ChainAware Weekly Rug Pull Tracker measures the most basic, mathematically verifiable form of rug pull on PancakeSwap V2: a contract creator adds liquidity (Mint event), retail investors buy in, and the creator removes more than they added (Burn event). The difference is confirmed retail loss. This definition is deliberately conservative – it excludes LP token transfer rug pulls, unlocked token sell-offs, honeypot contracts, and associated wallet extraction. The numbers reported here represent the confirmed floor. For complete methodology, see chainaware.ai/resources/rugpull-verification .

The post $32.4M Extracted in Week 21 – More Rugs, Lower Value Per Rug first appeared on ChainAware.ai.

This is the ChainAware Weekly Rug Pull Tracker – published every week, covering PancakeSwap V2 on BNB Chain. The numbers come from ChainAware’s on-chain analysis: every pool where a contract creator added liquidity and then removed more than they added. The difference is retail money. Gone.

Week-over-Week: The Biggest Single-Week Jump in 20 Weeks

Week 20 stands out sharply against the four weeks that preceded it. After a sustained low-activity period running from Week 16 through Week 19 – where weekly extraction averaged just $15M – Week 20 delivered a 191% spike. This is the largest week-over-week percentage increase in the entire 20-week dataset.

What the W20 Spike Tells Us

Four consecutive low weeks followed by a sharp resurgence is a recognizable pattern in this dataset. It appeared after the W4 peak ($53.4M) when extraction compressed through W8 before partially recovering. It appeared again after W13 when extraction declined through W19 before snapping back in W20.

The compression-then-spike pattern reflects the operational rhythm of professional rug pull operators. Low-sentiment periods reduce retail capital inflows into new pools – making large extractions less profitable. Operators compress their activity, reduce deployment volume, and wait. When market sentiment recovers and retail capital returns to speculative DeFi activity, operators re-accelerate. The W20 spike is not an anomaly. It is the beginning of a new extraction cycle.

Two data points support this reading. First, total pools created jumped from 9,777 in W19 to 10,752 in W20 – a 10% increase in deployment volume alongside the 191% increase in fraud value. Operators deployed more pools AND extracted more per pool simultaneously. Second, the ratio of removed-to-added liquidity widened sharply: W19 was 1.50x (removed/added), W20 was 1.79x. Operators are extracting a higher fraction of the available liquidity per pool – a signal of more aggressive execution.

RUG PULL DETECTOR V3 – FREE

Check Any Pool Before You Invest – 90.1% Accuracy

Behavioral analysis of contract creators + smart contract code inspection. Handles pools and individual tokens. No signup required. For businesses, subscribe to the API. For AI agents, X402 protocol is enabled.

→ Run a Free Check at chainaware.ai/rugpull

20-Week Running Total: $569M and Counting

Week 20 closes the first 20-week measurement period of 2026. The cumulative picture is stark:

The W20 spike pushes the 5-week trailing average (W16-W20) to $20.2M – below the 20-week mean of $28.5M, but trending sharply upward. If the W20 resurgence continues into W21, the trailing average will recover toward the historical mean within two weeks. For the full 20-week methodology and dataset, see our complete $569M PancakeSwap V2 rug pull analysis.

How to Protect Yourself

Every rug pull event in this dataset was preventable. Not by avoiding DeFi – but by checking before investing. ChainAware’s free tools take under two minutes per token:

• Rug Pull Detector V3 – paste any pool address or token contract. V3 runs behavioral analysis of the contract creator AND inspects the smart contract code. 90.1% prediction accuracy. Free, no signup.
• Fraud Detector – paste the deployer wallet address. Checks the full on-chain behavioral history of the person behind the contract. 98% accuracy.
• Wallet Auditor – for P2P transactions. Audit any receiving wallet before sending irreversible funds.

For DApps that need to screen wallets at connection automatically, ChainAware’s Transaction Monitoring Agent deploys via Google Tag Manager in 12 minutes with no code changes – screening every connecting wallet in real time and blocking bad actors before any transaction begins.

NEXT WEEK

Week 21 Data Published Every Monday

ChainAware publishes fresh PancakeSwap V2 rug pull data every week – pool creation, rug events, fraud value, and week-over-week analysis. Bookmark this page or follow ChainAware on X to get each week’s numbers as they drop.

→ Follow ChainAware at chainaware.ai

About This Tracker

The ChainAware Weekly Rug Pull Tracker measures the most basic, mathematically verifiable form of rug pull on PancakeSwap V2: a contract creator adds liquidity (Mint event), retail investors buy in, and the creator removes more than they added (Burn event). The difference is confirmed retail loss.

This definition is deliberately conservative – it excludes more complex extraction methods (LP token transfer rug pulls, unlocked token sell-offs, honeypot contracts, associated wallet extraction). The numbers reported here represent the confirmed floor. Real total losses are higher. For the complete methodology, see chainaware.ai/resources/rugpull-verification .

Coverage will expand to additional DEXes and chains in coming weeks. Follow the Rug Pull News archive for every weekly update.

The post $39.9M Extracted in Week 20 – PancakeSwap V2 Weekly Rug Pull Tracker 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.

FREE TOOL

Check Any Token or Pool Before You Invest

ChainAware Rug Pull Detector V3 analyzes behavioral signals from contract creators and inspects smart contracts before you commit a single dollar. Free to use. No signup required.

→ Run a Free Rug Pull Check at chainaware.ai/rugpull

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.

FRAUD DETECTOR

Is This Wallet Behind Your Token Safe?

ChainAware Fraud Detector analyzes the behavioral history of any wallet address – including token creators – to predict fraudulent intent with 98% accuracy. Check any creator wallet before you buy.

→ Run a Free Fraud Check at chainaware.ai/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.

RUG PULL DETECTOR V3

90.1% Prediction Accuracy – Free to Use

V3 combines behavioral analysis of contract creators with smart contract code inspection. Handles pools and individual tokens. No signup, no fee. For businesses, subscribe to the API. For AI agents, X402 micropayment protocol is enabled.

→ Try Rug Pull Detector V3 Free at chainaware.ai/rugpull

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.

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.

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. For the complete framework of how AI agents are replacing human functions in Web3, our guide to the Web3 agentic economy provides essential context.

WALLET AUDITOR

Audit Any Wallet Before Sending Funds

Before sending irreversible on-chain transactions, verify the receiving wallet. ChainAware Wallet Auditor delivers a complete 9-parameter behavioral profile – experience, risk, intentions, AML status – in seconds. Free, no signup.

→ Audit Any Wallet Free at chainaware.ai/audit

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.

API FOR BUSINESS

Protect Your DApp and Your Users at Scale

Subscribe to the ChainAware Rug Pull Detector API to screen tokens and pools automatically as part of your platform’s risk infrastructure. Combine with Fraud Detector and AML Screener for complete DApp fraud protection. X402 enabled for AI agent integration.

→ Subscribe to the API at chainaware.ai/subscribe

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.

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.

COMPLETE PROTECTION SUITE

Rug Pull Detector + Fraud Detector + Wallet Auditor

All three tools are free to use at chainaware.ai. Cover pool risk, creator fraud risk, and P2P wallet risk in under five minutes per investment decision. Business API and AI agent X402 access available at chainaware.ai/subscribe.

→ Start at chainaware.ai – Free, No Signup

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.

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.

Web3 lost over $3.6 billion to fraud and exploits in the first three quarters of 2025 alone. Remarkably, 57.8% of those losses came not from smart contract bugs but from access-control failures – the humans and systems operating around the code, not the code itself. This pattern reveals the central challenge of Web3 trust in 2026: the attack surface is not one problem. It is five distinct problems, each requiring a fundamentally different solution.

Most teams pick one trust tool and assume they have coverage. They verify identity with KYC and assume that covers fraud risk. They run a smart contract audit and assume that covers rug pull risk. They check a Sybil score and assume that covers behavioral quality. Each assumption is wrong – because each of these tools addresses a different layer of the trust stack. This guide maps the complete five-category Web3 trust verification landscape, explains what each provider actually covers, and shows precisely where ChainAware addresses the attack surfaces that every other category leaves unprotected.

The Five Trust Problems in Web3

Trust in Web3 is not a single dimension – it is a layered stack of five distinct questions that no single provider answers completely. Conflating them leads teams to select the wrong tools, build false confidence in partial coverage, and leave entire attack surfaces unprotected.

• Identity Trust: Is this a real, unique human with verifiable identity?
• Behavioral Trust: Is this wallet genuinely active, non-Sybil, and behaviorally high-quality?
• Social Trust: Does the community vouch for this person’s credibility and track record?
• Token and Protocol Trust: Is this smart contract safe? Is this token’s community genuine, or a manufactured rug pull setup?
• Agent Verification: Is this AI agent wallet – and the wallet funding it – trustworthy before I allow autonomous interaction with my protocol?

Each question requires different data, different methodology, and different tools. Furthermore, passing one trust check says nothing about performance on the others. A wallet can pass KYC, hold a clean Sybil score, have positive Ethos vouches, and still carry a 0.87 fraud probability in ChainAware’s behavioral model – because each layer catches threats that the others are structurally blind to. For how behavioral intelligence layers into the broader Web3 intelligence stack, see our Web3 Wallet Auditing Providers guide.

Category 1: Identity Trust – KYC and Document Verification

Identity trust answers the most foundational question: is this a real, unique person with verifiable government-issued identity? KYC providers verify document authenticity, biometric liveness, sanctions and PEP exposure, and ongoing AML obligations. Their 2026 market data reveals the scale of the problem – Sumsub analyzed over 23,000 fraud attempts daily and found that 55% of crypto firms confirmed experiencing fraud at least once in 2025, while 15% were unsure whether it happened at all.

Sumsub – The Market Leader

Sumsub works with 8 out of 10 top global crypto exchanges and covers the complete verification lifecycle: document verification (14,000+ document types across 220+ countries), biometric face matching, liveness detection, AML/PEP screening, Travel Rule compliance, KYB for businesses, and ongoing transaction monitoring. Their April 2026 State of the Crypto Industry report found that 74% of crypto firms now prioritize verification accuracy over onboarding speed – a structural shift from the growth-at-all-costs approach that dominated 2021-2023. According to Sumsub’s 2026 research , crypto companies are entering a phase where operational discipline matters more than momentum.

Civic Pass – Blockchain-Native KYC

Civic provides blockchain-native KYC through Civic Pass – an on-chain credential issued after off-chain identity verification. Available in 190+ countries, Civic covers liveness checks, document KYC, watchlist and PEP screening, VPN detection, and email and phone verification. The key differentiator is portability: users verify once and reuse their Civic Pass across any integrated DApp without re-submitting documents. This verify-once model significantly reduces onboarding friction while maintaining compliance. Fractal ID offers a similar Web3-native multi-chain identity stack positioned as a lighter-weight alternative for DeFi-native teams.

The Structural Limitation of KYC

Every KYC provider shares one fundamental constraint: they require active user participation. Document uploads, face scans, and liveness checks create friction that reduces conversion and makes KYC unsuitable for fully permissionless DeFi protocols. More critically, KYC verification is a point-in-time snapshot – it confirms who a wallet belonged to at verification date but says nothing about that wallet’s subsequent behavioral risk. A wallet can pass KYC completely and still develop a 0.91 fraud probability the following month based on new behavioral patterns. This gap is precisely where ChainAware’s behavioral layer operates. For how KYC connects to the broader compliance picture, see our Predictive AI for KYC and AML guide and our MiCA Compliance guide.

Free – No Signup Required

Audit Any Wallet in 1 Second – Fraud Score, AML Status, Behavioral Profile

Paste any address and get fraud probability (98% accuracy), AML/OFAC status, experience level, 12 intention probabilities, and Wallet Rank. Free, sub-second, no account needed. ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, SOL.

Audit Any Wallet Free Wallet Auditor Guide

Category 2: Behavioral Trust – On-Chain Reputation and Sybil Resistance

Behavioral trust operates entirely on public on-chain data – no user action required, fully permissionless, privacy-preserving. Providers in this category analyze wallet transaction history to answer whether a wallet is a genuine, active participant or a bot, farmer, or coordinated Sybil attacker. Two distinct methodologies dominate this space.

Trusta Labs / TrustScan – AI/ML Graph Pattern Detection

Trusta Labs applies Graph Neural Networks (GCNs, GATs) and Recurrent Neural Networks (GRUs, LSTMs) to detect four specific Sybil attack signatures in wallet transaction graphs: star-like transfer patterns (hub-and-spoke funding), chain-like transfer patterns (sequential wallet funding), bulk operations (coordinated timing), and similar behavior sequences (identical transaction fingerprints across wallets). Founded by ex-Alipay AI leaders, Trusta has analyzed 570 million wallets and integrated into Gitcoin Passport (1.54 points per verified address) and Galxe. For the complete Sybil protection landscape comparison, see our Web3 Sybil Protection Systems guide.

Nomis, RubyScore, and ReputeX – Activity-Based Reputation

Nomis scores historical activity volume, protocol diversity, wallet age, and cross-chain engagement across 50+ chains – issuing output as a portable on-chain NFT attestation. RubyScore provides a simpler activity quality filter with faster integration, suitable for projects needing lightweight Sybil gating without deep analysis. ReputeX takes a fusion approach combining multiple behavioral paradigms, though production deployment evidence remains limited.

All behavioral trust providers share a critical structural limitation: they are reactive and binary. They describe past behavior and produce pass/fail gates. None predicts future behavior, none scores behavioral quality beyond activity volume, and none provides the downstream deployment layer that converts screened wallets into transacting users. ChainAware closes all three gaps simultaneously. For keeping airdrop and IDO distributions clean from Sybil wallets, see the Sybil-Resistant Token Distribution use case. For the full reputation score comparison including Nomis, Ethos, Cred Protocol, and UTU, see our Web3 Reputation Score Comparison.

Category 3: Social Trust – Community Vouching and Staked Endorsements

Social trust builds reputation through community mechanisms rather than on-chain transaction analysis. Where behavioral trust asks “what has this wallet done?”, social trust asks “what does the community say about this person?” These are orthogonal signals – a wallet can have strong behavioral scores and poor social reputation, or vice versa. Combining both provides significantly more robust trust assessment than either alone.

Ethos Network – Staked Social Proof-of-Trust

Ethos Network launched mainnet on Base in January 2025 and represents the most sophisticated social trust system in Web3. The core mechanism requires users to stake ETH when vouching for others – making trust claims financially consequential rather than costless clicks. Participants can also slash (penalize) others for proven bad behavior, reducing the voucher’s staked amount. Credibility scores derive from the platform’s most engaged and reputable members, creating a peer-weighted system rather than simple vote counting. Ethos.Markets launched alongside the main platform, allowing users to financially speculate on trust scores through an AMM using the LMSR algorithm. Additionally, a Chrome extension shows Ethos credibility scores directly on Twitter/X profiles – bringing social trust verification into ambient browsing. The project raised $1.75M pre-seed from 60 Web3 community angel investors.

The primary limitation of Ethos is coverage: it only scores wallets with established Ethos profiles. Anonymous wallets with no Ethos history return no signal – which describes the vast majority of wallets that connect to any DeFi protocol. Furthermore, Ethos measures social community trust among known participants, not the behavioral quality or fraud risk of a wallet. A highly vouched wallet can still carry significant fraud probability based on its transaction patterns.

Karma3 Labs / OpenRank – Algorithmic Trust Propagation

Karma3 Labs builds ranking and reputation infrastructure using the EigenTrust algorithm – originally designed to improve trust propagation in distributed systems and later applied to Google’s PageRank concept. Their $4.5M seed round came from Galaxy and IDEO CoLab. OpenRank enables developers to build personalized search, discovery, and recommendation systems on top of on-chain social graph data, with notable deployment for Farcaster social graph trust scoring. Where Ethos is community-driven (humans staking on humans), Karma3 is algorithm-driven (EigenTrust computing trust propagation through the social graph). According to Karma3 Labs’ documentation , the OpenRank protocol enables context-aware trust that adapts to different application requirements.

UTU Protocol – Relationship-Context Trust

UTU Protocol builds trust through a non-transferable reputation token (UTT) and staked endorsements, with emphasis on relationship context – a user’s trusted network’s opinions carry more weight than a stranger’s. The UTT cannot be traded, only earned through genuine trust endorsements that later prove correct. Africa DeFi focus and Internet Computer deployment distinguish UTU from the other social trust providers. All three social trust systems – Ethos, Karma3, and UTU – address a genuine trust dimension that on-chain behavioral analysis cannot capture: long-standing human relationships and community standing that extend beyond wallet transaction history.

Category 4: Token and Protocol Trust – Code Audits, Short and Long Rug Pulls

This category covers two entirely different trust problems that are commonly conflated. Smart contract code audits (CertiK, Hacken) verify whether the code is technically safe. Behavioral token trust tools (ChainAware) verify whether the operator behind the code and the community around the token are genuine. CertiK’s H1 2025 Hack3d report recorded $2.47 billion lost across 344 incidents – with wallet compromise the largest category and phishing the most frequent. This confirms that the most expensive 2026 threats live around the code, not inside it. Yet most teams invest entirely in code audits while ignoring behavioral token trust.

CertiK and Hacken – Smart Contract Code Audits

CertiK is the dominant smart contract audit and security monitoring platform with 5,000+ enterprise clients, $600B+ in assets secured, and 180,000+ vulnerabilities identified. Its Skynet platform delivers real-time on-chain incident monitoring and alerting. The Spoq formal verification engine uses AI-driven automation to mathematically prove system correctness – validated at peer-reviewed venues OSDI 2023 and ASPLOS 2026. According to CertiK’s platform documentation , Skynet Enterprise meets the transparency and risk visibility requirements of institutional participants and regulators. Hacken provides security audits and a TRUST Score framework evaluating protocols across transparency, security, code quality, and community metrics – their 2025 TRUST Report tracked $3.6B stolen, with 57.8% from access-control exploits.

Both CertiK and Hacken audit code at a specific point in time. Neither analyzes the behavioral history of the wallet that deployed the contract, the fraud profile of the wallets that provided liquidity, or the quality of the token’s holder community. These are not limitations of the audit providers – they are simply a different layer of the trust stack. The critical mistake is treating a clean CertiK audit as comprehensive protection when 95% of PancakeSwap pools end in rug pulls and 99% of Pump.fun tokens extract money from buyers – most of them with no code vulnerabilities whatsoever. For the complete rug pull detection landscape, see our Rug Pull Detection guide.

ChainAware Rug Pull Detector – Short Rug Pull Detection via Creator Chain Traversal

ChainAware’s Rug Pull Detector (see the complete Rug Pull Detector guide) addresses the behavioral layer that code audits structurally cannot reach. The core insight: experienced rug pullers deliberately pass code reviews. Their malicious intent is not in the contract – it is in the wallet that deployed it, the wallets that provided liquidity, and the behavioral history that accumulates before the exploit.

The methodology uses creator chain traversal – a recursive process that climbs the deployment chain until it finds the terminal human-controlled wallet:

Token Contract
  └── contractCreatorAddress
         ├── If human wallet → score with predictive_fraud (98% accuracy)
         └── If contract (factory / proxy / deployer)
                  └── creator of THAT contract
                         ├── If human wallet → score with predictive_fraud
                         └── If contract → continue traversal...
                                  └── ... until terminal human wallet found

Sophisticated rug pull operators use deployment layers – factory contracts, proxy deployers, script contracts – specifically to sever the visible link between their personal wallet history and the new token. A naive rug pull checker that looks only one level up the creator chain sees a clean contract address and reports Low Risk. ChainAware’s traversal climbs through every layer until it finds the human operator, then scores their full behavioral fraud history across 19 forensic categories.

The “New Wallet” Risk Signal

When traversal terminates at a wallet created days or weeks before the token deployment, this carries elevated risk even without active fraud indicators. Legitimate protocol developers operate from established wallets with meaningful DeFi history. A new wallet at the chain terminus scores “New Address” rather than “Not Fraud” – and that distinction matters because it means the operator deliberately created a fresh wallet to avoid being traced from prior exploits. No prior fraud record is itself the red flag when combined with brand-new wallet age and a token launch event.

Liquidity Provider Fraud Scoring – The Second Dimension

Beyond creator analysis, the Rug Pull Detector independently scores every liquidity event. The `liquidityEvent` array returns every add/remove liquidity transaction with the `from_address` scored for fraud probability. Consequently, this catches the pattern where a clean creator wallet deploys the token but mixer outputs or darknet-linked wallets provide the liquidity – making those wallets the actual economic actors who will drain the pool. Creator analysis and liquidity provider scoring together cover the behavioral attack surface that 20+ code-level risk indicators alone miss. The overall tool achieves 68% detection accuracy before pool collapse – a dynamic prediction that updates as new behavioral data arrives. For how this fits the complete token analysis workflow, see our Fake Token Identification guide.

ChainAware Token Rank – Long Rug Pull Detection via Community Quality Scoring

Short rug pulls drain liquidity and disappear quickly. Long rug pulls unfold differently – the team builds apparent traction over months or years through manufactured social followers, inflated trading volume, and partnership announcements, while the actual holder base consists predominantly of bots, farm wallets, low-quality airdrop farmers, and coordinated Sybil wallets. When the team exits, price collapses because genuine community never existed. The fraud was in the community quality, not the code – and therefore invisible to any audit.

Token Rank detects long rug pulls by computing the median Wallet Rank across every meaningful token holder. Lower median Wallet Rank means higher holder quality. A token with 50,000 holders but a median Wallet Rank dominated by near-zero scores – new, inactive, single-chain wallets – has a manufactured community. A token with 5,000 holders and a median Wallet Rank of 2-3 has a genuinely high-quality community of experienced DeFi participants who chose to hold. Token Rank covers 2,500+ tokens across Ethereum, BNB Smart Chain, and other networks, exposing `communityRank`, `normalizedRank`, `totalHolders`, and the `topHolders` list with individual wallet profiles. No code audit, no tokenomics review, and no social metric reveals this – because it requires behavioral analysis of every individual holder. Token Rank is therefore the only tool that catches long rug pulls before they execute. See the Wallet Rank learn guide for how the underlying scoring methodology works, and the complete methodology in our Wallet Rank guide.

68% Detection Accuracy Before Pool Collapse

ChainAware Rug Pull Detector + Token Rank – Catch What Code Audits Miss

Creator chain traversal to the terminal human wallet. Liquidity provider fraud scoring. Community quality analysis across all holders. Short rug pulls and long rug pulls – both detected before you lose capital. Free for individual checks. MCP-native for AI agents.

Check Any Token Free Rug Pull Detection Guide

Category 5: Agent Verification – Why Voting Fails and Creator Chain Works

AI agents now execute DeFi strategies, manage DAO treasuries, run compliance pipelines, and interact with protocols autonomously – with significant capital and without any human in the loop. Worldchain noted that by some estimates 80% of blockchain transactions are already automated. As the Web3 agentic economy scales from thousands to millions of autonomous agent wallets, verifying the trustworthiness of those agents before granting them protocol access has become a critical infrastructure requirement. Every other trust category was designed for human wallets. None addresses the specific challenge of agent wallet verification. For the broader context of how AI agents are reshaping Web3 operations, see the ChainAware For AI Agents overview, our Web3 Agentic Economy guide and our 12 Blockchain Capabilities for AI Agents guide.

Why ERC-8004 and Voting-Based Agent Trust Fails

ERC-8004 and similar proposals attempt to build agent trust through on-chain reputation voting – agents vouch for each other, accumulate endorsements, and build scores based on peer consensus. The mechanism borrows from social trust systems like Ethos Network. However, it fails structurally when applied to agents rather than humans.

The manipulation attack is trivial and undetectable. A malicious operator deploys 50 agent wallets at near-zero cost. Each one votes up every other wallet in the cluster. Within days, all 50 accumulate high trust scores with zero genuine behavioral history. They then simultaneously vote down legitimate competing agents to suppress rival scores. The entire trust signal is manufactured – there is no Sybil resistance at the voting layer, no requirement for prior behavioral history, and no economic cost sufficient to deter a well-funded operator.

The deeper structural problem: AI agents have no social friction. When Ethos Network requires staked ETH behind a vouch, a human who vouches fraudulently loses money and social standing. An AI agent operator who creates 50 voting wallets and cross-vouches loses nothing – the wallets are free, the stake can be minimal, and the cluster rotates after each manipulation cycle. Voting-based agent trust is therefore not just gameable; it is machine-speed gameable by the very entities it is supposed to screen.

The Correct Approach: Creator Chain Traversal + Feeder Wallet Analysis

Agent trust does not require voting. It requires exactly the same methodology as short rug pull detection – creator chain traversal to the terminal human wallet, combined with independent feeder wallet analysis. The logic is identical:

Agent Wallet
  └── Who deployed this agent's controlling contract?
         ├── If human wallet → score with predictive_fraud
         └── If contract (factory / multi-sig / deployer)
                  └── creator of THAT contract
                         ├── If human wallet → score with predictive_fraud
                         └── If contract → continue traversal...

Feeder Wallet (who funds this agent's operations)
  └── Score independently with predictive_fraud
  └── Check: mixer interactions, darkweb, money_laundering,
             phishing, stealing_attack, sanctioned, 14 other forensic categories

This approach is manipulation-proof for a fundamental reason: blockchain history is immutable. A malicious operator cannot retroactively clean their terminal human wallet’s record of honeypot deployments, mixer interactions, or fraud associations. They cannot make a 6-day-old feeder wallet appear to have 3 years of legitimate DeFi history. They cannot remove the `honeypot_related_address` flag from a wallet that previously funded exit scams. The historical record makes creator chain analysis structurally Sybil-resistant in a way that no voting mechanism – regardless of its design – can achieve.

The Feeder Wallet – The Most Important Agent Trust Signal

Feeder wallet analysis is particularly critical because it catches the attack pattern that creator chain analysis alone misses. A sophisticated operator creates a clean deployment wallet specifically for the agent – passing creator chain analysis – while funding operations from a compromised wallet that reveals their actual risk profile. Both checks are necessary. Together they close the attack surface that any single-wallet screening approach leaves open.

ChainAware chainaware-agent-screener – The Only Agent Verification Tool

The `chainaware-agent-screener` (see Security & Fraud Agents) is the only purpose-built AI agent trust verification tool in the Web3 market. It screens both the agent wallet and the feeder wallet simultaneously, producing an Agent Trust Score from 0 to 10 (0 = confirmed fraud, 1 = new/insufficient data, 2-10 = normalized reputation). The agent uses both `predictive_fraud` and `predictive_behaviour` MCP tools and deploys via git clone and an API key – no custom engineering required.

Example output for a high-risk agent (from live documentation):

AGENT SCREENING
Agent Wallet: 0xSuspectAgent... | Network: Base
Feeder Wallet: 0xFundingSource... | Network: Base

Agent Trust Score: 2.1 / 10 ⚠

Agent Wallet:
  Fraud verdict: Elevated risk (0.52)
  On-chain age: 6 days ⚠
  Behaviour: Unusual - rapid fund movement, no prior agent pattern

Feeder Wallet:
  Fraud verdict: HIGH RISK (0.81) 🛑
  AML flags: Mixer interaction (Tornado Cash equivalent)
  Connected to 2 confirmed exit scams

→ 🛑 Do not allow. Feeder wallet has confirmed fraud indicators.
  Block and report to your security team.

The agent handles natural language prompts: “Is this agent wallet safe? 0xAgent… on Ethereum”, “Screen these 5 AI agents before we allow them into our protocol: [list of agent+feeder pairs]”, or “Can I trust this agent? It wants to execute trades on my behalf.” The growing adoption of multi-agent frameworks including ElizaOS, Fetch.ai, and Coinbase AgentKit makes this verification capability increasingly critical – every protocol integrating third-party agent infrastructure now requires a trust layer to screen those agents before granting access. For the complete AI agent capability reference, see our AI Agents for Web3 roadmap and our Blockchain Data Providers guide.

32 MIT-Licensed Open-Source Agents – Deploy in Minutes

Agent Screener · Governance Screener · Fraud Detector · AML Scorer – All via git clone

Screen AI agent wallets and feeder wallets before granting protocol access. Manipulation-proof via creator chain traversal – not gameable by voting clusters. Works with Claude, GPT, and any MCP-compatible LLM. No custom build required. See the full Ready-Made Agents catalogue.

View Agents on GitHub Prediction MCP Guide

ChainAware’s Unique Position Across All Five Categories

Having mapped all five categories, ChainAware’s competitive position becomes precise. Across the five trust problems, ChainAware plays a distinct role in each – complementary in some, competing and extending in others, and uniquely positioned as sole provider in two.

Category 1 (Identity Trust) – Complementary

KYC providers verify identity at a point in time. ChainAware adds ongoing behavioral fraud prediction that operates continuously after verification – catching wallets whose risk profile changes after KYC completion. Additionally, ChainAware’s permissionless approach covers the DeFi protocols that KYC is unsuitable for entirely, providing behavioral trust coverage without requiring user participation. The two layers are additive: KYC for regulatory compliance, ChainAware for continuous behavioral risk monitoring.

Category 2 (Behavioral Trust) – Competing and Extending

ChainAware operates in the same on-chain, permissionless, privacy-preserving space as Trusta, Nomis, and RubyScore – but answers fundamentally richer questions. Trusta detects coordination graph patterns. Nomis scores activity volume. ChainAware adds 22-dimension behavioral profiles, 12 forward-looking intention probabilities, 19-category forensic fraud analysis, AML/OFAC screening, governance tier classification, and 32 deployable agents. Furthermore, ChainAware is the only provider with a growth deployment layer – converting screened traffic into transacting users rather than just producing eligibility scores. For the full behavioral intelligence comparison, see our Web3 Analytics Tools Comparison.

Category 3 (Social Trust) – Complementary

Ethos, Karma3, and UTU measure what the community says about known participants. ChainAware measures what blockchain history predicts about any wallet’s future behavior. These signals are orthogonal: a highly vouched wallet can have high fraud probability, and a wallet with zero Ethos profile can have excellent behavioral quality scores. Both signals together provide more robust trust assessment than either alone. The practical combination: Ethos credibility scores for known community participants with established social standing, ChainAware behavioral intelligence for every wallet regardless of social profile.

Category 4 (Token and Protocol Trust) – Partially Competing

CertiK and Hacken own the code audit layer – ChainAware does not compete with smart contract formal verification. However, ChainAware owns the behavioral token trust layer that code audits structurally cannot reach. Rug Pull Detector (creator chain traversal + liquidity provider fraud scoring = short rug pull detection) and Token Rank (median Wallet Rank across all holders = long rug pull detection) address attack surfaces where CertiK and Hacken have no tools. A complete protocol trust stack requires both: CertiK/Hacken for code safety and ChainAware for behavioral token trust.

Category 5 (Agent Verification) – Sole Provider

No other provider has built agent wallet trust verification. ERC-8004 and voting-based proposals are manipulable at machine speed. Creator chain traversal with feeder wallet analysis – the methodology ChainAware applies through `chainaware-agent-screener` – is the only manipulation-proof approach, and ChainAware is the only provider that has implemented it. As the agentic economy scales, this category will grow from a niche capability to foundational infrastructure – and ChainAware currently has no competition in it.

The Recommended Trust Stack for 2026

No single provider covers all five trust dimensions. Consequently, the most sophisticated protocols in 2026 layer multiple tools addressing different attack surfaces. The following combinations map to the most common protocol types.

Regulated VASPs and Centralized Exchanges

Sumsub for document KYC, Travel Rule, and KYB compliance (mandatory regulatory layer) + ChainAware for ongoing behavioral fraud prediction and transaction monitoring (continuous behavioral layer) + CertiK audit for any smart contracts in the stack (code layer). Together these cover all five trust dimensions except social trust, which becomes relevant for DAO-adjacent products.

Permissionless DeFi Protocols

CertiK or Hacken for pre-launch smart contract audit (code layer) + ChainAware Rug Pull Detector pre-launch screening of the deployer wallet and liquidity setup (behavioral token trust) + Trusta or Nomis for airdrop Sybil filtering (campaign gate) + ChainAware Wallet Rank and fraud probability at wallet connection (quality and safety gate) + ChainAware Growth Agents to convert screened wallets into transacting users (deployment layer). For the complete DeFi compliance framework, see our DeFi Compliance Tools guide.

DAOs with Treasury and Governance

ChainAware `chainaware-governance-screener` before every governance vote (behavioral Sybil detection + tier classification + voting weight multipliers – the only tool that does this) + Ethos credibility scores for known community members (social layer) + Hacken TRUST Score for ongoing protocol security assessment. Additionally, ChainAware Token Rank continuously monitors holder community quality – detecting whether a coordinated low-quality holder base is accumulating governance tokens for a long-term governance attack. For the governance attack surface in depth, see our Governance Screeners guide.

Protocols Integrating Third-Party AI Agents

ChainAware `chainaware-agent-screener` for every third-party agent requesting protocol access – screening both the agent wallet and feeder wallet before granting any permissions + `chainaware-transaction-monitor` for ongoing real-time scoring of every agent transaction (ALLOW / FLAG / HOLD / BLOCK pipeline action) + ChainAware fraud detector for the agent operator wallet if known. This creates a complete agent trust perimeter: pre-access screening, real-time transaction monitoring, and operator background verification. For how AI agents integrate with Web3 protocols at scale, see our Real AI Use Cases for Web3 guide.

Token Investors and Pre-Investment Due Diligence

ChainAware Rug Pull Detector on the token contract (creator chain traversal + LP fraud scoring = short rug pull risk) + ChainAware Token Rank on the token’s holder community (median Wallet Rank = long rug pull risk) + CertiK or Hacken audit status (code risk) together provide a three-dimensional token trust assessment that no single tool delivers alone. For how to identify fake tokens using these signals, see our Fake Token Identification guide.

ChainAware.ai – Behavioral Intelligence Across All Five Trust Layers

One Platform. Five Trust Dimensions. 32 Ready-Made Agents.

Free Wallet Auditor · Rug Pull Detector · Token Rank · Governance Screener · Agent Screener · Prediction MCP · Growth Agents. No annual contract. No procurement cycle. Active in minutes.

Free Wallet Audit Prediction MCP View Pricing

Frequently Asked Questions

What is the difference between KYC trust and behavioral trust?

KYC trust verifies that a wallet belongs to a real, identifiable person with verified government documents at a specific point in time. Behavioral trust analyzes what that wallet has done on-chain to predict future fraud risk and behavioral quality. Both are necessary because a wallet can pass KYC and subsequently develop high fraud probability, and a wallet can have strong behavioral quality scores without any KYC verification. The two layers address different attack surfaces: KYC for regulatory compliance and identity certainty, behavioral trust for ongoing fraud risk and quality assessment.

Can a smart contract audit replace rug pull detection?

No – and this is one of the most dangerous misconceptions in Web3 security. Smart contract audits verify code correctness at audit time. Rug pull detection verifies the behavioral risk of the human operator behind the code. Experienced rug pullers deliberately write clean, auditable code – their malicious intent is in their wallet’s history, not the contract. The creator chain traversal approach catches this by climbing through every deployment layer to find the terminal human wallet and score their full behavioral fraud history. A clean CertiK audit combined with a high-risk creator wallet is a warning sign, not a green light. Running both checks is the complete picture.

What is a long rug pull and how does Token Rank detect it?

A long rug pull unfolds over months or years. The team builds apparent community through manufactured holder counts, inflated trading volume, and partnership announcements – while the actual holder base consists of bots, farm wallets, and coordinated Sybil wallets with no genuine community intent. When they exit, the price collapses because no real community existed to support it. Token Rank detects this by computing the median Wallet Rank across all meaningful holders. A high holder count combined with near-zero median Wallet Rank scores – dominated by new, inactive, single-chain wallets – signals a manufactured community before the collapse. No code audit, tokenomics review, or social metric catches this because it requires behavioral analysis of the individual holder base, not the contract.

Why is ERC-8004 voting-based agent trust inadequate?

ERC-8004 and similar proposals are trivially manipulable because AI agents have no social friction or economic consequences for false vouching. A malicious operator deploys a cluster of 50 agent wallets at near-zero cost, cross-vouches them to inflate trust scores, and simultaneously downvotes legitimate competitors – all at machine speed. The manipulation cannot be distinguished from genuine vouching because agents produce no social record, no real-world identity damage, and no economic loss when participating in a trust manipulation scheme. Creator chain traversal with feeder wallet analysis solves this problem structurally – blockchain history is immutable, making it impossible to retroactively clean a terminal human wallet’s record of prior exploits, mixer usage, or fraud associations.

What does ChainAware provide that Ethos Network does not?

Ethos Network measures social community trust among known participants with established Ethos profiles. ChainAware measures behavioral intelligence for any wallet regardless of social profile. Practically, Ethos cannot screen anonymous wallets with no Ethos history – which describes most wallets connecting to any DeFi protocol. Furthermore, Ethos does not predict future behavior, does not provide AML/OFAC screening, does not detect token rug pull risk, and does not screen AI agent wallets. The two systems address orthogonal trust dimensions: Ethos for social standing among known community participants, ChainAware for behavioral risk assessment of any on-chain address.

How does ChainAware’s credit score relate to trust verification?

ChainAware’s credit score (1-9 trust score derived from AI analysis of on-chain inflows, outflows, fraud indicators, and social graph data) addresses financial trustworthiness specifically – answering whether a counterparty can be trusted to repay in undercollateralized lending contexts. This is a trust verification use case that no KYC provider, no Sybil detection tool, and no social trust platform addresses. KYC verifies identity but not creditworthiness. Behavioral reputation scores activity quality but not repayment reliability. ChainAware’s credit score is therefore a sixth trust dimension specifically relevant to DeFi lending protocols seeking to move beyond overcollateralized models. For the complete methodology, see our Web3 Credit Scoring guide.

What is the minimum setup to get meaningful trust coverage?

For most DeFi protocols, meaningful coverage starts with two free tools requiring zero engineering: the ChainAware Wallet Auditor for individual high-stakes wallet checks, and the Rug Pull Detector for any token or liquidity pool before depositing. Adding the free Web3 Behavioral Analytics pixel via Google Tag Manager provides population-level quality assessment of every wallet connecting to your DApp – revealing experience distribution, fraud rate, and intention profiles without any engineering sprint. For protocols needing automated coverage, the Prediction MCP connects any AI agent or LLM to all six intelligence dimensions in a single natural language tool call. For the complete integration reference, see our ChainAware Complete Product Guide.

External sources: Sumsub 2026 State of Crypto Industry Report · CertiK Platform Documentation · Karma3 Labs / OpenRank · Ethos Network · ChainAware Behavioral Prediction MCP – GitHub

The post Web3 Trust Verification Systems in 2026 – The Complete Five-Category Landscape first appeared on ChainAware.ai.

Every wallet address that connects to your DApp carries a complete behavioral history. Behind that 42-character hexadecimal string sits a real person – with specific intentions, a measurable experience level, a risk appetite, and a predicted next action. Most Web3 platforms never access any of that information. Instead, they treat every connecting wallet identically and wonder why 90% of them never transact.

In 2026, a mature ecosystem of wallet auditing providers has emerged to solve this problem – but they solve it in fundamentally different ways. Some deliver raw blockchain data. Others deliver structured behavioral profiles. Only one delivers forward-looking predictions that DApps and AI agents can act on directly. Understanding the difference between these approaches is the most important infrastructure decision any Web3 team makes in 2026.

The Three-Layer Wallet Auditing Framework

Wallet auditing is not a single product category – it is a stack of three distinct capabilities, each answering a fundamentally different question. Confusing these layers leads to selecting the wrong tools, building the wrong integrations, and producing outputs that require far more analytical work than the team anticipated.

The three layers are best understood through the question each one answers:

• Layer 1 – Blockchain Data Infrastructure: “What transactions occurred on-chain?”
• Layer 2 – Descriptive Aggregation: “Who is this wallet, based on what it has done?”
• Layer 3 – Actionable Intelligence: “What will this wallet do next – and what should I do about it?”

Most Web3 teams today use Layer 1 and Layer 2 tools and assume they have a complete wallet auditing solution. They do not. Layer 1 gives raw materials. Layer 2 structures those materials into readable profiles. Neither layer tells a DApp, a compliance system, or an AI agent what decision to make. That translation still requires significant human analytical work – or a custom ML pipeline that most teams lack the resources to build. Layer 3 closes that gap by producing outputs that are directly actionable: predictions, instructions, and decisions rather than data and reports. For the broader context of why intention-based intelligence outperforms descriptive analytics in Web3, see our Intention Analytics vs Descriptive Token Data guide.

Layer 1: Blockchain Data Infrastructure

Layer 1 providers give developers structured access to raw on-chain data – transaction histories, token balances, smart contract events, NFT ownership, and DeFi positions. They serve as the foundational infrastructure that all higher-layer analysis builds upon. Without Layer 1, no wallet analysis is possible. Consequently, these providers are essential – but they are infrastructure, not intelligence. Their outputs require significant interpretation before they produce anything a DApp can act on.

Key Layer 1 Providers

Alchemy is the enterprise-grade choice – a Series C-backed infrastructure platform used by OpenSea, Trust Wallet, and Dapper Labs. Its enhanced APIs go beyond standard RPC: the NFT API returns complete metadata and ownership history in a single call, the Notify API delivers webhooks for wallet activity across Ethereum and EVM L2s, and the Trace API provides deep transaction-level smart contract interaction analysis. For teams building production AI agents that need 99.9%+ uptime and sub-100ms latency, Alchemy is the strongest infrastructure foundation available.

Moralis takes the most AI agent-friendly approach at Layer 1 – publishing an official ElizaOS plugin, a full MCP server, and positioning explicitly around agent use cases. Its Wallet API returns native token balance, ERC-20 holdings, NFTs, transaction history, and computed portfolio P&L in a single cross-chain call across 30+ networks. Real-time WebSocket streams push parsed contract events to agent webhooks without manual polling. For developers building on ElizaOS or needing the broadest chain coverage at Layer 1, Moralis is the natural choice. For the full Layer 1 provider comparison, see our Blockchain Data Providers guide.

The Graph provides decentralized, permissionless indexing via protocol-specific subgraphs – custom data schemas that define which on-chain events to index and how to structure them for efficient GraphQL queries. For agents built on specific DeFi protocols (Aave, Uniswap, Compound), The Graph’s protocol-native subgraphs are significantly more efficient than general-purpose RPC calls. According to The Graph’s developer documentation , thousands of subgraphs cover the most important DeFi protocols on EVM chains.

Dune Analytics launched an MCP server in 2025 – enabling AI agents to query 100+ chain datasets conversationally. A natural language prompt like “Top 10 wallets accumulating RWA tokens in the last 30 days” returns structured analytical results without requiring custom SQL expertise. Chain coverage includes Ethereum, Solana, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche, NEAR, zkSync, TON, TRON, Sui, Aptos, and more. Covalent rounds out the Layer 1 landscape with its standardized Block Specimen model – a unified API format across multiple chains that prioritises historical data consistency for compliance and auditing use cases.

What Layer 1 gives you: Transaction hashes, token amounts, contract addresses, timestamps, decoded event logs. The data is accurate and complete. However, it requires your team to build the analytical layer that converts it into something a DApp or AI agent can act on.

Skip Straight to Layer 3 – Free

ChainAware Wallet Auditor – Full Web3 Persona for Any Address in 1 Second

No raw data. No descriptive reports to interpret. Paste any wallet address and get the complete actionable profile – fraud probability (98% accuracy), experience level, all 12 intention probabilities, risk willingness, AML status, Wallet Rank. Pre-computed, sub-second, free. ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ. See the full Wallet Auditor documentation.

Audit Any Wallet Free Wallet Auditor Guide

Layer 2: Descriptive Aggregation Providers

Layer 2 providers take raw blockchain data and aggregate it into structured, human-readable profiles. They answer the question “who is this wallet, based on what it has done?” – producing outputs like reputation scores, activity metrics, entity labels, governance histories, and compliance reports. Layer 2 is where most of the wallet auditing market currently operates. These tools are significantly more useful than raw Layer 1 data, but they share a fundamental limitation: they describe the past without prescribing action for the future.

Reputation and Sybil Prevention Providers

Nomis is the broadest reputation scoring platform by chain coverage – supporting 50+ chains with 30+ on-chain parameters including activity volume, protocol diversity, wallet age, and cross-chain engagement. DApp teams use Nomis primarily for airdrop eligibility gating: setting minimum score thresholds that filter out bot wallets and airdrop farmers while rewarding genuine community participants. The score is issued as an on-chain NFT attestation, giving it portability across protocols. Nomis’s limitation is that it measures activity volume rather than behavioral quality – a wallet can have a high Nomis score through consistent but low-value activity, without that score indicating any specific future intention.

Trusta Labs / TrustScan focuses specifically on Sybil prevention and Proof of Humanity attestations, built by ex-Alipay AI and security experts. The platform uses graph neural networks and recurrent neural networks to analyze asset transfer graphs for coordinated wallet behavior – detecting the starlike funding networks, bulk operation patterns, and similar behavior sequences that characterize Sybil attacks. Its MEDIA score adds five dimensions (Monetary, Engagement, Diversity, Identity, Age) beyond the pure Sybil risk score. Trusta has processed 570 million wallets across EVM and TON chains, integrated with Galxe, Gitcoin Passport, and Binance, and is the top Proof of Humanity provider on Linea and BSC. Notably, Trusta’s headline “3M users” figure refers primarily to wallets processed through airdrop campaigns on behalf of partner protocols like Celestia, Starknet, and Manta – the monthly active user figure is approximately 200K. For teams running airdrops or building on Linea/BSC, Trusta provides the strongest Sybil detection available.

RubyScore and Spectral Finance serve narrower versions of the Layer 2 reputation use case. RubyScore scores wallet activity quality as a simple proxy for genuine engagement – useful for protocol gating but limited in depth. Spectral’s MACRO Score focuses specifically on DeFi credit assessment – evaluating borrower reliability for undercollateralized lending use cases based on historical repayment patterns and collateral behavior. Neither provides fraud prediction, behavioral intentions, or growth deployment.

Intelligence and Analytics Providers

Nansen occupies the most sophisticated position at Layer 2 – providing labeled blockchain data through its Smart Money identification system. Rather than returning anonymous transaction histories, Nansen identifies which wallets belong to recognized entities (funds, exchanges, known DeFi protocols, sophisticated traders) and labels their activity accordingly. Smart Alerts notify analysts when tracked smart money wallets execute significant moves. For investment intelligence and institutional risk management, Nansen is the strongest Layer 2 option – its entity labeling reduces the anonymous-address problem for a meaningful portion of high-value wallet activity. See our Blockchain Data Providers guide for how Nansen fits into a complete AI agent data stack.

DeepDAO provides governance-specific wallet reputation – tracking 11 million participant profiles across 2,500+ DAOs, with complete voting histories, proposal creation records, and cross-DAO engagement patterns. For DAO security screening and delegate verification, DeepDAO provides the most comprehensive governance-specific behavioral history available. For how DAO governance screening complements wallet behavioral intelligence, see our Governance Screeners guide.

Forensic and Compliance Providers

Chainalysis is the dominant forensic intelligence platform – built originally for law enforcement agencies (FBI, DEA, IRS) and government investigators tracking illicit fund flows. Its Know Your Transaction (KYT) product handles VASP compliance screening, and its investigation tools reconstruct transaction graphs across chains for evidence-grade analysis. CertiK’s year-end Hack3D report tallied $3.35 billion in losses across 630 security incidents in 2025, reinforcing the scale of the compliance problem Chainalysis addresses. Enterprise pricing ranges from $100,000 to $500,000 annually – designed for exchanges and institutional operators, not DeFi protocols or individual developers. According to Chainalysis’s platform documentation , its clustering heuristics and entity attribution cover hundreds of major counterparties across multiple blockchains.

TRM Labs and Elliptic serve similar VASP compliance use cases with different geographic and institutional focuses. Nominis positions itself explicitly as an alternative to these three for VASPs – combining on-chain data, off-chain intelligence, and behavioral analytics at significantly lower cost, with a specialised terror-financing database. All four forensic providers share the same fundamental architecture: they trace where funds have come from, not where they are going next. For the complete MiCA compliance cost comparison between Chainalysis and ChainAware, see our MiCA Compliance at 1% of Chainalysis Cost guide.

The Fundamental Limitation of Layer 2

Layer 2 providers are genuinely valuable – they eliminate the data parsing problem and provide structured profiles that human analysts can read and interpret. However, they share a structural limitation that no amount of feature development within Layer 2 can solve: they are backward-looking by design.

The Report-to-Action Gap

Consider what a Layer 2 output actually looks like for a real wallet – defidad.eth, a well-known DeFi educator and content creator whose wallet we analyzed via ChainAware’s Prediction MCP:

Layer 1 output (raw): 3,188 transactions, wallet age 2,147 days, MakerDAO: 84 interactions, Uniswap: 46, Curve: 46, OpenSea: 75, SuperRare: 26…

Layer 2 output (descriptive): Experienced DeFi user. Heavy DEX trader (178 DEX transactions). Active in Lending (94 transactions). NFT collector (102 transactions). Sybil risk: Low. Active since 2018. Top protocols: MakerDAO, Uniswap, Curve.

Both outputs are accurate. Neither tells a DApp what to do when this wallet connects. The Layer 2 output is significantly more readable than Layer 1 – but a compliance team still has to decide whether to allow or flag this wallet. A DApp product manager still has to decide which content to serve. An AI agent still has to figure out what the behavioral history means for the next interaction. That analytical work – translating description into prescription – is precisely what most DApp teams, compliance officers, and AI agents lack the capacity to perform at scale in the 200-millisecond window between wallet connection and first screen render.

Furthermore, descriptive output ages. A Layer 2 profile describes what a wallet did up to the moment of the last data refresh. It does not account for behavioral drift, changing market conditions, or the specific context of the current interaction. The most experienced DeFi user in your database might be exploring your platform for the first time – and their historical transaction count tells you nothing about whether they will convert on this visit if you show them the wrong content. For the deeper argument about why intention data outperforms descriptive transaction data for growth use cases, see our Intention Analytics guide and our Generative vs Predictive AI guide.

Layer 3: Actionable Intelligence – The Web3 Persona

Layer 3 takes the descriptive history produced at Layer 2 and transforms it into forward-looking behavioral predictions that any system can act on directly – without further interpretation, without a custom ML pipeline, and without human analytical overhead. This is where ChainAware operates. Currently, it is the only provider that has built a complete Layer 3 product stack.

What Layer 3 Output Looks Like

Continuing with the defidad.eth example – here is what ChainAware’s Layer 3 Web3 Persona produces from the same wallet data:

Layer 3 output (ChainAware Web3 Persona – actionable):

• Fraud probability: 0.055 → Action: Allow – proceed with onboarding
• Experience: 10/10 → Action: Show advanced UI, skip all beginner tutorials
• Lend intention: High → Action: Surface lending products first in hero section
• Trade intention: High → Action: Show DEX aggregator CTA prominently
• NFT intention: Medium → Action: Feature NFT-collateral borrowing options
• Gamble + all Leverage: Low → Action: Do not surface high-risk products
• Risk willingness: 3/10 → Action: Default to conservative risk parameters
• AML: Clear → Action: Proceed without compliance hold
• Recommendation: Stablecoin lending, ETH holding → Action: Serve these CTAs in priority order

The DApp, compliance system, or AI agent receives instructions – not data to analyze. The 200-millisecond window between wallet connection and first screen render is sufficient for the full persona to be queried via the Prediction MCP and the UI to be personalised accordingly. No human analyst. No custom ML pipeline. No interpretation required.

The 22 Dimensions of a Web3 Persona

ChainAware calculates 22 dimensions for every wallet address across 8 supported blockchains (ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, SOL). These dimensions split into three groups: behavioral predictions, identity profile, and compliance screening.

Behavioral predictions – the 12 intention categories (High / Medium / Low): Borrow, Lend, Trade, Gamble, NFT, Stake ETH, Stake Yield Farm, Leveraged Staking, Leveraged Staking ETH, Leveraged Lending, Leveraged Long ETH, Leveraged Long Game. These are ML predictions trained on 18M+ behavioral profiles – not simple transaction counts. A wallet with 50 Uniswap transactions does not automatically have a High Trade intention if those transactions were all simple USDC-to-ETH swaps from six months ago. The model weighs recency, volume, complexity, and behavioral consistency to produce a probability that reflects likely future action.

Identity profile dimensions: Experience level, Willingness to take risk, Categories used, Protocols used, Wallet Rank, Wallet Age, Transaction Numbers, Balance. Together, these describe the capability and character of the wallet owner – not just what they did, but who they are as a Web3 participant.

Compliance dimensions: Predicted Fraud Probability (98% accuracy, backtested on CryptoScamDB), AML attributes, OFAC status, Sanctions flags. For the complete Web3 Persona dimension reference, see our Web3 Personas guide. For how compliance dimensions specifically support MiCA requirements, see our Blockchain Compliance guide.

Layer 3 for Your Entire User Base – Free

ChainAware Web3 User Analytics – Persona Distribution of Your DApp in 24 Hours

Add 2 lines of Google Tag Manager code. Within 24 hours, see the complete Web3 Persona distribution of every wallet connecting to your DApp – experience levels, intention segments, risk profiles, fraud flags. Understand who is actually showing up before deciding how to talk to them. Free forever. No engineering resources required. See the full DeFi Business Analytics guide.

Get Free Analytics Analytics Guide

ChainAware’s Unique Position in the Stack

ChainAware is the only provider that operates natively at Layer 3 – and the only one that connects Layer 3 intelligence directly to a growth deployment layer. Five distinct advantages define ChainAware’s position against every other provider in the landscape.

USP 1: The Only Forward-Looking Behavioral Intelligence

Every Layer 2 provider is backward-looking by design. Chainalysis traces where funds came from. Nomis scores how active a wallet has been. Trusta measures whether coordination patterns suggest a Sybil. Nansen labels which entity a wallet belongs to. All four describe the past. ChainAware is the only provider that uses behavioral history as input to predictive ML models – producing forward-looking probability scores that answer what will happen next. This is the difference between reading a wallet’s bank statement and predicting its next transaction. For the technical distinction between descriptive and predictive AI in blockchain contexts, see our Forensic vs AI-Powered Analytics guide.

USP 2: The Only Provider With a Growth Deployment Layer

Intelligence without deployment is analysis. ChainAware’s Growth Agents take the Web3 Persona output and deploy it directly into DApp UI at wallet connection – automatically generating personalised content and CTAs without any human configuration per user. The mechanism works like Google AdWords inside your own product: a lightweight JavaScript snippet triggers at wallet connection, queries the Prediction MCP for the connecting wallet’s persona in milliseconds, and adjusts the UI accordingly before the user sees anything. A High Lend intention wallet sees lending content first. A Low Experience wallet sees simplified onboarding. Neither wallet needed to self-identify. No Layer 2 provider has an equivalent deployment mechanism. For the Agentic User Onboarding use case in full detail, including how the routing logic works at wallet connection, the learn documentation covers the complete architecture. For documented production results, see our SmartCredit.io Case Study.

USP 3: The Only MCP-Native Layer 3 Provider

Layer 1 providers (Moralis, Dune, Nansen) all now publish MCP servers – delivering data to AI agents via natural language. ChainAware is the only provider with an MCP server delivering predictions rather than data. An AI agent querying ChainAware’s Prediction MCP asks “What is the behavioral profile of 0x2f71…?” and receives fraud probability, all 12 intention probabilities, experience level, risk score, and AML status in a single structured response – pre-computed, sub-second, ready to act on. No data analysis required by the agent. See the Prediction MCP setup guide for the complete integration walkthrough. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for AI agent tool access. For how ChainAware’s Prediction MCP integrates into agent architectures, see our Prediction MCP guide and our 12 Blockchain Capabilities Any AI Agent Can Use.

USP 4: The Only Stack Combining Fraud + Behavioral Profile + Growth + Token Quality

Chainalysis does forensic compliance – not growth or behavioral intentions. Nomis does reputation scoring – not fraud prediction or growth deployment. Trusta does Sybil detection – not behavioral personalization or token holder quality. Nansen does smart money labeling – not fraud prediction or DApp personalization. ChainAware uniquely combines all four capabilities in one stack: fraud detection (98% accuracy), behavioral persona (22 dimensions), growth deployment (Growth Agents, User Analytics), and token holder quality (Token Rank). No competitor covers more than one of these four areas. Token Rank specifically addresses a use case no other wallet intelligence provider offers – scoring the behavioral quality of every token’s holder base to distinguish genuine communities from Sybil networks and manufactured adoption. For how Token Rank exposes long rug pulls, see our Rug Pull Detection guide.

USP 5: Free Entry Point – No Other Layer 3 Provider Offers This

The Wallet Auditor delivers the complete Web3 Persona for any address – free, no signup, no wallet connection required. Paste any address and receive fraud probability, all intention scores, experience level, risk profile, AML status, and Wallet Rank in under a second. Enterprise Layer 2 providers like Chainalysis charge $100,000+ annually for access. Layer 2 reputation providers like Nomis and Trusta offer partial free tiers but require wallet connection. ChainAware’s free tier provides the full Layer 3 intelligence output for individual queries – lowering the barrier to experiencing the product to near zero and allowing any team to evaluate the quality of the intelligence before committing to an API integration. For the complete Web3 reputation score comparison including Nomis, RubyScore, and others, see our Web3 Reputation Score Comparison.

Provider Comparison Tables

The Three-Layer Stack – Who Sits Where

Layer	Question Answered	Output Type	Key Providers	Requires Further Interpretation?
Layer 1: Infrastructure	“What transactions occurred?”	Raw / indexed on-chain data	Alchemy · Moralis · The Graph · Dune · Covalent · Etherscan	Yes – significant analytical work required
Layer 2: Descriptive	“Who is this wallet based on what it has done?”	Structured behavioral profiles, scores, reports	Nansen · Nomis · Trusta Labs · Chainalysis · TRM Labs · Spectral · DeepDAO · Nominis	Yes – human analyst or custom pipeline required
Layer 3: Actionable	“What will this wallet do next – and what should I do?”	Forward-looking predictions + instructions	ChainAware.ai (only full-stack Layer 3 provider)	No – directly consumable by DApp, agent, or compliance system

ChainAware vs Direct Layer 2 Competitors

Capability	ChainAware	Nomis	Trusta Labs	Nansen	Chainalysis
Forward-looking predictions	12 intention categories	Activity score only	Sybil risk only	Historical labels	Forensic traces
Fraud prediction	98% accuracy		Partial (Sybil)		Reactive forensics
AML / OFAC					Primary function
Experience + risk profile	22 dimensions	Partial	Partial (MEDIA)	Partial
Growth agents / personalization	Native deployment layer
Token holder quality	Token Rank			Partial
MCP / AI agent native	Prediction MCP			Data MCP
Free individual lookup	Full Wallet Auditor	Partial	Partial
Chains	8 (ETH/BNB/BASE/POL/TON/TRON/HAQQ/SOL)	50+	EVM + TON	18+	Multi-chain
Pricing	Freemium → API tiers	Freemium	Freemium	Paid	$100K-$500K/year
Primary use case	Growth + fraud prevention + AI agents	Airdrop/Sybil gating	Sybil prevention + PoH	Investment intelligence	VASP compliance

Which Layer Does Your Use Case Need?

Selecting the right wallet auditing layer depends entirely on what decision you need to make and how fast you need to make it. Most use cases require tools from multiple layers working together – but the Layer 3 intelligence layer is what determines whether your output is a report to be read or an instruction to be executed.

Use Case: DApp Growth and Conversion Optimization

Your DApp connects 200 wallets per day and converts approximately 1 at 0.5%. You need to understand who those wallets are and serve them experiences that match their intentions – immediately at wallet connection, without manual configuration. You need Layer 3. ChainAware’s Growth Agents read the Web3 Persona at connection and personalise content automatically. Layer 1 data cannot help here – it is too raw. Layer 2 profiles are too slow and require analytical overhead you do not have. Only Layer 3 intelligence operating in the 200-millisecond connection window improves conversion. For the full growth architecture, see our DeFi Onboarding guide and our User Segmentation guide.

Use Case: Airdrop Sybil Prevention

You are running a token distribution or airdrop campaign and need to filter bot wallets from genuine community participants. You primarily need Layer 2 – specifically Trusta Labs or Nomis. Both provide well-tested Sybil prevention infrastructure with broad chain coverage and established integrations with Galxe and similar platforms. Adding ChainAware’s Wallet Rank as a secondary filter strengthens quality – high Wallet Rank holders represent genuine, experienced Web3 participants who are far less likely to be airdrop farmers. The combination of Sybil filtering (Layer 2) and behavioral quality scoring (Layer 3) produces the highest-quality airdrop distributions.

Use Case: MiCA / AML Compliance Screening

Your protocol must screen wallets for AML risk, OFAC exposure, and sanctions compliance under MiCA or equivalent regulatory frameworks. You need Layer 3 fraud prediction + AML from ChainAware for pre-execution screening, plus a Layer 2 forensic tool if you need evidence-grade post-incident reporting. ChainAware’s AML screening and 98% accurate fraud prediction cover the real-time pre-transaction compliance requirement at a fraction of Chainalysis pricing. Chainalysis or TRM Labs add investigative depth if regulatory authorities require detailed fund flow reconstruction. For the complete MiCA compliance stack, see our DeFi Compliance Tools guide.

Use Case: AI Agent Behavioral Intelligence

Your AI agent needs to make real-time decisions about wallet addresses – routing users, screening for fraud, personalising recommendations, or verifying governance participants. You need Layer 3 via the Enterprise API or Prediction MCP. Layer 1 MCP servers (Moralis, Dune) deliver data that your agent must still interpret. ChainAware’s Prediction MCP delivers decisions. The agent asks a behavioral question in natural language and receives a prediction ready to act on – no blockchain expertise, no data pipelines, no model training required. For the full AI agent data stack architecture, see our Web3 Agentic Economy guide.

Access Layer 3 Intelligence via Any AI Agent

ChainAware Prediction MCP – Behavioral Predictions via Natural Language

Your agent asks “What will this wallet do next?” and gets fraud probability, all 12 intention scores, experience, risk, and AML status in under 1 second. Pre-computed. No blockchain expertise required. Compatible with Claude, GPT, and any LLM. 32 open-source MIT-licensed agent definitions on GitHub. 18M+ wallet profiles. 8 chains.

Get MCP Access Prediction MCP Guide

Frequently Asked Questions

What is the difference between a wallet audit and a smart contract audit?

Smart contract audits (CertiK, Sherlock, QuillAudits, Halborn) review Solidity or Rust code for vulnerabilities before deployment. They answer “is this contract safe to interact with?” Wallet audits analyze the behavioral history of the address behind a contract or transaction. They answer “is the person operating this address trustworthy?” Both are security practices, but they address completely different attack surfaces. Smart contract audits catch technical code vulnerabilities. Wallet audits catch fraudulent operators, Sybil networks, sanctioned addresses, and behavioral risk patterns that code analysis cannot detect. Professional security stacks in 2026 use both – smart contract audits before launch, wallet behavioral intelligence for every address that interacts with the protocol post-launch.

Does TrustScan actually have 3 million users?

The “3M Total Users” figure on Trusta.AI’s homepage refers to wallets that have been processed through any Trusta product – including wallets screened on behalf of partner protocols like Celestia, Starknet, Manta, and Plume during their airdrop campaigns. Those wallet owners were screened without necessarily interacting with Trusta directly. The more operationally meaningful metric is 200K Monthly Active Users – people actively using Trusta’s products each month. Trusta has analyzed 570 million wallet addresses in total, which is a more accurate reflection of the platform’s analytical scale. For comparison, ChainAware’s 18M+ Web3 Personas represents addresses with deep behavioral profiles computed – a different metric reflecting analytical depth rather than query volume.

Should wallet audit output be a report or an instruction?

It depends entirely on your use case and who consumes the output. If a human compliance analyst reads the output and makes a decision, a descriptive report (Layer 2) is appropriate – the analyst has the expertise to interpret behavioral data and apply regulatory judgment. If a DApp frontend, a compliance system, or an AI agent consumes the output and must act within milliseconds, the output must be an instruction (Layer 3) – because no human review step fits in that window. Most teams in 2026 have shifted toward the second scenario faster than they anticipated: AI agents are replacing compliance roles, DApp personalization is happening at wallet connection, and growth optimization requires real-time decisions. That shift makes Layer 3 intelligence no longer a nice-to-have but a prerequisite for competitive performance. According to FATF’s Virtual Assets Recommendations , transaction monitoring and risk assessment requirements under AML/CFT frameworks increasingly mandate real-time screening – reinforcing the need for actionable rather than descriptive outputs.

Can I use Layer 2 and Layer 3 tools together?

Yes – and for most serious use cases, you should. Layer 2 and Layer 3 tools complement each other rather than competing. A recommended stack for a DeFi protocol in 2026 would combine Trusta or Nomis at Layer 2 for airdrop Sybil filtering (they excel at population-level bot detection), ChainAware at Layer 3 for individual wallet behavioral intelligence and growth personalization, and Alchemy or Moralis at Layer 1 for raw transaction data infrastructure when specific historical context is needed. The key insight is that each layer answers a different question – using all three gives you complete coverage without redundancy.

How does ChainAware’s fraud detection differ from Chainalysis?

Chainalysis is a forensic tool designed to trace illicit fund flows after the fact – identifying where funds came from, clustering addresses into known entities, and producing evidence-grade reports for law enforcement and regulatory filings. ChainAware’s fraud detection is a predictive tool designed to identify wallets likely to commit fraud before they act – using behavioral pattern analysis trained on 18M+ profiles with 98% accuracy. The practical difference: Chainalysis tells you that a wallet received funds from a known exchange hack two years ago. ChainAware tells you that a new wallet connecting to your DApp today has behavioral patterns consistent with fraud operators, even if no prior incident has been recorded. These are complementary capabilities – reactive forensics (Chainalysis) for post-incident investigation, predictive fraud detection (ChainAware) for pre-execution protection.

Sources: The Graph Developer Documentation · Chainalysis Platform · Anthropic Model Context Protocol · FATF Virtual Assets Recommendations · Trusta.AI Platform

The post Web3 Wallet Auditing Providers in 2026 – From Raw Blockchain Data to Actionable Web3 Personas first appeared on ChainAware.ai.

Every wallet address looks identical on the blockchain – a string of 42 hexadecimal characters. Behind each one, however, sits a completely different person: a sophisticated DeFi veteran with five years of complex protocol interactions, a curious newcomer trying their first swap, a yield farmer running capital across twelve chains simultaneously, or a speculative memecoin trader chasing the next 100x. Your DApp receives all of them with the same landing page, the same onboarding flow, and the same call to action. That is why 90% of connected wallets never transact. In 2026, there is a better approach.

ChainAware’s Web3 Personas solve the identity problem that has limited Web3 growth since the beginning. By analyzing the complete on-chain behavioral history of any wallet address, ChainAware calculates who the person behind that address actually is – their behavioral intentions, experience level, risk appetite, and predicted next actions. With 18M+ Web3 Personas already calculated across 8 blockchains, the intelligence layer needed to run 1:1 personalized growth at scale already exists. This guide explains how it works and, more importantly, how to use it.

What Is a Web3 Persona?

A Web3 Persona is ChainAware’s calculated behavioral profile of who is behind a wallet address. It answers the question that every DApp, protocol, and growth team needs answered but currently cannot: who is this user, what do they want, and what are they likely to do next?

In Web2, understanding your user requires cookies, form submissions, survey data, and demographic proxies – none of which work in a pseudonymous blockchain environment. Web3, however, provides something far more powerful: a complete, immutable, publicly verifiable record of every financial decision that wallet has ever made. Every protocol interaction, every token swap, every liquidity provision, every leverage position, every NFT purchase – all of it is permanently recorded on-chain. ChainAware reads that history across 8 blockchains, applies its predictive AI models trained on 18M+ wallet profiles, and produces a rich behavioral persona that describes the real person behind any address.

Why Personas Are More Powerful Than Web2 User Profiles

Web2 user profiles are constructed from inferred data – cookies approximate browsing behavior, purchase history suggests interests, demographic segments proxy for individual preferences. Web3 Personas, by contrast, come from actual financial decisions made with real money at real cost. A wallet’s on-chain history is not browsing behavior – it is a complete record of consequential actions. Every transaction cost gas fees to execute. Every protocol interaction required the user to actively sign a transaction. Every leverage position involved real capital at real risk. Consequently, the behavioral signal quality in on-chain data is dramatically higher than any Web2 proxy – and it requires no cookies, no KYC, and no privacy invasion to access. For the full comparison of Web2 and Web3 data as marketing intelligence, see our Behavioral User Segmentation guide and our Web3 User Segmentation guide.

The Dimensions: What ChainAware Calculates for Every Wallet

A Web3 Persona is not a simple score or category – it is a multi-dimensional profile that captures distinct aspects of a wallet’s behavioral identity. ChainAware calculates the following dimensions for every address across its supported blockchains.

Behavioral Intentions (High / Medium / Low)

The intentions dimension is the most powerful for growth use cases because it answers “what is this user most likely to do on your platform next?” ChainAware calculates probability levels – High, Medium, or Low – for each of the following intention categories:

• Borrow – probability of taking a DeFi loan in the near future
• Lend – probability of providing capital to a lending protocol
• Trade – probability of executing token swaps on DEXes
• Gamble – probability of engaging with high-risk speculative positions
• NFT – probability of purchasing, minting, or trading NFTs
• Stake ETH – probability of ETH staking activity
• Stake Yield Farm – probability of yield farming across protocols
• Leveraged Staking – probability of leveraged staking positions
• Leveraged Staking ETH – probability of leveraged ETH-specific staking
• Leveraged Lending – probability of leveraged lending strategies
• Leveraged Long ETH – probability of leveraged long ETH positions
• Leveraged Long Game – probability of leveraged long gaming/metaverse positions

These intention probabilities are calculated from behavioral patterns in the wallet’s full transaction history – not from the most recent transactions alone, but from the complete pattern of engagement across all supported chains. A wallet that has borrowed on three lending protocols and repeatedly repaid and reborrowed has a High Borrow intention. A wallet that has never touched a leverage product and consistently holds conservative positions has a Low Gamble intention. These signals are objective, verifiable, and far more reliable than any self-reported preference data. For how intentions drive personalization in practice, see our Intention-Based Marketing guide.

Experience, Risk, and Identity Dimensions

Beyond intentions, ChainAware calculates the following profile dimensions that together describe who this wallet owner is as a Web3 participant:

• Experience Level – overall sophistication from blockchain transaction patterns (Beginner / Intermediate / Advanced / Expert)
• Willingness to Take Risk – behavioral risk appetite derived from historical position sizes and protocol complexity
• Categories Used – which DeFi categories this wallet has engaged with (Lending, DEX, Staking, Gaming, NFT, Bridges, etc.)
• Protocols Used – specific protocols interacted with across all supported chains
• Wallet Rank – ChainAware’s composite reputation score reflecting the overall quality and trustworthiness of the address
• Wallet Age – how long the address has been active on-chain
• Transaction Numbers – volume of on-chain interactions indicating engagement depth
• Balance – current asset holdings as a proxy for capital capacity
• Predicted Fraud Probability – AI-calculated likelihood of this address engaging in fraudulent activity (98% accuracy, backtested on CryptoScamDB)
• AML / OFAC / Sanctions Attributes – compliance screening flags for regulatory requirements

Together, these dimensions paint a complete picture of the person behind any wallet address – their capability, their history, their intentions, and their trustworthiness. For the complete Wallet Rank methodology and what each dimension represents, see our Wallet Rank guide and our Wallet Auditor guide.

The Spider Chart: Visualizing Identity on a Multi-Dimensional Map

The most intuitive way to understand a Web3 Persona is to imagine every Web3 user plotted on a spider chart – sometimes called a radar chart – where each axis of the spider web represents one of the persona dimensions. Experience sits on one axis. Risk willingness sits on another. Each intention category occupies its own axis. The result is a unique geometric shape for every wallet address – no two wallets produce identical spider charts, and the shape immediately communicates who this person is as a Web3 participant.

Why the Spider Chart Makes Differences Visible

Consider two wallets arriving at the same DeFi lending platform. Wallet A has a spider chart that extends far out on the Borrow, Lend, and Experience axes – and barely registers on Gamble or NFT. Wallet B has a completely different shape: high on NFT and Trade, low on Lend and Stake ETH, medium on Gamble. Both wallets look identical from the platform’s perspective if you only see “wallet connected.” Their spider charts tell a completely different story. Wallet A is an experienced DeFi lending user who will likely convert if shown relevant lending content immediately. Wallet B is an NFT-focused trader who may be exploring lending for the first time – and needs a completely different first experience if they are going to convert at all. Serving identical content to both produces low conversion for both. Serving persona-matched content produces dramatically higher conversion for each. For the SmartCredit.io case study documenting exactly this result, see our SmartCredit Case Study.

Real Examples: sassal.eth and vitalik.eth

Abstract explanations of multi-dimensional behavioral profiles become concrete the moment you apply them to real, well-known wallet addresses. ChainAware has calculated Web3 Personas for both sassal.eth (prominent Ethereum educator and content creator) and vitalik.eth (Ethereum co-founder). The resulting spider charts illustrate how dramatically different two highly experienced Web3 participants can be in their behavioral profiles – and why treating them identically as “experienced DeFi users” misses the most important distinctions.

sassal.eth – Experienced Educator Profile

sassal.eth’s persona reflects an experienced, education-focused Ethereum participant. The profile shows strong engagement with ETH staking and established lending protocols – consistent with a long-term Ethereum holder who interacts with the ecosystem thoughtfully rather than speculatively. The Gamble and Leveraged Long dimensions are notably low, reflecting a risk-conscious behavioral pattern that matches public content about measured, educational DeFi engagement. If sassal.eth connects to a DeFi protocol, the Growth Agent serving their session should immediately surface staking options, established lending pools, and educational content – not high-risk leverage products or speculative memecoin exposure.

vitalik.eth – Unique Founder Profile

vitalik.eth’s persona shape is unlike any other – reflecting the singular nature of the Ethereum co-founder’s on-chain behavioral history. Maximum experience level across every dimension reflects a wallet that has interacted with virtually every category of DeFi, NFT, and ecosystem activity since the earliest days of the network. The specific intention distribution, however, shows clear behavioral patterns that distinguish this address from a generic “experienced user” classification. The spider chart makes those distinctions immediately visible in a way that a simple score or category label never could. For each of these addresses, a one-size-fits-all content experience would be significantly worse than a persona-matched one.

See Any Wallet’s Full Persona – Free

ChainAware Wallet Auditor – Complete Web3 Persona in Under 1 Second

Paste any wallet address and get the complete persona: experience level, risk appetite, all intention probabilities, fraud probability, AML status, Wallet Rank, and behavioral categories. Free. No wallet connection. No signup. Try your own address or any address you’re curious about – including the examples above. Full documentation at the Wallet Auditor learn page.

Audit Any Wallet Free Wallet Auditor Guide

The Web3 Growth Problem Personas Solve

Web3 growth is broken. The numbers are stark: acquiring one transacting DeFi user costs between $300 and $1,000 – ten to twenty times the equivalent cost in Web2. For every 200 visitors who reach a DeFi protocol, roughly ten connect their wallet. Of those ten, only one transacts. That 0.5% end-to-end conversion rate is not an anomaly – it is the Web3 industry average. The standard response is to spend more on acquisition: bigger airdrop budgets, more KOL campaigns, higher liquidity mining emissions, more aggressive paid ads. None of these tactics address the actual problem. For the full architecture of how Agentic User Onboarding routes wallets automatically at connection based on their persona, the learn documentation covers the complete system.

Why Standard Growth Tactics Fail

Airdrops attract wallet farmers who claim tokens and leave. KOL campaigns generate traffic from audiences that have no behavioral affinity for the protocol. Liquidity mining attracts mercenary capital that exits the moment a better rate appears elsewhere. Paid ads deliver undifferentiated traffic with no targeting precision beyond basic demographic proxies. All four approaches share the same fundamental failure: they bring wallets to a platform that then treats every single one identically. A sophisticated DeFi veteran and a first-time wallet holder arrive at the same landing page. Both see the same headline, the same features list, the same call to action. The DeFi veteran finds nothing compelling enough to action immediately. The newcomer finds the experience confusing. Both leave without transacting. The acquisition spend is wasted on both. For the full analysis of why Web3 marketing channels fail and what the alternative looks like, see our Why Web3 KOL Marketing Fails guide and our DeFi Onboarding guide.

The Conversion Gap Personas Close

Web3 Personas shift the intervention point from acquisition to conversion – the moment immediately after wallet connection when the user is on the platform and engaged. The moment a wallet connects, ChainAware calculates their full persona in under a second. That persona determines everything about the experience they receive: which product the platform highlights first, which CTA appears in the hero section, which risk level is shown by default, which educational content is surfaced, which social proof is relevant. A High Borrow intention wallet arriving at a lending platform immediately sees borrow rates, available collateral options, and a “Borrow Now” CTA. A High Stake Yield Farm intention wallet arriving at the same platform sees yield options, APY comparisons, and “Start Earning” messaging. Neither wallet needed to self-identify or complete a survey – their behavioral history told the platform everything it needed to know. For the detailed conversion mechanics and how resonating content produces measurable results, see our Web3 Personas Personalized Marketing guide.

Growth Agents: Deploying Personas as 1:1 Personalization

Understanding personas is the intelligence layer. ChainAware’s Growth Agents are the deployment layer that translates persona intelligence into personalized user experiences automatically, at scale, without any manual configuration per user.

How Growth Agents Work – Like Google AdWords for Your DApp

Think of Growth Agents as the Web3 equivalent of Google AdWords – but running inside your own DApp interface rather than on Google’s ad network. Google AdWords works by matching ad content to user intent signals (search queries) and serving the most relevant ad automatically. ChainAware Growth Agents work by matching DApp content to wallet behavioral signals (the Web3 Persona) and serving the most resonating content and CTAs automatically. The mechanism integrates directly into your DApp UI with a lightweight JavaScript snippet – comparable to adding Google Tag Manager or any analytics pixel. When a user connects their wallet, the agent reads the wallet address, queries ChainAware’s Prediction MCP for the full persona in milliseconds, and dynamically adjusts the content visible to that specific user before they see anything. The user sees a platform that feels built for them. They never know personalization is happening. Conversion rates increase because the content resonates. For the SmartCredit.io documented case of this working in production, see our case study.

What the Agent Personalizes

Growth Agents can personalize any content element that is driven by the DApp’s frontend: hero section headlines and sub-copy, featured product or pool recommendations, CTA button text and destination, risk level displayed by default, educational content surfaced in onboarding flows, notification messaging, and promotional banners. Every element responds to the wallet’s persona dimensions. A wallet with High Experience and High Leverage Long ETH sees advanced product options immediately. A wallet with Low Experience and Low Risk sees simplified entry-level options with educational context. Neither wallet had to tell the platform anything – their blockchain history told the agent everything. For the technical architecture of how Growth Agents integrate with DApp frontends, see our AI Agent Personalization guide and our Web3 Agentic Economy guide.

Autonomous, Continuous, Self-Learning

Growth Agents run autonomously once deployed – no manual configuration per user, no campaign management overhead, no A/B test scheduling. The agent handles every wallet connection independently, calculating and serving persona-matched content in real time. As ChainAware’s behavioral models update with new on-chain data, the persona calculations improve automatically. This means the personalization quality improves continuously without requiring the DApp team to do anything. Founders and growth teams redirect the time they previously spent manually configuring targeting rules toward higher-value strategic work – exactly the founder bandwidth argument that drives Web3’s coming innovation wave. For the unit economics of why this reduces effective acquisition cost, see our Unit Costs guide and our Crossing the Chasm guide.

Know Your Users Before You Spend Another Dollar on Acquisition

ChainAware Web3 User Analytics – Free Persona Distribution in 24 Hours

Add 2 lines of Google Tag Manager code to your DApp. Within 24 hours, see the full persona distribution of your connecting wallets – experience levels, risk profiles, intention segments, behavioral categories. Understand who is actually showing up before deciding how to talk to them. Free forever. No developer resources required. Full guide at the Web3 User Analytics learn page.

Get Free Analytics Analytics Guide

Wallet Auditor: Free Persona for Any Address

The Wallet Auditor is ChainAware’s free individual-user tool for accessing the full Web3 Persona of any wallet address. Paste any Ethereum, BNB, BASE, POLYGON, TON, or HAQQ address and receive the complete persona output: experience level, risk willingness, all intention probability scores, behavioral categories used, protocols interacted with, Wallet Rank, wallet age, transaction count, balance context, fraud probability, and AML/OFAC screening status. No signup required. No wallet connection needed. The full persona appears in under a second.

Who Uses the Wallet Auditor

The Wallet Auditor serves multiple audiences. Individual users check their own wallets to understand what their on-chain history says about them – and to verify their Wallet Rank before using it as a trust signal. DeFi participants check counterparty wallets before large transactions, partnerships, or delegate decisions. KOL teams audit influencer wallets before paying for promotions – a KOL whose wallet shows no genuine DeFi engagement is a mass marketer, not a genuine community builder. DAOs audit delegate and governance participant wallets to verify that voting power holders have meaningful on-chain experience. Security teams check sender wallets when receiving unexpected tokens or unusual transaction requests. For the complete Wallet Auditor feature breakdown, see our Wallet Auditor guide. For how Wallet Rank functions as a portable Web3 reputation credential, see our Wallet Rank guide. According to CoinMarketCap’s Web3 wallet overview , the number of active Web3 wallets continues growing rapidly – making persona-based wallet intelligence an increasingly critical layer for navigating interactions with unknown addresses.

Web3 User Analytics: Persona Distribution of Your DApp Users

While the Wallet Auditor provides individual persona lookups, Web3 User Analytics scales the same intelligence to the entire connecting user base of a DApp. The setup requires adding two lines of JavaScript to your DApp via Google Tag Manager – comparable to installing any analytics pixel. Within 24 hours, ChainAware’s analytics dashboard shows the complete persona distribution of every wallet that has connected to the platform: what percentage are High Experience vs Beginner, what the dominant intention profiles are, what risk appetite distribution looks like, which behavioral categories are most common among your users.

From Blindness to Clarity in 24 Hours

Most DApp teams know how many wallets connected but nothing about who those wallets represent. Web3 User Analytics answers every question that wallet count cannot: Are most of your users experienced DeFi participants or newcomers? Do the majority have High Borrow intentions – or are they primarily yield farmers who will never use your lending product? What fraction carry fraud probability flags that suggest low-quality traffic? Are your KOL campaigns bringing genuinely high-quality users or airdrop farmers whose behavioral profiles show no long-term engagement patterns? These questions currently require expensive manual research – or remain permanently unanswered. ChainAware’s free analytics layer answers them automatically, continuously, with no engineering overhead beyond the initial GTM snippet. For the full analytics platform capabilities and what the dashboard shows, see our Web3 Marketing Analytics guide and our complete analytics guide. For why understanding your existing user base matters before optimizing acquisition, see our User Segmentation guide.

Token Rank: Personas Applied to Token Holder Quality

Token Rank applies Web3 Persona intelligence to a specific and critical investment problem: distinguishing genuine token communities from artificially inflated holder bases engineered to attract investment before a coordinated exit. Every token holder is a wallet address with a Web3 Persona. The Wallet Rank dimension of that persona reflects the quality and depth of that holder’s on-chain engagement history. Token Rank aggregates the Wallet Ranks of all token holders and produces a composite score for the token itself – reflecting the genuine quality of its community rather than the raw count of addresses holding it. For the complete Token & Community Intelligence use case, see the Token & Community Intelligence learn guide.

Why Token Rank Exposes Long Rug Pulls

The most sophisticated rug pulls in 2026 are not the obvious liquidity-drain-in-24-hours variety. Long rug pulls build artificial communities over months: they distribute tokens to thousands of freshly created wallet addresses with no transaction history, manufactured Telegram groups fill with paid shills, and the price chart looks healthy because the holder count is growing. Token Rank pierces this illusion because freshly created wallets have near-zero Wallet Ranks – they have no on-chain behavioral history, no protocol engagement, and no demonstrated DeFi participation. A token showing 50,000 holders but a low median Wallet Rank is not a genuine community – it is a network of dust wallets bought to manufacture the appearance of adoption. By contrast, a token with 5,000 holders but a high median Wallet Rank represents an authentic community of experienced, engaged Web3 participants who chose this token based on their own research. That distinction is the single most powerful signal for separating genuine projects from sophisticated fraud. For the complete Token Rank methodology and how to use it for due diligence, see our complete product guide. According to Immunefi’s Web3 security research , exit scams remain the largest category of DeFi losses annually – and Token Rank directly addresses the pattern recognition that catches them.

Developer Access: MCP and Open-Source Agents

DApp teams and developers who want programmatic access to Web3 Persona data for building custom agent workflows have two primary integration paths: the Prediction MCP and the open-source pre-built agent library.

Prediction MCP: Natural Language Access to All Persona Dimensions

ChainAware’s Prediction MCP is an SSE-based Model Context Protocol server that exposes all persona dimensions to any AI agent or LLM via natural language queries. An agent asks “What is the behavioral profile of 0x123…abc?” and receives the complete persona – all intention probabilities, experience level, risk score, Wallet Rank, fraud probability, and AML status – in a single structured response in under a second. The MCP works with Claude, GPT, and any open-source LLM. Integration requires adding the MCP server configuration to the agent’s tool list – no custom API integration code, no blockchain parsing, no data pipeline. For the complete MCP integration guide and all five exposed tools, see our Prediction MCP guide and our 12 Blockchain Capabilities guide. For context on how the MCP standard is transforming AI agent data access across Web3, see our Blockchain Data Providers guide.

32 Open-Source Pre-Built Agents

For developers who want to deploy persona-powered agents without building from scratch, ChainAware publishes 32 MIT-licensed agent definitions on GitHub. Each agent integrates the Prediction MCP for persona access and implements a specific workflow – fraud detection, AML compliance, onboarding routing, marketing personalization, governance verification, DeFi intelligence, and more. Developers clone the relevant agent, configure it with their Prediction MCP credentials, and deploy. The growth agent that reads wallet personas and generates personalized DApp content is one of the 32 available agents – ready to integrate directly into any DApp’s frontend stack. For the full agent catalog and deployment instructions, see our Web3 Agentic Economy guide. According to Anthropic’s Model Context Protocol documentation , MCP has rapidly become the standard for connecting AI agents to external data providers – making ChainAware’s MCP server compatible with the widest possible range of agent frameworks from day one.

Build Persona-Powered Agents Without Starting from Scratch

32 Open-Source Agents + Prediction MCP – Clone, Configure, Deploy

Every persona dimension – intentions, experience, risk, fraud probability, AML status – accessible via natural language through the Prediction MCP. 32 MIT-licensed pre-built agent definitions covering growth, compliance, fraud detection, governance, and DeFi intelligence. Works with Claude, GPT, and any LLM. No data pipelines to build.

Get MCP Access Prediction MCP Guide

Web3 Persona Dimensions Reference Table

Frequently Asked Questions

How does ChainAware calculate Web3 Personas without knowing who the person is?

ChainAware never attempts to identify the individual behind a wallet address – and does not need to. Instead, it analyzes the complete on-chain transaction history of the address across 8 blockchains, applying predictive AI models trained on 18M+ wallet profiles to classify behavioral patterns. A wallet that has borrowed, repaid, and reborrowed across multiple lending protocols produces a strong Borrow Intention signal – regardless of who owns it. The behavioral pattern is the signal; the identity is irrelevant. This approach preserves user anonymity completely while producing behavioral intelligence that is more accurate than identity-based profiling because it reflects actual financial decisions rather than demographic proxies.

How are 18M+ Web3 Personas already calculated?

ChainAware continuously analyzes the on-chain activity of wallet addresses across ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, and SOL – building and updating persona profiles for every address that has meaningful on-chain history. The 18M+ figure represents wallets with sufficient transaction history to produce reliable persona classifications. As blockchain activity continues growing and new wallets accumulate behavioral history, the covered population expands automatically. The models retrain continuously on new behavioral data, which means persona quality improves over time without requiring any action from DApp teams using ChainAware’s tools.

Can Web3 Personas be wrong or manipulated?

No behavioral model is 100% accurate – and ChainAware’s models are designed with specific accuracy metrics and confidence thresholds that reflect real-world performance. The fraud probability dimension, for example, carries 98% accuracy validated against CryptoScamDB using an independent test set. For intention dimensions, the models are trained on historical behavioral patterns and are regularly validated against observed user actions. Regarding manipulation: unlike Web2 profile data that can be easily fabricated with fake accounts or purchased behavioral data, on-chain transaction history requires real gas fees and real time to generate. Manufacturing a sophisticated behavioral profile is expensive and detectable – the cost and time required to fake extensive DeFi engagement patterns makes manipulation economically irrational at scale. According to a16z crypto’s research on on-chain behavioral data , blockchain transaction data provides unusually high-quality behavioral signal precisely because each action has real economic cost attached.

How do Web3 Personas differ from basic wallet analytics tools?

Basic wallet analytics tools show what happened – transaction history, token balances, protocol interactions, NFT holdings. Web3 Personas show who the person is and what they will do next – behavioral classifications, intention probabilities, risk profiles, and forward-looking predictions. The distinction is the difference between reading a bank statement and understanding a customer. A bank statement tells you what transactions occurred; a behavioral profile tells you what kind of financial actor this person is and what they are likely to need from your product. Web3 Personas convert raw on-chain data into actionable growth intelligence – the layer that makes 1:1 personalization possible without requiring wallets to self-identify. For how this compares to other analytics approaches, see our Web3 Analytics Tools comparison.

What is the fastest way to start using Web3 Personas for growth?

The fastest path is the free Web3 User Analytics tier – add two lines of GTM code to your DApp and see the full persona distribution of your users within 24 hours. This costs nothing and requires no engineering resources beyond the GTM snippet. The next step is integrating ChainAware’s Growth Agents into your DApp frontend to activate persona-driven personalization at wallet connection – this turns the analytics insight into a conversion improvement immediately. For teams building custom workflows, the Prediction MCP gives any AI agent instant access to all persona dimensions via natural language query. All three paths start with understanding who your users already are before optimizing how you talk to them.

Sources: CoinMarketCap – Web3 Wallets Overview · Immunefi – Web3 Security Research · Anthropic – Model Context Protocol · a16z Crypto – On-Chain Behavioral Data Research · FATF – Virtual Assets Recommendations

The post What Are Web3 Personas? How to Use Them to Enable Your Growth – Complete Guide 2026 first appeared on ChainAware.ai.

AI agents need data to make decisions. In Web3, the richest behavioral data source in the world – 18+ years of immutable public transaction history across billions of wallet addresses – sits freely accessible on public blockchains. The problem is that raw blockchain data is not agent-ready. A transaction history full of hexadecimal addresses and token amounts tells an AI agent nothing useful until someone translates it into intelligence the agent can act on. In 2026, a competitive ecosystem of blockchain data providers has emerged to close that gap – each taking a different approach to what “agent-ready blockchain data” actually means.

This guide maps the complete landscape: seven providers enabling AI agent access to on-chain wallet data, organized by what kind of data they deliver and how agent-ready that data actually is. The core distinction – between raw indexed data that agents must still interpret, and pre-computed behavioral intelligence that agents can act on immediately – determines which provider belongs at which layer of your agent stack.

Why AI Agents Need On-Chain Wallet Data

The blockchain AI market reached $735 million in 2025 and is projected to hit $4.04 billion by 2033 – growing at a CAGR of 23.81%. That growth is driven not by speculation but by a specific operational requirement: AI agents operating in Web3 need to make decisions about wallet addresses constantly. A compliance agent screening transactions must know whether a wallet carries AML risk. A DeFi onboarding agent routing new users must know their experience level and behavioral profile. A fraud detection agent monitoring a protocol must predict which addresses are likely to commit fraud before they act. A trading agent managing a portfolio must understand whether a token’s holders represent genuine smart money or coordinated shill networks. For the complete overview of how AI agents interact with blockchain infrastructure, see the ChainAware For AI Agents overview.

The Data Gap That Limits Agent Intelligence

Without access to on-chain wallet data, agents make generic decisions. Generic decisions produce poor outcomes – wrong users get the same experience as right users, fraudulent wallets pass through undetected, and opportunities that depend on behavioral context get missed entirely. The agents that perform best in 2026 are those connected to real-time, high-quality blockchain intelligence – not just transaction feeds, but interpreted behavioral signals they can immediately act on. For how behavioral intelligence specifically transforms agent decision-making, see our AI Agent Personalization guide and our Web3 Agentic Economy guide. According to Grand View Research’s AI market data , AI systems with access to domain-specific real-time data consistently outperform general-purpose models by significant margins in specialized applications.

The Two-Tier Distinction: Raw Data vs Behavioral Intelligence

Before evaluating individual providers, the most important conceptual distinction in this landscape is the difference between raw or indexed blockchain data and pre-computed behavioral intelligence. This distinction determines how much analytical work an agent must perform before it can act on what a provider delivers.

Tier 1: Raw and Indexed Blockchain Data

Tier 1 providers give AI agents structured access to what has happened on the blockchain – wallet balances, transaction histories, token holdings, DeFi positions, NFT ownership, protocol interactions. This data is essential and powerful. However, the agent still has to figure out what it means. A wallet’s transaction history does not automatically tell an agent whether that wallet is trustworthy, what it is likely to do next, or whether it matches the behavioral profile of the users a DeFi protocol wants to attract. Moralis, Nansen, Dune Analytics, The Graph, Datai, and Alchemy all operate primarily at this tier – delivering data the agent must still analyze or score. For a complete overview of what blockchain capabilities AI agents can access, see our 12 Blockchain Capabilities Any AI Agent Can Use guide.

Tier 2: Pre-Computed Behavioral Intelligence

Tier 2 providers deliver pre-computed predictions and intelligence scores that agents can act on immediately, without building their own analytical layer. Instead of delivering “this wallet made 47 transactions across 12 protocols,” a Tier 2 provider delivers “this wallet has a 0.94 fraud probability, a High experience level, a borrower behavioral profile, and a Low rug pull risk.” The agent does not need to analyze the transaction history – the prediction is already computed from 18M+ behavioral profiles and delivered in under a second. ChainAware’s Prediction MCP operates at this tier. The distinction maps directly to agent performance: Tier 1 data enables analytical agents; Tier 2 intelligence enables decision-making agents. For the detailed breakdown of predictive vs generative AI in this context, see our Generative vs Predictive AI guide.

1. ChainAware.ai – Behavioral Prediction MCP (Pre-Computed Intelligence)

Data type: Pre-computed behavioral predictions – fraud probability, AML risk, wallet rank, behavioral personas, rug pull risk, experience level, risk tolerance, behavioral intentions
Integration: Prediction MCP (SSE-based, natural language queries) + REST API + Google Tag Manager pixel
Chains: ETH, BNB, BASE, POLYGON, TON, TRON, HAQQ, SOL (8 chains)
Agent-ready: Fully pre-computed – no analysis required

ChainAware occupies a unique position in the blockchain data provider landscape: the only provider delivering forward-looking behavioral predictions rather than backward-looking data retrieval. While every other provider in this comparison answers “what has this wallet done?”, ChainAware answers “what will this wallet do next, and how trustworthy is it?” That distinction matters enormously for AI agent use cases because agents are fundamentally decision-making systems – and decisions require predictions, not just history.

What the Prediction MCP Delivers

The ChainAware Prediction MCP exposes five core tools queryable by any AI agent in natural language: fraud probability detection (98% accuracy, backtested on CryptoScamDB), behavioral prediction (experience level, risk tolerance, segment classification), rug pull risk scoring (creator and LP behavioral Trust Score), token ranking (holder quality scoring via Wallet Rank), and AML screening. Together, these tools give agents immediate answers to the questions that drive the most important Web3 decisions: Is this wallet safe to interact with? What kind of user is this? Should this protocol onboard this address? Is this pool likely to rug pull? An agent integrating the Prediction MCP via Claude, GPT, or any LLM can ask “What is the fraud risk of 0x123…abc?” and receive a structured prediction response in under a second. For the complete integration guide, see our Prediction MCP guide and our 5 Ways Prediction MCP Turbocharges DeFi.

32 Open-Source Pre-Built Agents

Beyond the MCP tools themselves, ChainAware publishes 32 MIT-licensed pre-built agent definitions covering fraud detection, compliance screening, growth intelligence, DeFi analysis, governance verification, GameFi scoring, and AI agent verification. See the full catalogue at the Security & Fraud Agents documentation. These agent definitions integrate ChainAware’s Prediction MCP with specific workflows – developers clone and deploy rather than build from scratch. The combination of pre-computed predictions, natural language MCP access, and ready-made agent definitions makes ChainAware the fastest path from zero to a production-quality behavioral intelligence layer for any AI agent stack. For how the 18M+ wallet profile dataset was built and what it covers, see our complete product guide.

Best agent use cases: Fraud detection agents · Compliance screening agents · DeFi onboarding routers · Marketing personalization agents · Airdrop quality screening · Governance participant verification
Unique advantage: Only provider delivering forward-looking behavioral predictions – the difference between a data retrieval layer and a decision intelligence layer
Free tier: Yes – individual wallet checks free; Prediction MCP via subscription

Add Behavioral Intelligence to Any AI Agent in Minutes

ChainAware Prediction MCP – Pre-Computed Wallet Intelligence via Natural Language

Your AI agent queries any wallet address in plain English and gets fraud probability (98% accuracy), behavioral profile, AML status, rug pull risk, and wallet rank – pre-computed, under 1 second, no blockchain expertise required. 18M+ profiles. 8 chains. 32 open-source agents on GitHub. SSE-based MCP compatible with Claude, GPT, and any LLM.

Get MCP Access Prediction MCP Guide

2. Moralis – Web3 AI Agent API (Raw + Indexed, 30+ Chains)

Data type: Indexed raw blockchain data – wallet balances, transaction history, NFT ownership, DeFi positions, token prices, historical data
Integration: REST API + MCP server + WebSocket + ElizaOS official plugin
Chains: 30+ (Ethereum, Polygon, BNB, Solana, Avalanche, Arbitrum, Optimism, and more)
Agent-ready: Well-indexed and structured – agent must still interpret

Moralis is the most AI agent-friendly raw blockchain data provider in 2026. The platform has explicitly repositioned around AI agent use cases – publishing an official ElizaOS plugin that lets developers integrate real-time blockchain data directly into ElizaOS-based agents, shipping a full MCP server implementation, and restructuring its documentation around agent-first use cases. The combination of 100+ API endpoints, 30+ chain coverage, and WebSocket streaming for real-time event delivery gives agents the raw material they need for trading bots, analytics tools, portfolio managers, and social media intelligence agents.

Moralis’s Wallet API and What It Returns

Moralis’s Wallet API is the centerpiece of its agent integration offering. A single API call against a wallet address returns native token balance, all ERC-20 holdings, NFT collection, complete transaction history, and computed portfolio P&L – across all supported chains simultaneously. This unified cross-chain wallet profile is immediately useful for any agent that needs to understand a user’s on-chain footprint. Moralis Streams push parsed contract events and transfer logs to webhooks or WebSocket clients in real time, enabling event-driven agent architectures where the agent acts on on-chain triggers rather than polling for data. For agents built on ElizaOS specifically, the official Moralis plugin reduces blockchain data integration to a configuration step rather than a development project. According to Moralis’s AI agent documentation , the platform supports trading bots, analytics tools, governance voting assistants, and fraud detection agents. For how Moralis-type raw data compares to predictive intelligence for DeFi use cases, see our Web3 Analytics Tools comparison.

Best agent use cases: Trading bots needing real-time token data · Portfolio management agents · NFT intelligence agents · Social media crypto analytics agents · Cross-chain wallet profiling
Unique advantage: Most complete AI agent integration story among Tier 1 providers – ElizaOS plugin + MCP server + 100+ endpoints
Limitation: Historical data only – cannot predict fraud, behavioral intentions, or future wallet behavior

3. Nansen – Smart Money Labeling and Wallet Profiling

Data type: Labeled and profiled blockchain data – smart money identification, wallet entity labeling, token flow analysis, portfolio profiling across 18+ chains
Integration: MCP + REST API + CLI (structured JSON)
Chains: 18+ including Ethereum, Solana, Base, Arbitrum, BNB, and others
Agent-ready: Well-labeled – significantly reduces agent interpretation burden

Nansen occupies a distinct position between raw data and behavioral intelligence: it delivers labeled blockchain data. Rather than returning a transaction history full of anonymous addresses, Nansen’s wallet profiling system identifies which wallets belong to recognized entities – exchanges, funds, known DeFi protocols, smart money traders – and labels their activity accordingly. A Nansen API response for a wallet address includes not just transaction history but entity labels, smart money classifications, and portfolio analytics that give agents meaningful context without requiring the agent to build its own labeling system.

Smart Alerts and Agent-Driven Event Detection

Nansen’s Smart Alerts feature is particularly valuable for event-driven agent architectures. When configured, Smart Alerts notify an agent the moment a tracked wallet executes a significant action – accumulating a new token, moving large positions between protocols, or withdrawing from liquidity pools. This real-time detection capability enables investment and risk management agents to respond to smart money movements as they happen rather than discovering them after the fact. Nansen’s CLI with structured JSON output makes it straightforward to pipe Nansen data directly into agent decision pipelines without HTTP complexity. For investment intelligence and compliance use cases, the combination of entity labeling, portfolio profiling, and real-time alerts positions Nansen as the strongest Tier 1 provider for institutional-grade agent applications. For how wallet profiling complements ChainAware’s behavioral predictions in a complete intelligence stack, see our Wallet Auditor guide and our Wallet Rank guide.

Best agent use cases: Investment intelligence agents tracking smart money · Risk management agents monitoring whale movements · Compliance agents verifying entity identities · Portfolio optimization agents
Unique advantage: Entity labeling and smart money classification – removes the anonymous-address problem for a significant portion of high-value wallet activity
Limitation: Labeled but not predictive – does not score fraud probability or behavioral intentions for the majority of unlabeled wallets

4. Dune Analytics – MCP Server for 100+ Chain Datasets

Data type: SQL-queryable decoded blockchain data – raw transactions, decoded smart contract events, wallet intelligence, DeFi positions, NFT activity, community-curated datasets
Integration: MCP server (launched 2025) + REST API + Dune Sim query engine
Chains: 100+ including ETH, SOL, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche, NEAR, zkSync, TON, TRON, Sui, Aptos, and more
Agent-ready: MCP enables natural language queries – but responses require interpretation

Dune’s MCP server launch is one of the most significant infrastructure developments for blockchain AI agents in 2025. The integration requires a single command-line entry and draws from existing Dune API credits – meaning any developer already using Dune can immediately give their AI agents access to 100+ chain datasets without additional setup. The practical capability is broad: an agent can query “Top 10 wallets accumulating RWA tokens in the last 30 days” or “Compare Uniswap vs Curve daily swap volume over the past 90 days” in natural language and receive structured analytical responses. The kind of research that previously required a dedicated blockchain analyst now happens conversationally. Additionally, Dune’s community-curated dataset ecosystem – tens of thousands of community-built dashboards covering protocol analytics, wallet intelligence, DeFi positions, and NFT activity – gives agents access to specialized intelligence that no single provider could build internally.

Dune’s Role in the Agent Data Stack

Dune excels at analytical queries – understanding trends, comparing protocols, identifying patterns across large populations of wallets. Consequently, it is most valuable for research and analytics agents rather than real-time decision agents. For an agent needing to answer “is this specific wallet a fraud risk right now?”, Dune requires building a custom query against its raw data – which demands significant blockchain analytical expertise. For an agent needing to answer “which protocols are seeing unusual wallet accumulation this week?”, Dune’s natural language MCP interface delivers the answer immediately. According to Dune’s official documentation , the MCP server covers all major EVM and non-EVM chains with decoded event data. For how analytical data layers complement behavioral prediction in complete agent architectures, see our Web3 User Segmentation guide.

Best agent use cases: Research agents analyzing blockchain trends · Protocol analytics agents · Market intelligence agents · Community analytics and governance research agents
Unique advantage: Broadest chain coverage (100+) of any provider; community-curated dataset ecosystem; natural language MCP queries
Limitation: Analytical rather than real-time – best for batch analysis rather than per-transaction decisions; requires significant query expertise for novel research questions

Free Behavioral Intelligence – No Complex Queries Needed

ChainAware Free Analytics – Behavioral Distribution of Your Users in 24 Hours

Before building complex data pipelines, understand who is actually connecting to your protocol. ChainAware Analytics delivers experience levels, risk profiles, and behavioral segment distributions for your connecting wallets via a 2-line GTM pixel. No SQL. No queries. No blockchain expertise. Free forever. The data layer that makes every agent decision smarter.

Get Free Analytics Analytics Guide

5. The Graph – Decentralized Protocol-Specific Subgraph Indexing

Data type: Decentralized indexed data via subgraphs – protocol-specific event data, customizable GraphQL queries, open and permissionless
Integration: GraphQL API + decentralized network of indexers
Chains: Ethereum, Polygon, Arbitrum, Optimism, and other EVM chains
Agent-ready: Moderate – requires subgraph development expertise; powerful once built

The Graph is the foundational decentralized indexing protocol that underlies much of Web3’s data infrastructure. Rather than providing a centralized API, The Graph operates a network of indexers who stake GRT tokens to serve subgraph queries – creating a permissionless, censorship-resistant data layer that any protocol can publish to and any developer can query. Subgraphs are custom data schemas that define what on-chain events to index and how to structure the resulting data, enabling extremely efficient queries against protocol-specific event logs that would be prohibitively expensive to reconstruct from raw chain data.

The Graph’s Role in Agent Data Infrastructure

For AI agents building on top of specific DeFi protocols – a lending agent on Aave, a liquidity management agent on Uniswap, a governance agent on Compound – The Graph’s protocol-specific subgraphs provide the most efficient and decentralized access to the exact events those agents need. A well-built subgraph exposes complex protocol state (user positions, liquidation thresholds, yield rates, governance proposals) in a single GraphQL query rather than requiring multiple RPC calls and manual data reconstruction. The decentralized nature also matters for agents that need censorship resistance – no single entity can block subgraph queries on The Graph. According to The Graph’s developer documentation , subgraphs are available for most major DeFi protocols. For how protocol-specific data complements behavioral scoring in DeFi agent use cases, see our DeFi Onboarding guide.

Best agent use cases: Protocol-specific DeFi agents needing efficient event queries · Governance agents · Decentralization-critical agent deployments · Developers already building subgraphs
Unique advantage: Decentralized and permissionless – no single point of failure or censorship; most efficient data access for protocol-specific use cases
Limitation: Requires significant development expertise to build subgraphs; no wallet behavioral intelligence or fraud scoring

6. Datai Network – Smart Contract Categorization Layer

Data type: Behaviorally categorized blockchain data – smart contracts labeled by function (lending, borrowing, NFT, bridging, gaming, RWA), wallet behavioral narratives, user behavior profiles
Integration: API data feeds + decentralized indexer network
Chains: Multi-chain EVM expanding
Agent-ready: Well-categorized – provides behavioral context missing from raw transaction data

Datai Network solves a specific and underappreciated problem in blockchain data infrastructure: the semantic gap between raw transaction data and agent-understandable behavioral context. When a blockchain explorer shows “0x4f…a2 interacted with 0x7d…c8,” it conveys no behavioral meaning – that address could be lending on Aave, minting an NFT, bridging to Arbitrum, or buying a gaming asset. Without knowing which smart contract category that interaction represents, an AI agent analyzing this transaction cannot construct a meaningful behavioral narrative about the user.

AI-Ready Intelligence Through Categorization

Datai’s machine learning models automatically identify, label, and categorize smart contracts at scale – translating raw transaction histories into structured behavioral narratives that read like descriptions rather than hex strings. A wallet that “interacted with 14 smart contracts across three chains” becomes “a user who has borrowed on two lending protocols, provided liquidity on Uniswap, bridged to Base twice, and purchased gaming assets on Immutable X.” This translated narrative is what Datai describes as “AI-ready intelligence” – data structured to the level of detail that agents need to make segment-based decisions without custom blockchain parsing. For more on Datai’s role as a behavioral context layer and its use in AI trading agents, see our X Space with ChainGPT and Datai. Datai’s approach is complementary to ChainAware: Datai provides behavioral context history (what the user did in the past), while ChainAware provides behavioral predictions (what the user will do next). For the full picture of how behavioral context enables DeFi personalization, see our User Segmentation guide.

Best agent use cases: DeFi personalization agents needing user behavior context · Cross-protocol user segmentation · Trading strategy personalization agents · Portfolio analytics needing semantic transaction understanding
Unique advantage: Solves the semantic gap between raw transactions and meaningful behavior – provides the “what was the user doing?” context layer
Limitation: Historical context only – does not predict future behavior or score fraud probability

7. Alchemy – Enterprise Node Infrastructure and Enhanced APIs

Data type: Enhanced raw blockchain data – wallet activity, NFT metadata, transaction history, webhooks, smart contract state, transaction simulation
Integration: REST API + WebSocket + Notify API + subgraph managed service
Chains: 18+ (Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, and others)
Agent-ready: Enterprise-grade reliability – most production-hardened infrastructure

Alchemy’s position in the blockchain data provider ecosystem is defined by enterprise-grade reliability rather than analytical breadth. As a Series C-backed company with OpenSea, Trust Wallet, and Dapper Labs as core clients, Alchemy has built the infrastructure layer that production-grade AI agent deployments depend on – the kind of infrastructure that can handle millions of API calls per day with sub-100ms latency and 99.9%+ uptime. For teams building agents where reliability and performance are the primary constraints, Alchemy’s combination of enhanced APIs and institutional-grade node infrastructure is the strongest option available.

Enhanced APIs That Go Beyond Standard RPC

Alchemy’s enhanced APIs go significantly beyond standard blockchain RPC endpoints. The NFT API fetches complete NFT metadata, ownership history, and collection data in a single call – eliminating the complex on-chain parsing that standard RPC requires. The Notify API delivers webhooks for wallet activity events, NFT transfers, and contract interactions across Ethereum, Polygon, Optimism, and Arbitrum – enabling event-driven agents that react to on-chain triggers rather than polling. The Trace API provides deep transaction-level analysis of how transactions interact with smart contracts and wallets, enabling agents that need to understand complex DeFi interaction flows. Additionally, Alchemy’s transaction simulation capability allows agents to preview the outcome of any transaction before broadcasting – a critical capability for agents making consequential financial decisions on behalf of users. For how Alchemy-type infrastructure supports compliance agent deployments in DeFi, see our DeFi Compliance Tools guide and our MiCA Compliance guide.

Best agent use cases: Production-grade agents requiring enterprise reliability · Transaction simulation agents · Event-driven agents on Ethereum and EVM L2s · Teams migrating from self-hosted nodes
Unique advantage: Most production-hardened infrastructure; transaction simulation; institutional-grade reliability and support
Limitation: Raw data only – no wallet behavioral intelligence, fraud scoring, or behavioral predictions

Deploy Behavioral Intelligence Agents Without Building from Scratch

32 Open-Source ChainAware Agents – Clone, Configure, Deploy

Fraud detection, AML screening, onboarding routing, growth segmentation, DeFi intelligence, governance verification – 32 MIT-licensed pre-built agent definitions on GitHub. Each integrates ChainAware’s Prediction MCP for immediate behavioral intelligence. Works with Claude Code, any Claude agent, GPT, and custom LLMs. No data pipelines to build.

View Agents on GitHub 12 Blockchain Capabilities Guide

Head-to-Head Comparison Table

Provider	Data Tier	Predictive?	MCP?	Chains	Agent-Ready?	Best For
ChainAware.ai	Tier 2: Behavioral predictions	Forward-looking scores	Prediction MCP	8 (ETH/BNB/BASE/POL/TON/TRON/HAQQ/SOL)	Pre-computed, no analysis needed	Fraud detection · AML · onboarding · personalization agents
Moralis	Tier 1: Indexed raw data	Historical only	MCP server	30+	Well-indexed, structured JSON	Trading bots · portfolio agents · ElizaOS agents
Nansen	Tier 1: Labeled data	Historical only	MCP + REST + CLI	18+	Entity-labeled – reduces interpretation	Smart money tracking · investment agents
Dune Analytics	Tier 1: SQL-indexed raw data	Analytical only	MCP launched 2025	100+	Moderate – natural language queries but needs interpretation	Research · trend analysis · protocol analytics agents
The Graph	Tier 1: Protocol-specific indexed		Limited	EVM chains	Moderate – requires subgraph dev	Protocol-specific DeFi agents · decentralized deployments
Datai Network	Tier 1.5: Categorized behavioral context	Historical only		Multi-chain EVM	Semantic context layer	Personalization · DeFi strategy agents needing behavioral context
Alchemy	Tier 1: Enhanced raw data		Via subgraph	18+	Enterprise-grade reliability	Production agent infrastructure · transaction simulation

Agent Use Case to Provider Mapping

Building Your Agent Data Stack

Most production-grade AI agent deployments in Web3 require data from multiple providers because different use cases require different data types at different speeds. The framework below maps three common agent architectures to their optimal data stack.

Architecture 1: Decision Agents (Fraud, Compliance, Onboarding)

Decision agents that need to make real-time binary or classification decisions about wallet addresses – allow or block, onboard or route, safe or risky – require pre-computed intelligence rather than raw data. The overhead of fetching raw data, building analytical pipelines, and computing risk scores on every wallet interaction is too high for real-time use cases. Consequently, the core data layer for decision agents is ChainAware’s Prediction MCP – fraud scores and behavioral profiles delivered in under a second via natural language query. Alchemy or Moralis serves as a supporting layer for transaction verification and data retrieval when specific historical context is needed. For the Enterprise API documentation covering batch and high-volume agent deployments, the learn guide covers all endpoints. For the complete decision agent architecture, see our Web3 Agentic Economy guide.

Architecture 2: Analytical Agents (Research, Trend Detection, Market Intelligence)

Analytical agents that synthesize information across large populations of wallets and long time horizons – identifying trends, comparing protocols, detecting accumulation patterns – prioritize breadth over speed. Dune’s MCP server provides the broadest chain coverage and most flexible analytical query capability through natural language. Nansen’s Smart Money labeling adds contextual signal to population-level analysis. Together, these two providers cover the analytical agent use case comprehensively. ChainAware’s Token Rank capability – which scores the behavioral quality of a token’s holder base – adds a uniquely powerful signal for market intelligence agents assessing token legitimacy. For how behavioral analytics supports population-level marketing intelligence, see our Web3 Marketing Analytics guide.

Architecture 3: Personalization Agents (DeFi UX, Onboarding, Marketing)

Personalization agents that tailor every wallet interaction – serving different content, routing to different product flows, or generating personalized messages based on wallet profiles – need both behavioral context (what kind of user is this historically?) and behavioral predictions (what will this user do next?). Datai provides behavioral context history through smart contract categorization. ChainAware provides forward-looking behavioral predictions through its Prediction MCP. Moralis provides the raw wallet data layer that both can reference. This three-provider combination creates a complete behavioral intelligence stack: historical context (Datai) + current state (Moralis) + predicted future (ChainAware). For the personalization agent architecture in detail, see our AI Agent Personalization guide and our User Segmentation guide. According to Anthropic’s Model Context Protocol documentation , MCP is rapidly becoming the standard integration layer for connecting AI agents to external data providers – with Moralis, Dune, Nansen, and ChainAware all shipping MCP servers in 2025. For additional context on the MCP ecosystem, see the official MCP servers repository .

Start With the Intelligence Layer

ChainAware Wallet Auditor – Full Behavioral Profile for Any Address

Before deploying any agent data stack, understand what behavioral intelligence looks like in practice. Paste any wallet address and get fraud probability, experience level, risk profile, behavioral segment, AML status, and Wallet Rank – all pre-computed, in under a second. Free. No wallet connection. No signup. This is what Tier 2 intelligence delivers.

Audit Any Wallet Free Full Product Guide

Frequently Asked Questions

What is the difference between blockchain data and blockchain intelligence for AI agents?

Blockchain data is what happened – transaction histories, token balances, protocol interactions, NFT ownership. An AI agent receiving raw blockchain data must still analyze it to produce a decision. Blockchain intelligence is what the data means – fraud probability scores, behavioral segments, predicted next actions, AML risk classifications. An AI agent receiving behavioral intelligence can act on it immediately without additional analytical processing. The distinction maps to agent performance: data retrieval agents require more computational work and latency per decision; intelligence-receiving agents make faster, better-calibrated decisions with less infrastructure overhead. ChainAware’s Prediction MCP delivers intelligence; Moralis, Dune, Nansen, and Alchemy deliver data.

What is Model Context Protocol (MCP) and why does it matter for blockchain AI agents?

Model Context Protocol (MCP) is an open standard developed by Anthropic that defines how AI agents connect to external data sources and tools. Rather than requiring custom API integration code for each data provider, MCP creates a standardized interface – an agent with MCP support can connect to any MCP-compatible data provider by simply declaring the connection. For blockchain AI agents, MCP adoption by major providers (Moralis, Dune, Nansen, ChainAware) means that integrating on-chain wallet data into any Claude, GPT, or open-source LLM agent requires configuration rather than custom development. The agent queries the MCP-connected blockchain provider in natural language and receives structured responses – exactly as it would query any other MCP tool.

Why can’t AI agents just query blockchain explorers directly?

Blockchain explorers (Etherscan, BscScan, Solscan) are designed for human consumption – their interfaces return HTML pages with formatted transaction data, not structured JSON for programmatic consumption. Furthermore, raw blockchain data from explorers requires the agent to parse hexadecimal function signatures, decode ABI-encoded parameters, resolve token addresses, and construct meaningful behavioral narratives from individual transactions. This work requires substantial blockchain engineering expertise that most AI agents do not have built in. Data providers like Moralis abstract this complexity by pre-decoding, indexing, and structuring the data into agent-consumable formats. ChainAware goes further by pre-computing behavioral scores so agents do not need to analyze the data at all.

Which blockchain data provider is best for a DeFi compliance agent?

Compliance agents have two core requirements: AML risk screening of wallet addresses and transaction monitoring for suspicious behavioral patterns. ChainAware’s Prediction MCP addresses both directly – AML screening returns risk status for any address in under a second, and the fraud detection tool provides 98% accurate behavioral risk scoring that identifies wallets likely to commit fraud before they act. Alchemy provides the reliable transaction data infrastructure for verifying specific transaction details when compliance records require it. For MiCA-aligned compliance specifically – the EU regulatory framework requiring AML screening and transaction monitoring for DeFi protocols – ChainAware’s combination of pre-execution screening and continuous behavioral monitoring is the most cost-effective implementation available. For the full MiCA compliance architecture, see our DeFi Compliance Tools guide.

How does ChainAware’s Prediction MCP differ from Chainalysis for AI agent use cases?

Chainalysis is a forensic and compliance intelligence tool designed primarily for post-incident investigation, law enforcement support, and enterprise VASP compliance. It excels at tracing the flow of already-identified illicit funds through transaction graphs, attributing addresses to known entities, and producing audit-quality compliance reports. ChainAware’s Prediction MCP is designed for real-time agent decision-making – predicting fraud probability before it occurs, not documenting it after. The practical differences: Chainalysis pricing is enterprise-scale ($100K+ annually); ChainAware’s Prediction MCP is accessible to individual developers and small protocols. Chainalysis requires weeks to integrate; ChainAware’s MCP integrates in minutes. Chainalysis identifies known bad actors from forensic databases; ChainAware predicts which unknown addresses will become bad actors from behavioral patterns. For the complete cost comparison, see our MiCA Compliance at 1% of Chainalysis Cost guide.

Sources: Grand View Research – AI Market Data · Moralis AI Agent API Documentation · Anthropic Model Context Protocol · The Graph Developer Documentation · Dune Analytics Documentation

The post Blockchain Data Providers Enabling AI Agent Access to On-Chain Wallet Data – Complete Guide 2026 first appeared on ChainAware.ai.