How it works
A deterministic path from address list to day-cut report.
Every stage is rebuildable from the layer below. Providers are swappable. Spend is visible before you commit.
- 01Import
Import
CSV, XLSX, or paste addresses. Network detection and validation before anything runs.
- 02Load
Load
Pull full on-chain history through provider adapters with budgets, checkpoints, and retries.
- 03Clean
Clean
Spam and noise rules mark junk without deleting evidence. Balance-affecting events stay.
- 04Archive
Archive
Daily netting and balances in your timezone — the ledger slice finance already expects.
- 05Report
Report
Portfolio, movement, and point-in-time exports in CSV, JSONL, or XLSX.
Step 01
1. Bring wallets in
Upload a spreadsheet or paste addresses. Map columns to ownership, venue, counterparty — or any dimension you need. Invalid and ambiguous rows surface before spend.
Step 02
2. Confirm cost & run
See an estimate for initial backfill and ongoing refresh. Set a budget ceiling. Jobs checkpoint so restarts don’t re-bill the same page twice.
Step 03
3. Process in layers
Raw provider payloads stay hashed and intact. Cleaning rules flag dust spam and noise. Archiving nets intra-day offsets and stores balances in your archive timezone.
Step 04
4. Operate the registry
Track each wallet through loaded → cleaned → archived → export-ready. Build slices, share URL state, and export only what the period requires.
Ready to run this on your wallets?
We’ll map networks, history depth, and refresh — then send a custom quote.