Before a single unit exists, the underlying asset is proven, scored, and cryptographically bound to the ledger. Nothing issues against an asset the ledger cannot vouch for.
Verification establishes that the real-world asset exists, is owned by the party claiming it, and is free of undisclosed encumbrance.
The pipeline ingests title records, custody statements, and chain-of-ownership documents and reconciles them against the issuing party's declared position. Discrepancies halt sealing rather than surfacing as warnings after issuance.
Liens, pledges, and prior security interests are captured as structured claims against the asset. An asset carrying an undisclosed charge cannot proceed to seal until the charge is recorded or released.
The token's legal claim on the asset is defined at verification, not assumed later. The governing instrument, jurisdiction, and enforceable rights are attached to the asset record so a unit always resolves to a specific legal entitlement.
Third-party valuers, custodians, and auditors sign their findings under their own keys. The record distinguishes what the issuer asserts from what an independent party has attested to.
Scoring turns verification evidence into a structured, machine-readable assessment that travels with the asset for its entire life.
Each required document class is tracked as present, missing, or stale. The score reflects the actual state of evidence rather than a one-time checklist marked at onboarding.
The valuation method, inputs, and date are recorded alongside the number. A mark-to-model figure is distinguished from a mark-to-market one so downstream holders know how the value was derived.
Jurisdictional, counterparty, and asset-class concentration are flagged at the point of sealing. Sovereign owners set the thresholds; the pipeline enforces them rather than negotiating them.
The score is a precondition, not a label. Assets below the owner-defined threshold are rejected from issuance, and the rejection itself is written to the record.
Sealing produces a tamper-evident cryptographic commitment to the verified asset using ML-DSA-65 under FIPS 204.
The seal is produced with ML-DSA-65 (FIPS 204), a lattice-based scheme designed to resist both classical and quantum attack. The evidence backing a token remains verifiable across the multi-decade life of long-dated assets.
The signing keys belong to the sovereign or institutional owner, not to Sovex. The party accountable for the asset is the party whose key seals it, and that key never leaves their control.
The verification package is canonicalized and hashed before signing, so the seal commits to an exact, reproducible representation of the evidence. Any later alteration of a document breaks verification of the seal.
No tokenized unit can be minted against an unsealed asset. The seal is the hard boundary between an asset under review and an asset eligible to back issued units.
Once sealed, the asset commitment is written into the tamper-evident ledger where it becomes the anchor every later lifecycle event references.
The seal is recorded as a ledger entry linked to its predecessor by hash, so the asset's admission to the system carries a verifiable position in an append-only history.
The sealed asset receives a durable on-ledger identity that issuance, servicing, and redemption all bind to. Every future unit traces back to this single anchor.
Assets requiring periodic revaluation or attestation carry scheduled re-seal obligations. A lapsed obligation is visible in the record rather than silently ignored.
External auditors verify the chain from the seal forward without trusting Sovex as an intermediary. The anchor is the point from which an independent party can reconstruct the asset's full lifecycle.