Every partner signs the Charter in their own language. Every signature is sealed into an append-only cryptographic ledger. The wall of signatories, by country, is the living proof that the message is traveling.
The prototype above is real — the hashes are genuine SHA-256, computed live and chained. Here's what turns it into production infrastructure on your existing ledger spine.
Each signature is an immutable entry. The prevHash field links it to the entry before, forming the chain; changing any past record breaks every hash after it.
Reuse the Ed25519 / SHA-256 ledger you already built. Each entry is hash-chained for order and Ed25519-signed by the registry key so signatures are provably authentic, not just append-only.
Production writes to the shared @bbg/ledger; the public wall reads from it. The browser prototype proves the hashing; the server holds the signing key.
The Charter text is versioned (charterV) and stored per language through the Localization Engine. A signer reads and signs in their own language, but every record points to the same canonical Charter version — so a Polish signature and an English one attest to the identical text.
New languages are a content add, not a code change.
The wall groups signatories by country and renders live from the ledger — the visible, shareable evidence of reach. Each card can link to its ledger entry so any visitor can verify the chain themselves.
It doubles as the map's data source: countries light up as signatures arrive.
The name "Charter Registry" and any public "tamper-proof / immutable" language clear through McAuliffe (trademark) and Olson (claims). Signatory personal data stays minimal and consented — privacy-first, the same standard as Harbor. The registry itself is text-only and export-safe; it does not carry the gated Tier-3 crypto tooling across borders.