INKG · Post-Quantum Bank & Blockchain Live PQC service · NIST FIPS 203/204

The first sovereign bank & blockchain that survives the quantum era.

When quantum computers break RSA and ECDSA, every classic bank, wallet and chain becomes readable and forgeable. INKG already runs on real NIST post-quantum cryptographyon our own sovereign infrastructure, zero third parties, zero foreign tax.

ML-KEM-768 (CRYSTALS-Kyber) key exchange + ML-DSA-65 (CRYSTALS-Dilithium) signatures — delivered as a sovereign service. Open the live lab →

ML-DSA-65Signature standard
ML-KEM-768Key encapsulation
Wallets PQC-protected
PQC service

◆ Live Quantum Shield — reacting to real posture

🛡️ LIVE QUANTUM SHIELD

LIVE ML-KEM-768 · ML-DSA-65
guarded node   protected wallet   quantum probe (absorbed) wallets · anchors · readiness /100 · service

⚛️ Quantum Attack Simulator — watch Shor's algorithm break RSA, then fail against us

⚛️ Quantum Attack Simulator

Educational demo · real mathematics

This is a visualization of a real mathematical fact, not live quantum hardware and not fake telemetry: a large fault-tolerant quantum computer running Shor's algorithm would factor RSA-2048 and forge ECDSA — but Shor's algorithm has no traction on lattice problems (Module-LWE / Module-SIS), which is exactly why NIST standardized ML-DSA-65 and ML-KEM-768. Launch the attack and watch the difference.

Same attack, two targets. One breaks. One holds.
🏦Classic crypto (the whole internet today)
RSA-2048 · ECDSA · secp256k1
Shor factorizationattack progress
🦅INKG sovereign crypto
ML-DSA-65 · ML-KEM-768 (lattice)
Shield integrityholding
Ready. Press “Launch quantum attack”.
Why RSA breaks and lattice doesn't. Shor's algorithm turns factoring and discrete-log into a period-finding problem a quantum computer solves in polynomial time — that kills RSA, ECDSA, ECDH, secp256k1. Lattice schemes (ML-DSA-65, ML-KEM-768) rest on Module-LWE / Module-SIS, which are not hidden-subgroup problems, so Shor gives no speedup and the best known quantum attack is essentially as slow as the classical one. That is the entire reason INKG runs on lattice cryptography — and you can prove it yourself in the live lab below.

📡 Live post-quantum activity

📡 Sovereign PQC operations — live LIVE sigs 0 · wallets · anchors

Each “keypair minted live” line is a real ML-DSA-65 keypair generated on our sovereign node this second (proof the service is up). Wallet and anchor totals are the real live figures from the sovereign bank.

Live sovereign quantum-safe posture

/ 100
Readiness score— / 6 controls safe
Mamey anchors signed (ML-DSA-65)
PQC service (FIPS 203/204)

Coverage by component

  • loading real posture…
Migration is prioritized for long-lived assets (anchors, custody) first — numbers are read live from the sovereign bank, not estimates.

The quantum threat is real — and it is a "harvest now, decrypt later" problem

☠️ What breaks under quantum

RSA · ECDSA · ECDH · secp256k1 — the cryptography behind virtually every bank, wallet, TLS session and blockchain today. Shor's algorithm on a large-enough quantum computer factors and forges these. Adversaries are harvesting encrypted traffic now to decrypt it later, and any long-lived signature (bonds, deeds, custody) can be forged retroactively.

🛡️ What INKG runs instead

ML-KEM-768 + ML-DSA-65 — the lattice-based schemes NIST standardized (FIPS 203 / FIPS 204) precisely because no known quantum or classical attack breaks them. Our wallets enroll a post-quantum keypair: the bank keeps only the public key, the citizen keeps the secret. Signatures and key exchange are quantum-resistant end to end.

What Quantum-Proof Sovereign delivers

🔑 Post-quantum wallets

Every wallet can enroll an ML-DSA-65 identity. Transactions are signed with a lattice signature no quantum computer can forge. The bank stores only the public key — the citizen holds the secret.

🔐 Quantum-safe key exchange

ML-KEM-768 encapsulation for confidential settlement channels, so session keys can't be recovered from harvested traffic — defeating "harvest now, decrypt later".

🦅 Sovereign & open

Runs 100% on our own nodes, open-source (@noble/post-quantum), auditable, no licenses, no foreign cloud. Your quantum-safe rails stay in your jurisdiction.

Proof — sign & verify with real post-quantum crypto, right now

Not a simulation. Every button calls our live service (/api/pqc/keypair · /sign · /verify, NIST FIPS 203/204). Generate a key, sign your own message, verify it — then tamper with it and watch the signature fail.

⚡ Live post-quantum lab ① Keypair ② Sign ③ Verify ④ Tamper
A brand-new lattice keypair is produced on our sovereign node each time.

Generate a signing keypair (ML-DSA-65) first.

Why sovereign quantum-proof is worth more

  • Regulators are already mandating PQC migration — NIST timelines deprecate RSA/ECDSA; get certified ahead of the deadline.
  • Long-lived assets need it first — bonds, custody, land titles and settlement outlive the arrival of quantum computers.
  • Sovereign entity = tax-efficient — paid in sovereign tokens, settled on your own rails, no foreign processor.
  • Open source, auditable, no lock-in — you own the whole post-quantum stack, forever.

Pricing — sovereign grade

Quantum-Safe Audit

$15,000
  • Post-quantum readiness assessment
  • Inventory of RSA/ECDSA exposure
  • Harvest-now-decrypt-later risk map
  • Migration roadmap + report

Quantum-Proof Migration

$45,000
  • Migrate keys & signatures to ML-KEM-768 + ML-DSA-65
  • Wallet PQC enrollment
  • Quantum-safe settlement channels
  • Hybrid rollout (classic + PQC)
  • Sovereign deployment

Sovereign Certification

$120,000/yr
  • Annual quantum-proof certification
  • On-chain attested credential
  • Continuous PQC posture monitoring
  • Compliance-ready evidence pack
  • Renewal + re-attestation

Enterprise

$250,000
  • Full PQC stack, on-prem sovereign
  • Custom key ceremony & HSM
  • Dedicated engineering support
  • Bank / exchange integration
  • SLA + priority response

Settled in sovereign tokens (WUSD 1:1, WMP, IGT…) via sovereign checkout — 1% burned to the treasury. No foreign processors.