Pushed 1 commit to main
- 875ea6a docs(audit): stage 4 on v4 with the Ethereum setting, reports in docs/audit · fnoufnou

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.
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.
Pushed 1 commit to main
Pushed 1 commit to main
Earned a Ship Weeks badge.
Pushed 1 commit to main
Pushed 1 commit to main
Pushed 1 commit to main
Pushed 1 commit to main
Pushed 1 commit to main
Pushed 11 commits to main
and 6 more commits
Pushed 1 commit to main
Earned a Ship Weeks badge.
Pushed 1 commit to main
Pushed 1 commit to main
Pushed 6 commits to main
and 1 more commit
Pushed 1 commit to main
New project.
@fnoufnou
Please feel free to ask any questions or recommend any suggestions!