SOVEX
CBDC Data Centers Sovereign AI Tokenization Deep Tech Architecture About Team Request access
Tokenization / Lifecycle / Issue on-chain

Issue on-chain.

Tokenized units are minted only against a sealed asset, under rules the ledger enforces rather than the issuer promises. Supply is a consequence of the record, not a claim about it.

Units are bound to a sealed asset at the moment of issuance

Issuance cannot begin without a valid seal, and every unit created is tied to the specific asset that backs it.

01

Seal precondition

The issuance engine refuses to mint against an asset that is not sealed and anchored. There is no path to create supply that skips verification.

02

Unit-to-asset lineage

Each issued unit references the sealed asset's on-ledger identity. Given any unit, the ledger resolves the exact asset, seal, and evidence package behind it.

03

Claim definition

The token's economic and legal rights are fixed at issuance: what the holder is entitled to, in what priority, and under which instrument. Holders acquire a defined claim, not an undefined exposure.

04

Terms in the record

Coupon, maturity, denomination, and transfer restrictions are encoded on-ledger at issuance. The servicing and redemption stages read these terms rather than re-interpreting a document.

Supply is enforced against the asset, not asserted by the issuer

The ledger caps issued units to the sealed asset's capacity so over-issuance is structurally impossible.

01

Capacity ceiling

Issuable supply is derived from the sealed asset's verified value and structure. Attempts to mint beyond that ceiling are rejected at the ledger, not caught in reconciliation later.

02

No fractional over-commitment

Fractional units sum to the whole; the engine prevents the same underlying value from being issued twice. One asset cannot silently back two token series.

03

Tranche and seniority

Where an asset supports multiple tranches, seniority and allocation are encoded so subordination is enforced by the ledger. Priority of claim is a property of the record, not a footnote.

04

Deterministic total supply

Total issued supply is computable from the ledger at any block, with no off-ledger adjustments. The number a regulator sees is the number the system enforces.

Only authorized keys can bring units into existence

Issuance authority is held by owners and their designated agents, exercised through post-quantum signatures the ledger checks.

01

Owner-authorized minting

Minting requires signatures from the keys the sovereign owner has designated for issuance. Sovex operates the engine but cannot issue on an owner's behalf.

02

ML-DSA-65 authorization

Issuance instructions are signed under ML-DSA-65 (FIPS 204), keeping the authorization step quantum-resistant across the life of long-dated programs.

03

Multi-party approval

Issuance can require a quorum of distinct keys, so no single official can create supply alone. The threshold is a policy the owner sets and the ledger enforces.

04

Signed issuance record

Every mint writes who authorized it, against which asset, and under what terms. The authorization is part of the permanent, hash-chained history.

Issuance is written into the tamper-evident chain

Each mint becomes an append-only ledger event that later lifecycle stages and external auditors read directly.

01

Hash-chained mint event

Issuance is recorded as an entry linked to its predecessor by hash. The creation of every unit sits in a verifiable, ordered history.

02

Atomic issuance and allocation

Minting and first allocation to holders settle as a single atomic operation. There is no interval where units exist unassigned or allocations reference units not yet created.

03

In-nation residency

The issuance record and its backing data remain within the owner's jurisdiction. Supply is created and held where the owning state's law and infrastructure govern it.

04

Reconstructable from genesis

An auditor can replay the chain from the asset seal through issuance and confirm supply independently. Trust rests on the record, not on Sovex's assurances about it.

Build it sovereign.

Talk to us about issue on-chain in a sovereign deployment.