INKG Sovereign POST-QUANTUM ATTESTED

Audit our reserves yourself.

Every figure below comes from a live sovereign source — token supply is read on-chain (totalSupply()), mining metrics from the live ledger, verified reserves from the bank ledger. The whole snapshot is canonicalized, SHA-256 hashed, and signed with ML-DSA-65 (NIST FIPS-204 post-quantum), then anchored on-chain (MameyNode 20022). Tamper-evident and impossible to forge, even by a quantum computer. No trust required — verify it live below.

POST-QUANTUM ATTESTED · ML-DSA-65
HONEST RESERVE POLICY (Law #8): token supply is the real on-chain totalSupply() — anyone can query the contract themselves. Physical/backing reserves count only VERIFIED, auditable assets; unverified/pending assets are disclosed separately and never summed into the total. A modest real number beats an inflated one. No invented figures.
—Total verified reserves (USD)
ML-DSA-65Post-quantum signature (FIPS-204)
—Anchored at MameyNode block

Sovereign token supply — read live on-chain

loading on-chain supply…

Source: eth_call totalSupply() on chain 20022 (sovereign EVM). You can query these contracts yourself — the numbers here are exactly what the chain returns. WMP = market-priced mining token; WUSD = 1:1 USD stable (on/off-ramp).

Sovereign mining ledger — live

loading mining…

Source: live /api/mining/stats (sovereign mining ledger). Blocks, tokens minted, USD value and active miners are read at snapshot time.

Verified reserves — real assets on the ledger

loading reserves…

Population & the attestation — signed & anchored

This snapshot's post-quantum proof

The entire snapshot above is canonicalized to JSON, SHA-256 hashed, and signed with ML-DSA-65 (FIPS-204). The signature + hash are stored in the additive table reserve_attestations and the hash is anchored on-chain (MameyNode 20022). Anyone can recompute the SHA-256 of the published snapshot and verify the signature.

attestation —
algo —
snapshot_hash (SHA-256) —
chain block —
anchor_tx —
generated —

Verify this proof yourself

Click Verify to re-verify the ML-DSA-65 signature live against the sovereign pqc-service and run a tamper test (altering the sealed hash must be REJECTED). Click Re-hash to recompute the SHA-256 of the exact published snapshot in your own browser and confirm it matches the sealed hash — no server needed.

Verify calls /api/pqc/reserves/verify, which re-verifies the ML-DSA-65 signature (FIPS-204) and demonstrates tamper rejection — zero third parties (Law #16). The browser re-hash independently confirms the data equals what was signed.