The post-quantum layer for data, messages and agents.
Coins can run to a fresh address. Your data can’t. Kvant seals it post-quantum, on your device. Your agents are next.
Post-quantum security infrastructure on Robinhood Chain
ML-KEM-768 + X25519, signed with ML-DSA-65
Sealed on your device. No backend sees plaintext
Built on proven standards:
- ML-KEM-768NIST FIPS 203
- ML-DSA-65NIST FIPS 204
- X25519RFC 7748
- AES-256-GCMNIST SP 800-38D
- MCPAgent interface
- x402Agent payments
- Robinhood Chain$KVANT tiers
- nobleOpen-source crypto
Coins can run. Data can’t.
Why now
A coin can run to a fresh address. A file can’t.
Bunker mode
Crypto is planning for bunker mode: move coins to fresh addresses, in case elliptic curves fall early, to AI or to quantum computers.
A file can’t run
A coin can run to a fresh address. A file can’t. Anything sealed with curves alone can be copied today and opened the day those curves fall. Nearly every signature agents and wallets emit rides on the same math.
The bunker for your data
Kvant seals what you can’t move. Every .kvant envelope is sealed with ML-KEM-768, the NIST post-quantum standard, on top of X25519, and signed with ML-DSA-65. On your device.
Going full bunker?
Seal to a freshly generated key file. Its keys are random and never touch your wallet’s signature, so if curves fall, an attacker still has to break ML-KEM-768 too.
How it works
One envelope, sealed on your device. No accounts. No uploads.
Pick your key source
Keys in >
Connect an EOA wallet and sign one message, or generate a passphrase-protected key file. No accounts, no gas.
Drop your file
File in >
Any format, any type. The filename and the exact size are encrypted along with the content.
Sealed on your device
Sealing >
ML-KEM-768 + X25519 through HKDF-SHA256 into AES-256-GCM, signed with ML-DSA-65. Nothing is uploaded.
Keep the envelope
Result >
Download the .kvant envelope and its Quantum Seal. Store it anywhere, open it on any device with the same keys.
The post-quantum security layer for autonomous finance.
A unified infrastructure protecting agent identities, encrypted communications and payment authorization.
Encrypted communications
Files and messages sealed with ML-KEM-768 + X25519 and signed with ML-DSA-65, on your device.
Agent identities
One post-quantum identity for your browser and your agents: the same keys open the same envelopes over MCP.
Payment authorization
Agents sign x402 payment payloads with ML-DSA-65 under their own context, so anyone can check which key signed.
One envelope, three surfaces.
Humans drop files. Agents call tools. Receipts get signed. Kvant runs entirely in your browser or in your agent runtime. There is no backend that sees plaintext, not ours, not anyone’s.
01 / 03
Humans
Drop a file in the browser. Out comes a .kvant envelope that only your wallet or your key file can open, plus a Quantum Seal receipt. Store it anywhere and open it on any device with the same keys.
Bunker mode for agents.
On the roadmap · next
Agents hold keys and sign on curves all day. Next from Kvant: the same post-quantum envelope as six MCP tools, for Claude, Cursor and any MCP client. Built and tested. The npm release is next.
$ npx -y @kvant/mcpMCP · stdio · 6 tools
kvant_encrypt_file
- Seal bytes into a .kvant blob + Quantum Seal
- In: bytes_base64…
- Out: blob_base64…
kvant_decrypt_file
- Recover plaintext and verify the signer
- In: blob_base64…
- Out: plaintext_base64…
kvant_send_message
- Wrap text into a shareable, signed URL
- In: text…
- Out: url…
kvant_decrypt_message
- Read a message URL and return the key that signed it
- In: url…
- Out: text…
kvant_verify_seal
- Parse a Quantum Seal and return its metadata
- In: png_base64…
- Out: valid…
kvant_sign_x402
- Sign an x402 payment payload with ML-DSA-65
- In: payload_json (JSON object)…
- Out: signature_base64…
One identity, two doors.
Seal a file in /app, open it in your agent with the same key file or wallet signature. Same keys, same .kvant format.
Runs on your machine.
A local stdio server. No Kvant server, no network calls, no telemetry.
Signs what agents pay.
x402 payment payloads signed with ML-DSA-65, under their own context.
Built on the standards securing the next decade.
NIST-grade post-quantum cryptography, wired into MCP for agents and built for Robinhood Chain. Same envelope, every surface.
Hybrid post-quantum
ML-KEM-768 combined with X25519 via HKDF-SHA256. Attackers have to break both. The same defence-in-depth used by Signal, Chrome, and Cloudflare.
FIPS 203 · FIPS 204
MCP-native interface
Six PQC tools exposed over the Model Context Protocol, encrypt files, sign x402 receipts, message agents. Same crypto core as the web app. Agent-ready.
MCP · stdio · 6 tools
Built for Robinhood Chain
The USD value of your $KVANT on Robinhood Chain sets your tier, priced on-chain from the launch curve and Chainlink ETH / USD. Wallets connect as injected browser wallets only, with no relay in between.
Robinhood Chain · $KVANT tiers · x402
NIST FIPS 203 + 204 · MCP · Robinhood Chain · x402
Five guarantees.
We hold none of your data
No backend processes file content. Nothing to hand over.
NIST-standardized algorithms only
ML-KEM-768 and ML-DSA-65, FIPS 203 and 204. No home-made crypto.
Resistant to quantum computers
Hybrid: an attacker must break a post-quantum and a classical scheme.
Your keys stay yours
No storage, no escrow. Keys come from your wallet or your key file.
Tampering is detected
Every envelope is signed. One modified byte and decryption fails.
Kvant security
These are not marketing claims. Each one is a direct consequence of how the product is built.
Kvant Shield: PQ Gateway for x402.
Kvant Shield
A post-quantum tunnel for every x402 endpoint your agents pay.
Front any HTTP 402 Payment Required endpoint with a Shield URL. Requests and receipts tunnel inside a post-quantum envelope, and every paid call emits a Quantum Seal that can be anchored on Robinhood Chain. Every receipt deserves a Quantum Seal.
Hybrid ML-KEM + X25519 tunnel: drop-in proxy in front of any x402 endpoint.
Every paid call emits a Quantum Seal PNG with endpoint, amount, and transaction hash.
Reserved capacity for $KVANT holders: Pro and Whale tiers get priority lanes.
One endpoint swap. No code rewrites. MCP-native. Agent-ready.
x402 · Quantum Seal receipts · Robinhood Chain anchors
Also on the roadmap
- >Seal anchoring on Robinhood Chain, from the app and the MCP server
- >Gas-free anchoring on Robinhood Chain
- >Encrypt for any address through an on-chain key directory
- >Sealed receipts for agents that trade Stock Tokens
Opens by application
A first cohort of x402 endpoints, chosen from applications.
No date set.
The application form goes up when the gateway is ready for that cohort. Questions until then: write to us.
Write to usHolders encrypt more.
The quantum-safe token on Robinhood Chain.
The envelope is post-quantum. $KVANT sets how much you seal: the USD value of your balance on Robinhood Chain raises encryptions per day and maximum file size in the web app. Seals, messages and the MCP server are the same on every tier. No subscriptions, no accounts: your balance is your tier.
For first envelopes and the occasional file.
Free
$0
No $KVANT needed
- Encryptions
- 3 / 24h
- Max file size
- 25 MB
- Quantum Seal on every encrypted file
- Wallet or key file mode
For daily use: more files a day, and bigger ones.
Holder
First holder tier$20+
≥ $20 in $KVANT
- Encryptions
- 25 / 24h
- Max file size
- 100 MB
- Quantum Seal on every encrypted file
- Wallet or key file mode
For heavy daily use and large archives.
Pro
$100+
≥ $100 in $KVANT
- Encryptions
- 250 / 24h
- Max file size
- 1 GB
- Quantum Seal on every encrypted file
- Wallet or key file mode
No daily cap and no tier cap on file size.
Whale
$1,000+
≥ $1,000 in $KVANT
- Encryptions
- Unlimited
- Max file size
- No tier cap
- Quantum Seal on every encrypted file
- Wallet or key file mode
$KVANT is not live yet. Every wallet is on the Free tier until launch. The official contract address will be published here, and only that contract will set your tier.
Things people ask.
FAQ
Everything you need to know about post-quantum envelopes.
Can’t find what you’re looking for?
Browse the docs or ask us on X @Kvantcoin.