Cross-chain settlement evidence
One anchor identity, several chains, one schema — and an evidence tier attached to every single figure. Stellar is the keystone: the only chain here where settlement is proven from a replayable public ledger. Everything else is attested, derived, or honestly marked as not yet covered.
Cross-chain artifact unavailable
This page has nothing to show you yet.
It reads a generated cross-chain scan artifact. Nothing on this page is hardcoded, so rather than render an empty shell with plausible-looking zeros in it, it shows nothing.
The honesty ladder
Three tiers, in descending strength. The rule that matters: a tier is never inflated, and two tiers are never blended into one headline number without saying so.
What you are trusting on each path
Stellar has no consensus-layer interoperability standard — no IBC, no XCM, no canonical rollup bridge. Every way in and out rests on a third party of some kind, and they are not interchangeable. This is the reason the tiers above exist: on a chain with native interop it bridged carries its own proof, and here it does not, so the honest unit of information is not whether value moved but what you were trusting while it did.
Incidents are listed only where independently reported, with a source. An empty incident list means nothing has been reported — which is not the same as a path being safe, and this table must not be read as a safety rating.
Ranked by evidence
pickAnchor() sorts on PROVEN first, then ATTESTED, then DERIVED — so no
amount of custodial, derived evidence can ever outrank ledger-proven settlement. There is
deliberately no blended 0–100 score here; collapsing the tiers into one figure is exactly
what would let a guess pass for a measurement.
Per anchor, per chain
Four states, kept distinct on purpose: observed (scanned, events found), empty (scanned, nothing in the window), unresolved (no address curated for this anchor on that chain — which is not the same claim as "it did nothing there"), and failed (the scan broke, and says so rather than reporting a zero).
How this is produced: scripts/cross-chain-scan.ts resolves each anchor's
identity from its SEP-1 stellar.toml, runs every configured
ChainAdapter, converts each settlement event into an STP attestation, and
writes api/v1/cross-chain.json. The schema and the
tier definitions live in
docs/architecture/MULTICHAIN.md.