The settlement layer
for the rest of the chains.
Settler resolves every cross-chain transaction to a single, signed coordinate on the canonical map. Eight chains anchor to the same root. The auditor reads the same line you do.
Four panes,
eight chains.
Live coordinates, treasury, anchor pulse, fee chart. Every pane is signed at the source — auditor reads the same line you do.
Three primitives.
One map.
One settlement, one signed point.
Settler resolves every transaction to a single, signed coordinate on the canonical map — chain ID, block height, log index. The receipt is portable across any indexer or subgraph.
Eight chains, one finality root.
Every supported chain anchors its finality root to Settler. Cross-chain reads return the canonical state at depth 12 or better, with the anchor proof in the same response.
Trace any value, end-to-end.
Walk a token from origin to current bearer across any chain it has touched. Settler returns the full path, with each leg signed by the chain that handled it.
Trustless map
vs CEX gazetteer.
Five places where a single signed coordinate beats a chain-specific gazetteer. The data is public — we just made the map portable.
“Settler is the first cross-chain index our compliance team accepted on the first call. The signed coordinates put the audit on the chain itself.”
Per-coordinate
pricing.
Pay for the coordinates you query. No per-chain charge, no per-seat charge, no archive surcharge. Predictable to the request.
Public coordinate lookup · 5 req/s · 7 day archive.
- +1 API key
- +Coordinate lookup
- +Last 7 days archive
- +Discord channel
Cross-chain provenance, signed receipts, full archive.
- +10 API keys
- +Cross-chain provenance
- +Signed coordinate receipts
- +Anchored finality reads
- +Slack + webhook alerts
- +8h SLA
Dedicated map shard, custom anchors, attested.
- +Unlimited keys
- +Dedicated map shard
- +Custom chain anchoring
- +On-prem option
- +1h SLA · 24×7
- +Trail of Bits attestation
Mechanics & custody.
Coordinates, anchors, finality, custody — every question your protocol team and your auditor will ask in the same call.
A coordinate is the tuple (chain ID, block height, transaction index, log index) — the canonical identifier of a single on-chain event. Every Settler response carries the coordinate for every record.
Protocol upgrades.
Avalanche C-chain anchoring is now live — eight chains anchored to the same map.
Cross-chain lineage now resolves wraps and unwraps as a single span on the map.
Coordinate format upgraded to CCTP-3 — signed, portable, indexer-neutral.
Map shard latency now sub-50 ms p99 across every supported chain.
The map is open.
Connect a wallet, settle.
No per-chain indexer, no chain-specific gazetteer, no manual reconciliation. Just one coordinate per settlement, signed by the chain that handled it.