Verify It Yourself
You do not have to take the chain's word, or Darwin's. Each transaction page in the app re-verifies the signatures in your browser.
A trade
A trade made through a Darwin account shows Signed by with the owner's address and the summary the owner signed. The page then verifies the owner's ML-DSA-87 signature with @qorechain/pqc, in your browser:
- it decodes
factory.execute(owner, calls, summary, deadline, pqSignature)from the calldata; - it finds the account's nonce for this trade: from its
Executedevent for an older EVM-lane trade; for a native-lane execution, which leaves no EVM log, the one nonce below the account's current one for which the signature verifies (the relayer's memodarwin execute <account> <nonce> <calls hash, 12 hex>names it too); - it rebuilds the exact text,
qorechain-msg-v1|qorechain-diana|+ summary, account, nonce, deadline and the hash of the calls, as the account did on chain; - it verifies the 4,627-byte signature against the owner's registered key;
- it checks that the same signature fails for nonce + 1.
For any native transaction, QoreSign's inspectTransaction (@qorechain/qoresign) re-reads the committed transaction and checks both its secp256k1 signature and its ML-DSA-87 layer against the keys the signer registered on chain, over the sign-bytes version the network verifies. A trade relayed on the path used before Darwin accounts shows the relayer's signature and the user it was relayed for. Every transaction Darwin itself sends (rounds, rebalances, account executions) is such a native transaction; the QoreChain explorer shows each "quantum-safe · verified on-chain".
An oracle round
The page decodes submit(timestamp, ids, prices, signature) from the transaction's calldata, rebuilds the exact roundMessage the oracle checked, reads the reporter's key, and verifies the 4,627-byte ML-DSA-87 signature with @qorechain/pqc. It then checks that the same signature fails for the next round number, for example "Round #72 signature verified · rejected for round #73".
Rounds are sent on the native lane, as a hybrid MsgCrossVMCall, which leaves no EVM log. The round number comes from the transaction's memo, darwin round <n>. The memo is never trusted alone: the signature verifies for that round number only. Older EVM-lane rounds are read from their RoundSubmitted log.
From the terminal
QoreChain's qore CLI gives a second opinion; Darwin's on-chain suite uses it:
npx @qorechain/qore-cli pq status <txhash> --json # tier, layer count, verified
npx @qorechain/qore-cli pq status <qor1 or 0x> --json # registered key, proof of possession, EVM windowFor a Darwin account (deployer qor1yzq84n9uj6fmgzsh7tk88gr7dhrh60u95gpw8p, or a relayer) the second command shows no open EVM window. To check every transaction those accounts sent since a date:
cd ops && npx tsx src/pq-audit.ts 2026-11-21T09:12:00Z # each must show pqc_hybrid_verify status=verifiedRaw data
Every transaction page links to the raw transaction on the testnet's REST API and to the QoreChain explorer (set it to Testnet once; it remembers).