How the real crawler will work
PlannedThe planned design for tracing real funding networks: first-funding links, caching, traversal and stop conditions.
Planned Not built.
First-funding links#
Each wallet gets one upward edge: the address that sent it its first native funds. First funding is immutable, so every link can be cached permanently once read.
Traversal#
- Upward: from each holder, follow first funders until a stop condition.
- Downward: from each ancestor found, list the wallets it funded first.
Stop conditions#
| Condition | Why |
|---|---|
| Contracts | Contracts do not have a meaningful first funder |
| Bridges and exchanges | They fund huge numbers of unrelated users |
| Hubs above a threshold | Any address funding more than a set number of wallets is treated as infrastructure |
| Dust | Tiny transfers are ignored, they are often spam |
| Depth cap | Traversal stops after a maximum number of hops |
| Node cap | Traversal stops at a maximum network size |
Token grouping#
Holders that share an ancestor below the hub threshold are grouped. The network view shows the groups as fans hanging off shared tendrils.
Coverage reporting#
Every trace will report how much it covered: wallets resolved, wallets skipped and why, and which stop conditions fired. The stats strip already shows "Coverage: Synthetic: not a trace" in its place.
The crawler plugs in behind the same data interface the synthetic generator uses. See Interfaces.
Last updated 2026-09-28