One record substrate under every function
What makes a record from these functions checkable, one line each.
Records are hash-linked, so a removed or reordered entry shows.
What the register says
Sealed records written from 24 September 2026, 11:30 NZST are hash-linked, so a deleted or reordered entry in the middle of a history can be detected.
Limits and dates for each: EST-12.
Time stamps come from European authorities; the daily estate root carries two.
What the register says
Time stamps from outside time-stamping authorities under RFC 3161 are in use: Certum (Poland) stamps records, and the Portuguese state's Cartão de Cidadão authority stamps the estate root. The published estate-root index shows both stamps on every root from 4 October to 8 November 2026 (36 of 36).
Per-record time stamps come from Certum (Poland), a non-qualified service; the daily estate root also carries a stamp from the Portuguese state's Cartão de Cidadão authority (EST-10).
The Gateway checker holds five authorities’ keys, Portugal’s and the qualified ArubaPEC’s among them.
What the register says
The offline checking program verifies a stamp from any of five European time-stamping authorities: Certum (Poland), BOSA (Belgium), CESNET (Czechia), the Portuguese state's Cartão de Cidadão authority and the qualified ArubaPEC (Italy). It needs no account and no network.
Limits and dates for each: GTW-08.
Each checking program is published with its SHA-256.
What the register says
Each offline checking program is published at mysovereignty.digital/downloads/ with its SHA-256, so a reader can confirm that the file they run is the file MDSL published.
A decision record can be exported with its approvals, receipt and events, and an offline checker (Node 20, no network, no product installed) verifies the export against a bundle of public keys.
A second signature, ML-DSA-65, on four kinds of record, switched on per account.
What the register says
A second signature using ML-DSA-65 (NIST FIPS 204) is added to Provenance™ seals, Governance API receipts, Email Decision Record™ receipts and proof-chain compaction summaries after the classical signature, so a record carries both; the downloadable verifier checks it.
Limits and dates for each: EST-37.
Signing keys sit on a separate host; a 2-of-3 split-key scheme is built and available on request.
What the register says
A separate signing host, operated by MDSL, holds the signing key for each Village™ moved onto it. A 2-of-3 split-key scheme (FROST: the key is generated in shares and no whole key ever exists) is built, tested, deployed to both servers and available on request: a Village is moved onto it by a key ceremony among its three key holders.
Limits and dates for each: EST-16.
One hash a day, the hash of the estate root, is anchored on Midnight mainnet.
What the register says
One value a day, the hash of the signed daily estate root, is anchored to an insert-once contract on Midnight mainnet (contract 517a75cf…5de7, deployed 12 Nov 2026); the ledger holds a date key and a hash, and no personal or tenant data.
A daily hash of the estate root is anchored on the Midnight main network (EST-29); business records stay on MDSL infrastructure in New Zealand and the EU. Village Gateway is built so that, where Gateway anchoring is switched on for a Village, each of its Gateway receipts is a leaf in that Village's sealed day root, and a proof file links each receipt to the anchored hash; that path is built and tested and has not yet been run on the main network (GW-57).
Records stay in New Zealand and France; no US-owned provider holds them.
Every signing key is MDSL’s today. A sealed record shows what was signed and when, not that its content was true.