
Encrypted Apps
SealedBid
Sealed-bid auctions with ML-KEM-1024 encryption on QoreChain
About
Sealed-bid auctions on the QoreChain testnet: bids are encrypted client-side with ML-KEM-1024 (NIST FIPS 203) to the auctioneer's public key, published in the chain's x/pqc KEM registry. Only ciphertext goes on-chain, so bids stay sealed until the reveal phase — while the contract enforces the auction rules and verifies every reveal against the commitment submitted with the sealed bid.
How it's made
The auctioneer generates an ML-KEM-1024 keypair and publishes the public key in the chain's x/pqc KEM registry (MsgRegisterKEMKey, hybrid-signed). Auctions are created on-chain with bidding and reveal deadlines. Bidders seal their bids in the browser: ML-KEM-1024 encapsulation produces a shared secret, and AES-256-GCM encrypts the payload {amount, salt} under it — only the ciphertext goes on-chain. After the deadline, bidders reveal; the contract verifies each reveal against the commitment submitted with the sealed bid, and the auctioneer decrypts the winning bid. The contract has 21 passing tests (contract + crypto, including tamper detection), and full end-to-end auctions ran on the Diana testnet: 2 sealed bids, both revealed, finalised with the winner at 2,500,000 uqor, with auctioneer-decrypted amounts matching the on-chain reveals.
Timeline
Comments and questions
- No comments yet.