Reference
The Flow Atlas
Our living reference for how we read on-chain structure — corridor types, cluster labels, and pool-depth signals used across every engagement.
The Flow Atlas is not a product you subscribe to. It is the methodological backbone our analysts reference when producing mapping reports and briefings. Clients receive relevant Atlas excerpts with each engagement; this page summarises the framework so you know what to expect before scoping a project.
Corridor taxonomy
We classify capital paths into primary corridors (direct pool-to-pool), bridge corridors (cross-chain via known endpoints), and dispersion corridors (single source to multiple sinks). Each type carries different predictive weight depending on network congestion and pool depth.
Cluster labels
Wallet groups receive provisional labels — accumulator, distributor, dormant, rotating — based on net flow direction over rolling windows. Labels are revised when behaviour crosses thresholds defined in the Atlas, not on single transactions.
Pool depth signals
Liquidity level shifts are measured relative to each pool's 30-day median, not absolute TVL. A 15% depth contraction at a thin pool may matter more than a 5% shift at a deep one. The Atlas documents these relative thresholds per venue type.
Bridge endpoints
Known bridge contracts are mapped to corridor entry and exit points. Delayed settlement patterns — where funds sit in bridge contracts longer than typical — are flagged as potential pre-positioning signals.
Time horizons
Corridor reads are tagged by decision horizon: intraday (0–24h), swing (2–14 days), and structural (15+ days). Mixing horizons in a single briefing creates noise; we separate them by default.
Revision log
The Atlas is updated when network behaviour shifts materially — new bridge deployments, major pool migrations, or changes in cluster funding patterns. Clients on retainer receive revision notices.
Commission a mapping using this framework Ask a methodology question