Skip to content
QORECHAIN
Register

Quantum Pass

Letterplate

Give any QoreChain account an address it can receive post-quantum sealed messages at, and check where to seal for any ad

Share on X

About

A message sealed with ML-KEM-1024 can only be opened with the recipient's key, so every encrypted app starts with one question: does this address have a key, and where is it? QoreChain has a native registry for these keys, but almost nobody is in it. On 21 November, 0 of 8 mainnet and 0 of 4 testnet validators had one. And a QoreX user cannot add one: the extension refuses MsgRegisterKEMKey from websites and has no setting of its own to register a key. Letterplate fixes both sides. - Check: paste any qor1 address and Letterplate reads the chain to say whether it can receive sealed mail, and exactly which key to seal to. It also checks every bonded validator on mainnet and testnet. - Your address: connect QoreX and get an address in five steps. The page creates a sealing key in your browser, with a passphrase-encrypted backup. QoreX funds a small sealing account; it publishes its ML-KEM-1024 key; then each side names the other on chain, in hybrid-signed transactions (secp256k1 + ML-DSA-87). The binding records are self-addressed, so any app can find them with no registry account to trust. A binding counts only when both sides agree, and the latest one wins, so a lost key can be replaced. Classical-only or malformed records are listed as refused, with the reason. Tested end to end on testnet with the official QoreX wallet mock: a fresh wallet went from "cannot receive" to "can receive", in four transactions, all code 0.

How it's made

Scaffolded with create-qorechain-dapp 0.14.0 (fullstack-web template); the first commit is the untouched template. TypeScript, React and Vite in the browser, with a small Node server, because QoreChain's REST API sends no CORS headers. - Resolver (lib/resolve.mjs): an address's own key from the ML-KEM registry, or a two-way binding to a sealing account. Records are 1 uqor self-sends with a letterplate/1 memo, and they must be hybrid-signed. The public testnet node prunes old blocks, so Letterplate reads newest first and says when older history could not be read. A failed read is always an error, never "cannot receive". - Keys: @qorechain/sdk 0.14.0 for the sealing account and its ML-DSA-87 registration with proof of possession; @qorechain/qoreseal 0.1.0 for the ML-KEM-1024 key and MsgRegisterKEMKey; @qorechain/qorex-types 0.1.0 for QoreX connect and signAndBroadcast. - Backup: one 32-byte secret, encrypted with PBKDF2-SHA-256 (600,000 rounds) and AES-256-GCM, bound to the owner and the key. Never stored or sent. - Relay: the server's one write path. It holds no keys and forwards only the sealing account's two transaction shapes, with a size cap and a rate limit. - Checks: 24 tests (every resolver state, rebinding, a sealing account that cannot be borrowed, refused records, the relay's gate, the server's guard rails). The flow was run end to end on testnet with @qorechain/qorex-wallet-mock. - Builds on the same builder's Quorate (Encrypted Apps), credited in the README.

Timeline

LetterplateQuantum Pass

Pushed 2 commits to main

  • eb70253 Check whether any QoreChain address can receive sealed mail, and where to seal it · nftkingiii
  • c875545 Scaffold Letterplate from create-qorechain-dapp 0.14.0 (fullstack-web template, testnet) · nftkingiii
LetterplateQuantum Pass

Pushed 2 commits to main

  • 6260fd8 Give a QoreX account an address for sealed mail: sealing key, relay and two-way binding · nftkingiii
  • b82de75 Document how AI was used to build Letterplate, including where it was wrong · nftkingiii

Comments and questions

  • No comments yet.