Method
How the data is collected, verified and checked
Swaps are read from public JSON-RPC or your own endpoints, proven complete for every block range and cross-checked before anything is published.
Collection and verification
A protocol family is supported only after its decoded swaps matched transaction receipts exactly on several networks. Uniswap v4 is verified differently: its pools share one contract and can carry hooks, so each pool is verified on its own, and only individually verified pools are ingested. PancakeSwap Infinity pools on BNB Smart Chain are verified the same way. A pool is ingested only if its factory is one we have recorded with receipt evidence.
On BNB Smart Chain, collection runs forward only: windows starting more than 8 days (192 hours) ago are refused, and every window needs two endpoints serving its first block. On Solana and TON, swaps from pinned pools are reconciled exactly against the pools' token balances or reserves.
Three stages
Each stage has its own checks. Nothing reaches a report or an AI answer without passing the stage before it.
1. Verified data
Ingestion runs prove block coverage, confirm empty answers with a second provider and publish to ClickHouse only after quality gates pass. USD comes from stablecoin legs or an hourly price feed configured for the installation; unvalued swaps are never counted as $0.
2. Analytics and findings
Covered-hour metrics, window comparisons and an anomaly engine with frozen baselines. Reports state exactly which pools and hours they cover.
3. Evidence-grounded AI
The AI phrases answers from the verified facts of each question. Every number must match a fact the sentence cites; anything unproven is replaced by a clearly labelled deterministic answer.
Every finding answers five questions
Each anomaly finding comes with an Evidence Card built only from stored data, with the same five sections in the application, the API and every report export.
- What was observed? The metric and its unit, the observed value against the expected baseline, and the window in UTC.
- Where is the evidence? Network, chain id and the token's contract; the block range; each measured pool with its protocol and decoder family; the swap count and the five largest transactions; the RPC providers and ingestion runs covering the window.
- How was it computed? The method and its version, the baseline window and value (frozen when the anomaly starts), the parameters and the detector's facts.
- How much can we trust it? Hours expected against hours fully covered, every gap, the checks that passed, and the caveats and alternative explanations.
- How can it be checked independently? The detection SQL with its SHA-256, and a recipe for any public JSON-RPC node that needs no access to our database.
Evidence Cards cover anomaly findings on the EVM networks. Solana and TON entries have coverage and verified swaps, but no anomaly findings yet. Findings describe the verified pools that were measured, never a token's whole market, and none is an accusation.
Coverage
Networks
Ethereum, Arbitrum One, OP Mainnet, Base and BNB Smart Chain; collecting: Avalanche C-Chain, Monad, Solana and TON.
Verified protocol families
- Uniswap v3-style
- Uniswap v2-style, including PancakeSwap v2
- Solidly (Velodrome/Aerodrome v2)
- PancakeSwap v3
- Recorded factories only
Solana and TON venues
- Raydium CPMM and CLMM, Orca Whirlpool, Meteora DLMM and DAMM v2, PumpSwap (Solana)
- STON.fi v1 and v2, DeDust (TON)
- Pinned pools only; no anomaly findings yet
Individually verified pools
- Uniswap v4: each pool verified on its own; hookless native-currency pools (ETH, MON) included, their native leg reconciled from call traces
- PancakeSwap Infinity (BNB Smart Chain): each pool verified on its own
Not counted
- Unrecorded factories and forks
- v4 and Infinity pools without a verification record
- v4 pools with hooks and a native currency, or with hooks that change swap amounts
- Infinity pools with native BNB, any hook or a dynamic fee
- Other networks and venues
What is verified, and what is not yet
We separate what has been tested on real data from what is integrated, experimental or not supported.
| Capability | Status |
|---|---|
| Ingestion, token explorer, anomaly engine, reports and window comparisons on Ethereum, Arbitrum One, OP Mainnet and Base | Tested on real data |
| Ingestion and token analysis on BNB Smart Chain, collected forward only (windows starting more than 8 days ago are refused) | Tested on real data |
| Uniswap v3-style, Uniswap v2-style (including PancakeSwap v2), Solidly-style and PancakeSwap v3 decoders, for recorded factories only (decoded swaps matched transaction receipts exactly) | Tested on real data |
| Uniswap v4 and PancakeSwap Infinity (BNB Smart Chain): only pools with an accepted verification record (PoolId/PoolKey match, accounting rules, two-provider agreement, exact receipt or settlement reconciliation) | Tested on real data, per pool |
| Solana: catalog collection of pinned Raydium, Orca, Meteora and PumpSwap pools (swaps reconciled exactly against token balances); no anomaly findings yet | Collecting; experimental |
| TON: catalog collection of pinned STON.fi v1/v2 and DeDust pools (two independent providers per window, reconciled against pool reserves); no anomaly findings yet | Collecting; experimental |
| Avalanche C-Chain: Uniswap v3, LFJ v1, Pangolin v2 and Pharaoh v3 factories recorded with receipt evidence; catalog tokens collecting since 29 Oct 2026 | Collecting; available after the 72-hour verification period |
| Monad: Uniswap v2, Uniswap v3 and PancakeSwap v3 factories recorded with receipt evidence, Uniswap v4 per pool; catalog tokens collecting since 29 Oct 2026, with history from 23 Oct 2026 | Collecting; available after the 72-hour verification period |
| Uniswap v4 and PancakeSwap Infinity pools without a verification record; v4 pools with hooks and a native currency, or with hooks that change swap amounts; Infinity pools with native BNB, any hook or a dynamic fee; unrecorded factories and forks | Not supported |
| Other networks | Not offered |
Limitations
- Only the listed networks, verified protocol families and individually verified pools are analysed, and only pools that were discovered and ingested. Other venues are not counted, so no figure covers every venue where a token trades.
- Pool-event volume counts a routed trade in every ingested pool it passes through. Transaction-net volume is reported separately.
- The research examples use public blockchain data collected by the application; USD values are omitted because they depend on an external price feed. Protocol, token and network names describe the data analysed; they do not imply any affiliation or endorsement.
- WATAM DeFi Intelligence is analytics and research software. It is not investment advice, makes no promise of trading or investment outcomes, and is not a regulatory certification.
The public catalog lists each tracked token with its coverage window; EVM entries are refreshed every 12 h, TON every 3 h and Solana hourly. See the token catalog.
Reproducibility
Every figure carries its coverage, its valuation method and the SQL behind it, so analysis can be reproduced, reviewed and shared. For an anomaly finding, the Evidence Card gives the detection SQL with its SHA-256, and a recipe for any public JSON-RPC node that needs no access to our database.
USD values are not part of the evidence.