
Post-Quantum dApp
Jaydaad
An inheritance vault that requires a witness and post-quantum signatures.
About
What happens to your crypto if you’re no longer there to unlock it? Sharing a wallet key today gives someone access before you intend. Keeping it to yourself could leave the people you love with no way in. Jaydaad lets you plan that handover on your own terms. You set funds aside, choose who should receive them, and name a witness you trust. A regular check-in keeps the funds in place. Life gets busy, so a missed check-in starts a grace period. If you still haven’t checked in when it ends, the person you chose can claim the funds with your witness’s approval. You can make that plan today and keep your wallet key private. I built Jaydaad on QoreChain Diana and tested the full handover, all the way to a beneficiary receiving 0.25 test QOR.
How it's made
I started with a problem that’s easy to miss in a crypto inheritance plan. A forged check-in could keep the beneficiary waiting indefinitely. That matters for a vault designed to hold funds for years. A sufficiently powerful quantum computer could eventually forge the kinds of signatures conventional wallets rely on. I wanted the vault to keep enforcing the owner’s plan even if someone gained control of their wallet key. I built the vault as a Solidity contract on QoreChain Diana. Every check-in, cancellation, and payout requires two ML-DSA-87 signatures, a type of digital signature designed to resist quantum attacks. The owner and witness sign a check-in or cancellation. The beneficiary and witness sign a claim, which the contract accepts only after the grace period ends. When the vault is created, it records a hash of each person’s public key from QoreChain’s on-chain registry. Before accepting an action, it checks that the registered keys still match and verifies both signatures using pqcVerify. Each approval specifies the chain, vault, action, and signer, and includes a one-time nonce and an expiry. A signature for today’s check-in can’t be reused for the next one or applied to a payout. The main integration challenge was connecting native QOR transfers to EVM contract calls. The dashboard uses QoreX to fund the vault. For the live check-in, I used the QoreChain SDK and qorechain-pqc to open a one-transaction EVM window restricted to the vault, submit the signed check-in, and close the window. Alongside the end-to-end payout on Diana, I tested that the contract rejects early claims, reused approvals, and actions signed with the conventional wallet key alone.
Timeline
Comments and questions
- No comments yet.