Base mainnet · read-only · no wallet
Who funded the wallets behind this token's volume?
Dervyx reads public Base data for one token and one block window, maps how the trading wallets were funded, and issues a certificate you can re-verify by hash. It reports observed relationships, not accusations.
Anomaly certificate
CLUSTER_LINKED_SHARE_ABOVE_THRESHOLD
- Observed share
- 10/16 swap events (62.50%) via shared unknown roots
- Coverage
- 100.00% attributed (4/4 origins), funding complete
- Clusters
- 1 coordination, 1 known-root exclusion (router separated)
- Report hash
- cb5d256b9eeda3216a3499f88b3f94df9800953a…
Shared funding is evidence of a relationship, not proof of intent, ownership, coordination, or wrongdoing. This report is not proof of wash trading.
A real certificate over an example dataset. The numbers and hash above replay-verify.
Deterministic
Same token and window give the same hash, every time.
Read-only
No wallet, no transactions, no signing.
Source-linked
Every funding edge cites an on-chain transaction.
Reproducible
Download the report and replay its hash.
Honest
Thin coverage returns a non-verdict, never a forced label.
Base-native
Canonical Uniswap v4 swaps and funding transfers.
Certificate
Every run is a certificate.
Not a dashboard number you have to trust. A single, canonical document with a stable hash, carrying the verdict, the exact share, the coverage it was measured against, and the funding evidence it rests on.
- Verdict
- ANOMALY, CLEAN, UNKNOWN_ROOTS, or INSUFFICIENT_DATA, as text.
- Observed share
- Numerator and denominator of swap events, with the window.
- Coverage
- How many trading origins were attributed, and funding status.
- Exclusions
- Known routers and exchanges, separated and named.
- Report hash
- A SHA-256 over the canonical JSON that anyone can replay.
Funding graph
Follow the funding, two hops back.
Dervyx traces each trading wallet to the source that funded it. When several wallets share one unknown root, that is the signal. Known routers and exchanges are separated, never counted as coordination.
Wallets at the top, the shared unknown root at the bottom. Hover a wallet to trace it.
Evidence, not accusations.
Dervyx surfaces observed relationships for a person to judge. It never claims proof of wash trading, ownership, or intent, and it never forces a verdict on incomplete evidence.
Verdicts
Four honest verdicts.
Partial coverage is never labeled clean. Switch between real certificates for each outcome.
A material share of swap activity traces to a shared unknown root.
Anomaly certificate
CLUSTER_LINKED_SHARE_ABOVE_THRESHOLD
- Observed share
- 10/16 swap events (62.50%) via shared unknown roots
- Coverage
- 100.00% attributed (4/4 origins), funding complete
- Clusters
- 1 coordination, 1 known-root exclusion (router separated)
- Report hash
- cb5d256b9eeda3216a3499f88b3f94df9800953a…
Shared funding is evidence of a relationship, not proof of intent, ownership, coordination, or wrongdoing. This report is not proof of wash trading.
Workflow
How an investigation runs.
- 01
Scope
One token and a fixed Base block window. You get a reproducible request identity before any chain read.
- 02
Evidence
Canonical Uniswap v4 swaps and the funding transfers behind each trading wallet, over public Base RPC.
- 03
Certificate
The deterministic engine computes the verdict, the share, coverage, and a stable hash.
- 04
Verify
Download the report and replay its hash, in the browser or from the command line.
Technical proof
You do not have to trust it. Check it.
Every certificate carries the canonical JSON it was hashed from. Recompute the hash and it matches. Change a single field and it fails. Same scope and config, same hash.
Canonical JSON (head)
{"coordinationClusters":[{"id":"coord_73234a5547437c9b","linkedSwapEvents":10,"rootAddress":"0xbBbBBBBbbBBBbbbBbbBbbbbBBbBbbbbBbBbbBBbB","rootClass":"unknown","sampleSourceUrls":["https://basescan.org…SHA-256
cb5d256b9eeda3216a3499f88b3f94df9800953abb2293cb50a06e1805fbbaf1
- Replay in the browser. The tool re-runs verification and shows a match or a mismatch.
- Replay on the command line. node scripts/verify-report.mjs report.json
- Tamper detection. Any edit to the report changes the hash and fails the check.
- No shields or seals. The proof is the reproducible document, not a badge.
Agent
AI proposes a path. The engine owns the verdict.
When a model is configured, it picks one allowlisted investigation branch from a sanitized summary. It never sets a number or the verdict, and it always has a deterministic fallback.
Sources
Built on public Base data.
Run an investigation.
One token, one block window, one certificate you can re-verify.
example report cb5d256b9eeda3216a3499f8…