
Encrypted Apps
Qapsule
Send a message into the future that no quantum computer can open — and nobody can open early.
About
Qapsule is a post-quantum encrypted time-capsule dApp on QoreChain. A sender seals a message in their browser for a future date: the message is encrypted with AES-256-GCM, its key is XOR-split, one share is wrapped to the recipient with ML-KEM-1024 (FIPS 203), and the other share exists only as a hash commitment on-chain. The Qapsule contract on Diana testnet (0xfe5ee7ee9c4820144d7c95f5916722bbcbc492cc) refuses to accept the reveal of the second share before the unlock time — so not even the recipient can open the capsule early. When the time comes, the reveal lands as a public, timestamped on-chain event and the recipient decrypts locally. Time-capsules are exactly what "harvest now, decrypt later" attacks target — data meant to stay secret for 10–30 years. Classical key wrapping will not survive that horizon; ML-KEM-1024 will. Live proof: capsule id 0 was sealed, an early reveal was rejected by the contract itself (TooEarly), the reveal landed after unlock, and the message was decrypted from on-chain data alone.
How it's made
Built with the official QoreChain EVM starter (create-qorechain-dapp) and deployed through QoreChain's native flow: an ML-DSA-87 key registered for the deployer account plus a live EVM authorisation window for every deployment session. The capsule protocol runs entirely client-side plus one Solidity contract (Qapsule.sol, Diana testnet, chain ID 9800): the browser generates an AES-256-GCM content key, XOR-splits it, wraps Share A to the recipient's ML-KEM-1024 public key (@noble/post-quantum, FIPS 203 KEM-DEM), and anchors SHAKE-256 hashes of the ciphertext and Share B as on-chain commitments. The contract stores sender, recipient, unlock time and the wrapped share, and its revealShareB rejects any reveal before unlockTime and any share that fails the commitment check. The hardest part was QoreChain's deployment model itself: plain EVM tooling fails without a registered post-quantum key and an open authorisation window, so deployment goes through the template's own @qorechain/evm path. The full lifecycle is proven on testnet: capsule id 0 sealed, early reveal reverted with TooEarly, reveal accepted after unlock, message decrypted from on-chain data alone.
Timeline
New project.
Comments and questions
- No comments yet.