Pushed 1 commit to main
- 75a7222 Update video script for PqcGate and the hosted demo · Amin

Quantum Pass
A Foundry contract behind a post-quantum EVM window, read through the QoreX wallet.
Quantum Pass Counter is our first end-to-end run through QoreChain's post-quantum flow on the Diana testnet. A minimal Counter contract is deployed with Foundry from an account whose ML-DSA-87 key is registered on chain and whose scoped EVM authorisation window was opened with a hybrid-signed transaction (secp256k1 + ML-DSA-87). A second contract, PqcGate, calls the pqcKeyStatus and pqcVerify precompiles: it answers whether an account is quantum-ready and lets an account prove control of its post-quantum key with a nonce-bound ML-DSA-87 attestation. A small web page connects the QoreX wallet through the official RainbowKit kit, shows the connected account, its QOR balance and its EVM window, and reads the live Counter value.
Scaffolding. Both halves come from create-qorechain-dapp 0.14.0: the Foundry template for dapp/ and the viem-wagmi template for web/. Node 22, Foundry 1.5.1, npm. Post-quantum setup. The window helper (scripts/window.ts, @qorechain/sdk + @qorechain/evm) derives the EVM deployer from the team mnemonic, registers its ML-DSA-87 key with MsgRegisterPQCKey, and opens a scoped EVM window (600 blocks, 5 txs, 3.75 QOR cap) with a hybrid-signed MsgOpenEVMWindow. Only then does the chain accept forge's deployment transaction. Contracts. Counter is the template contract. PqcGate adds an IQorePQC interface to the precompiles at 0x...0a01 (pqcVerify) and 0x...0a02 (pqcKeyStatus). isQuantumReady() reads the registry; attest() verifies an ML-DSA-87 signature over a message bound to chain id, contract, sender and a per-account nonce. Tests run on Foundry's local EVM with mock precompiles installed via vm.etch, following the pattern from the official qday-vault example. 9 tests pass. Web. wagmi + viem + RainbowKit with @qorechain/qorex-rainbowkit for QoreX. The page reads the Counter with useReadContract on chain 9800 and the EVM window through the native REST API. QoreX connects and reads; it does not sign EVM transactions yet, so increment() is wired for other injected wallets. Ship Weeks. From the team's QoreX account via the SDK, hybrid-signed: a 30 QOR transfer, an ML-KEM-1024 key registered with @qorechain/qoreseal (keys derived from the mnemonic), and a swap in native AMM pool 2. AI tooling: Claude Code as pair programmer; see AI_USAGE.md
Pushed 1 commit to main
Newly verified on chain: AMM pools, QoreSeal and the encryption key registry, Test tokens fUSD, fETH, fBTC
Pushed 1 commit to main
Earned a Ship Weeks badge.
Newly verified on chain: EVM window (incl. scoped), Hybrid ML-DSA-87 transactions, PQC key registration with proof of possession
New project.