SOVEX
CBDC Data Centers Sovereign AI Tokenization Deep Tech Architecture About Team Request access
Sovereign CBDC / Issuance & ledger / Non-custodial keys

Non-custodial keys.

The state holds the root signing keys to its own currency. There is no vendor key, no recovery backdoor, and no override path — sovereignty over money is a cryptographic condition, not a contractual promise.

The issuer is the sole holder of monetary authority

Root authority over the currency lives inside the central bank's own custody, and the engine is built with no place for anyone else's key.

01

State-held root keys

The signing keys that authorize issuance and top-level policy belong to the issuing authority and are generated and stored in its own environment. The vendor never sees the private material.

02

No vendor key of any kind

The system contains no supplier-controlled key that can mint, move, freeze, or reverse value. There is nothing for a vendor to lose, be compelled to surrender, or be coerced into using.

03

No recovery backdoor

There is no master seed, escrow key, or hidden recovery path that reconstitutes the state's authority. Key loss is a sovereign operational responsibility, not a lever held by a third party.

04

Custody is the owner's choice

The issuer decides where and how root keys live — HSMs, air-gapped ceremony, quorum devices — because the engine only ever verifies signatures, never holds the secrets that make them.

The engine cannot act without the owner's signature

Every state-changing operation requires a valid signature from the authorized key, and no code path exists to bypass that check.

01

Signature-gated state changes

The ledger accepts a transaction only if it carries a valid signature from a key with the authority for that action. An unsigned or wrongly-signed instruction is rejected by the protocol, not merely logged.

02

No administrative shortcut

Operations, support, and infrastructure roles can run the engine but cannot forge authority. There is no maintenance mode that lets an operator move value the keys did not authorize.

03

Compulsion resistance

Because the vendor holds no key, legal or physical pressure on the vendor yields nothing that can touch the currency. The only party who can act on the money is the party that holds the state's keys.

Rotation and revocation belong to the sovereign

The full lifecycle of keys — creation, delegation, rotation, and retirement — is exercised by the owner as signed on-ledger acts.

01

Owner-driven rotation

The issuer can rotate signing keys on its own schedule by signing a rotation with the outgoing authority. The chain records the handover so continuity of authority is provable end to end.

02

Scoped delegation

The root authority can delegate narrow, revocable powers to subordinate keys — for example, operational issuance within policy limits — without ever exposing the root itself.

03

Provable revocation

Revoking a key is an on-ledger event, so the exact moment a key lost authority is part of the permanent record and any transaction signed after that point is invalid.

04

Quorum ceremonies

The design accommodates multi-party control, so no single official can exercise root authority alone. Sensitive acts can require a threshold of independent signers.

Keys built to outlast the cryptographic era they were born in

Sovereign money must remain secure for decades, so signing authority is anchored in post-quantum cryptography from the ground up.

01

ML-DSA-65 signatures

Authority is asserted with ML-DSA-65 under FIPS 204, a lattice-based scheme standardized for resistance to both classical and quantum attack.

02

Harvest-now defense

Because signatures are post-quantum today, an adversary recording traffic now cannot forge a state signature later when quantum hardware matures.

03

Long-horizon custody

The lifecycle and rotation model lets the issuer migrate keys as standards evolve, so the currency's authority is never trapped in a single generation of cryptography.

Build it sovereign.

Talk to us about non-custodial keys in a sovereign deployment.