Skip to content
QORECHAIN
Register

Post-Quantum dApp

QoreWitness

Video Evidence You Can Trust Again

Share on X

About

AI tools can change a face, a licence plate or a time stamp in a video in minutes. Judges, insurers and investigators now ask one hard question about every clip: can you prove that nobody changed it afterwards? Most camera owners cannot. QoreWitness seals camera footage at the source. A small agent next to the recorder gives every 60-second video segment a SHA-256 fingerprint. Every 10 minutes it combines the fingerprints into a Merkle root, signs the root with the camera's own ML-DSA-87 key and anchors it on QoreChain. The contract checks the post-quantum signature on chain before it accepts the record. The video never leaves the recorder. Later, anyone can check a clip with the free browser verifier. You drop in the clip and its receipt. The verifier checks the fingerprint, the Merkle path, the camera key, the ML-DSA-87 signature and the record on chain. Change one byte and the check fails. Why post-quantum: evidence can matter for 10 to 30 years. ML-DSA-87 (NIST FIPS 204) keeps the link between camera, owner and time valid after quantum computers break today's signatures. Status: early alpha. A home camera has anchored its footage every 10 minutes since 9 November 2026. Demo site with a test clip, its receipt and the verifier: https://qorewitness.fnoufnou.com Limits: a record proves that a file existed at a time. It cannot prove that the scene was real. It is not an eIDAS qualified timestamp.

How it's made

Architecture - Recorder: ffmpeg cuts the camera's RTSP stream into 60-second MP4 segments. - Agent (TypeScript, Node 22): hashes the segments, builds a SHA-256 Merkle tree per 10-minute window, signs the root with the device's ML-DSA-87 key (@qorechain/pqc) and calls AnchorRegistry.anchor(). It writes a JSON receipt per window next to the recordings. - Contract (Solidity, Hardhat 3): AnchorRegistry with a device registry. Register needs the owner key and the new device key (proof of possession). Rotation needs the old and the new device key. Revoke is final. Windows per device only move forward. No contract owner, no upgrade path. Every signed message is domain-separated (chain ID, registry, owner, device, action). - Verifier: one static HTML file (esbuild, viem). It calls verifyAnchor() over the public EVM RPC. Its SHA-256 is published on the demo site. QoreChain features - pqcVerify precompile (0x...0A01): the contract checks every ML-DSA-87 signature on chain. - pqcKeyStatus precompile (0x...0A02): the contract reads the owner's registered key and its proof of possession. - PQC key registration with proof of possession for the owner and agent accounts. - Scoped EVM window: the agent opens a window with allowed_targets set to the registry only, and renews it by itself. - Hybrid ML-DSA-87 transactions on the native lane (@qorechain/sdk). Two layers of post-quantum protection: the chain needs the account's ML-DSA-87 key for every EVM transaction, and the contract needs a fresh device signature for every state change. In a Q-Day Drill dry run, a bot with only the ECDSA key tried 13 attacks. None succeeded. What was hard - A call to an inactive precompile returns empty data, so the Solidity wrapper checks the return length. - Opening an EVM window changes the nonce. The agent opens the window first, then reads the nonce. - A scoped window refuses contract creation, so deploys use an unscoped window first. - Hardhat cannot run the precompiles. Unit tests use mocks, and live probes check the real precompiles on testnet. - Starting from a private key, the SDK derives the ML-DSA key from the ECDSA key. QoreWitness accounts come from a mnemonic, so a stolen ECDSA key does not give the ML-DSA key. 41 contract and Merkle tests. Gas per action and failure paths are in docs/TESTNET_FINDINGS.md. Built with Claude as AI pair developer, see AI_USAGE.md.

Timeline

QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 875ea6a docs(audit): stage 4 on v4 with the Ethereum setting, reports in docs/audit · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • fd7542d test: fail-closed regression tests, PQC call map in AUDIT.md, CHANGELOG · fnoufnou
QoreWitnessPost-Quantum dApp

Earned a Ship Weeks badge.

QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 0cd7df6 docs: recovery drill result, AI usage log · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 63af742 fix(scripts): recovery drill opens a scoped EVM window first · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 2 commits to main

  • 3821185 feat(agent): crash-safe receipts, rebuilt from the chain (T33) · fnoufnou
  • 972e151 feat(install): any stream type, retention service, image workflow · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • b535908 feat(verify): both fingerprints decide, signing boundary documented · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • ecea4d9 docs: demo re-anchored with spec/3, AI usage log for 15 Nov · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 2 commits to main

  • 1029e90 docs(audit): stage 3 on registry v4, findings assessed · fnoufnou
  • 9704f92 feat: second file hash SHA3-256 bound into the segment link (spec/3) · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • b712fa3 docs(audit): exact QCAI audit input for registry v4 (hardhat flatten) · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 11 commits to main

  • 7ff018c docs: custody drill results, README drills section, verifier hash on the site · fnoufnou
  • 3327044 feat(drill): custody drill, substitute the input (D) · fnoufnou
  • 6d234df chore: remove the one-time send-proof scripts, fix the one-segment verifier text · fnoufnou
  • 5804db2 feat(site): roadmap live, verifier for receipt v3, demo clip anchored on registry v4 · fnoufnou
  • ef683df docs: second hash moves to Next on the roadmap, AI_USAGE for 14 Nov · fnoufnou

and 6 more commits

QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 94489d7 feat(site): roadmap shows chain of custody and the custody drill as done · fnoufnou
QoreWitnessPost-Quantum dApp

Earned a Ship Weeks badge.

QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • c1254ff docs(audit): exact QCAI audit input for registry v3 (hardhat flatten of 404010e) · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 1310f04 feat(install): Docker image, compose file, setup wizard and one-line installer (T24) · fnoufnou
QoreWitnessPost-Quantum dApp

Pushed 6 commits to main

  • 8f5a2c1 feat(ops): retention timer and health check (T32) · fnoufnou
  • b53d51c feat(receipts): court-proof replay (T22) · fnoufnou
  • c9aca80 docs: AI_USAGE adds drill registration and week 1 posts · fnoufnou
  • 5f11bf3 docs: AI_USAGE adds workshop 1 · fnoufnou
  • a17efd4 docs: AI_USAGE with the division of work and a full log to 13 Nov · fnoufnou

and 1 more commit

QoreWitnessPost-Quantum dApp

Pushed 1 commit to main

  • 404010e feat(contracts): registry v3 with QCAI audit fixes (T9) · fnoufnou
QoreWitnessPost-Quantum dApp

New project.

Comments and questions

  • @fnoufnou

    Please feel free to ask any questions or recommend any suggestions!