Earned a Ship Weeks badge.

Post-Quantum dApp
Perennial
A pension that survives Q-Day: only the yield is paid out.
About
Perennial is a pension protocol for humans and AI agents. The owner deposits once; the principal sits in a yield source and is never paid out, and only the yield it earns is paid to the beneficiary on a schedule. The beneficiary proves they are alive by checking in; after the check-in period plus a grace period without one, anyone can trigger succession and the income goes to the registered heirs by weight, while the principal stays invested. A pension has to outlive today's cryptography. If a quantum computer recovers the classical secp256k1 key, Perennial still holds: claiming, checking in, changing heirs and closing are authorised by an ML-DSA-87 signature verified inside the contract, not by msg.sender. A recovered classical key cannot redirect, fake a proof of life or withdraw anything. The vault has no admin, no upgrade path and no pause. Positions are permanent unless the owner kept the right to close at opening.
How it's made
Architecture: one Solidity contract, PerennialVault, per asset and yield source. A position's principal is deposited into an ERC-4626-shaped yield source and tracked as shares; harvest keeps exactly the shares needed to withdraw the principal (previewWithdraw rounds up) and redeems the surplus into the position's buffer. Payouts only ever come from the buffer. Post-quantum authorisation: a small library, PQCAuth, reads the signer's key from the pqcKeyStatus precompile (requiring algorithm ML-DSA-87, a 2592-byte key and possessionProven) and checks the signature with the pqcVerify precompile. The signed message binds chain id, vault, position, action, a per-position nonce, a deadline and a hash of the arguments, so signatures cannot be replayed or reused. Because authority is the signature, anyone can relay a signed action. Both precompile calls fail closed when they return empty data. Network features: hybrid ML-DSA-87 transactions and key registration with proof of possession (deployer and drill account), EVM windows scoped with allowedTargets to the vault and fUSD, the Solidity PQC signature check and key status precompiles, and fUSD converted from bank form to ERC-20 with MsgConvertCoin. Kits: @qorechain/sdk and @qorechain/evm (window helper, hybrid signing), @qorechain/pqc (ML-DSA-87 signing in the end-to-end script), and the create-qorechain-dapp Foundry template. Testing: 105 Foundry tests, including fuzz tests and invariant tests (principal never spent, the vault holds exactly the harvested buffers, succession is one-way, no value leaks to third parties), plus an end-to-end script that drives the deployed vault on testnet with real ML-DSA-87 signatures and confirms forged, mismatched and replayed signatures are refused. What was hard: Foundry's local EVM has no PQC precompiles, so unit tests use a mock and real verification is proven on testnet; Foundry scripts simulate locally, so the deploy script asks the node directly whether the precompile is active; and one mnemonic gives separate Native and EVM accounts, so faucet fUSD had to be converted before contracts could use it. The yield source on testnet is a fixed-rate mock; a real source is future work.
Timeline
Newly verified on chain: QoreSeal and the encryption key registry
Earned a Ship Weeks badge.
Earned a Ship Weeks badge.
Newly verified on chain: AMM pools
Earned a Ship Weeks badge.
Pushed 5 commits to main
- 57d1949 test(contracts): give the verifier address its own mock · raldblox
- c9c2c52 fix(deploy): let the dry run skip Foundry's second simulation · raldblox
- 3ec34ae ci: pin the Foundry version · raldblox
- 8a059ab docs: record accounts, fees, token conversion and scripting findings · raldblox
- 6e1a01e docs: describe the adversarial test account accurately · raldblox
New project.
Comments and questions
- No comments yet.