scale to a billion.
MARS-S extends the v1.0 protocol with a two-tier registry topology: a Global Anchor Layer that sees only roots, and a Regional Shard Layer that holds the bytes — wherever they were created.
Three-hop cascade
Most resolutions never leave the local shard. Misses propagate up to the regional cluster; only roots and revocations ever hit the global anchor layer.
- 01
Local shard
<12 ms · P50The shard your registry is pinned to. Holds the entries you publish, the entries you most frequently resolve, and a curated set of hot entries from neighboring shards.
- 02
Regional cluster
<48 ms · P95A federated mesh of shards in the same regional zone. On a local miss, the request fans out across the cluster. Most cross-org resolutions stop here.
- 03
Global anchor
<320 ms · tailThe Sigil chain itself. Holds only HMR/MHR/ENR identity records, revocations, and lineage roots. Authoritative, slow, never the hot path.
Shard map
Shards are organized by topological affinity — entries cluster with their likely consumers, not by geographic latitude. Reassignment is online and progressive.