QoreChain testnet, Intermediate, solo
A client and a freelancer do not trust each other to release payment on time.
Quantum Escrow holds the payment in a milestone escrow. The client funds it first, the freelancer can see the money is held, and payment releases only after a hybrid approval: a classical signature plus a real ML-DSA-87 post-quantum signature. A classical signature on its own is rejected, every time.
Open the ledgerLive on testnet, verified Nov 15
Live testnet flow, complete 5 of 5
Testnet qorechain-diana, EVM chain 9800. Deploy, create escrow 0, fund 0.01 QOR, approve with live ML-DSA-87 verification via the real PQC Verify precompile 0x0000000000000000000000000000000000000a01, release, all done Nov 15 about 02:44 to 02:49 WAT.
The steps above are the live testnet result. The ledger below still runs in demo mode, with simulated fUSD and no chain transaction sent in a local run.
Ledger
Escrow ledger
Demo fUSD balance: 1,000 fUSD held by you, the client. Freelancer received: 0 fUSD. Escrow held: 0 fUSD.
Proof
Receipts
Every step writes a receipt here. Nothing is faked: demo mode is labelled, and the live testnet flow is complete, see the live section above.
No receipts yet. Create a milestone escrow to begin.
Flow
How it works
- 1Create. The client opens a milestone escrow with a title, a freelancer, and an amount in fUSD.
- 2Fund. The client funds it in demo mode with test tokens. On testnet this is a real fund call inside a scoped EVM window.
- 3Approve, hybrid. The client signs the approval message twice: once classically, and once with a fresh ML-DSA-87 keypair from @qorechain/pqc 0.2.3. The demo verifies that post-quantum signature in the browser.
- 4Release. After hybrid approval, payment releases to the freelancer and a receipt is issued. If the window closes with no approval, the client can refund.
Classical only approval is rejected on chain by QuantumEscrow.approveMilestone. The contract test suite proves it: 7 passing tests, including classical only rejection and hybrid success. The on chain post-quantum check in local tests is a deterministic stand in for the PQC Verify precompile. Live, the approval was verified with the real PQC Verify precompile 0x0000000000000000000000000000000000000a01, and the full live flow is complete: escrow 0 released, contract balance 0 QOR, Nov 15 about 02:44 to 02:49 WAT. See BUILD-REPORT.md for the exact audit results.
Wallet status, verified Nov 15
Five QoreX wallet, read only
Verified live Nov 15 with qore-cli on testnet qorechain-diana, chain 9800. No transaction hash is invented here.
History: fresh account at first check, exists false, 0 QOR. Faucet claimed Nov 15 01:00 WAT, 100 QOR, account number 15585, sequence 0. Key registration completed Nov 15 01:13 WAT, sequence 2, balance 99.85 QOR, 100 QOR minus 0.15 QOR in fees. Live flow complete Nov 15 about 02:44 to 02:49 WAT: deploy, create escrow 0, fund 0.01 QOR, approve with live ML-DSA-87 verification via the real PQC Verify precompile, release. Escrow 0 final status released, contract balance 0 QOR.
Kits
QoreChain kits used
- QoreChain SDK 0.14.0, @qorechain/sdk, for the unified account, PQC key status, and the EVM authorisation window helper in scripts/window.ts.
- @qorechain/pqc 0.2.3, for real ML-DSA-87 key generation, signing, and verification in the demo.
- QoreSign, the signing model the hybrid approval follows: classical plus post-quantum, both required.
- @qorechain/evm 0.14.0, for the EVM window cost and status checks before any testnet deploy.
Live contract address: QuantumEscrowLive 0xb014d1d21dee9536e66d12097a7ecf16df4cb506. Deployer wallet is qor1kkmn9z3es9p3heet7y5zcrcg57g9ljp8909r5u (Native) and 0xB5b7328A3981431BE72bF1282c0F08A7905fC827 (EVM form, same identity). Verified live Nov 15 with qore-cli on testnet qorechain-diana chain 9800. Live flow complete Nov 15 about 02:44 to 02:49 WAT: deploy, create escrow 0, fund 0.01 QOR, approve with live ML-DSA-87 verification via the real PQC Verify precompile 0x0000000000000000000000000000000000000a01, release. Escrow 0 final status released, contract balance 0 QOR. Client coin 60 EVM 0x60934cfE09477E8be038CEd7Ef140c9643d5466f, freelancer coin 118 EVM 0xB5b7328A3981431BE72bF1282c0F08A7905fC827. No transaction hash is invented here.