Skip to content
QORECHAIN
Register

Quantum Pass

Hallmark

Proof that the contract on QoreChain is the code in your repo.

Share on X

About

QoreChain's explorer has no source verification and no Etherscan-compatible API. Today nobody can prove that a contract deployed on diana was built from the code in a GitHub repo, and Solidity PQC features (pqcVerify, pqcKeyStatus) can only be checked by reading the repo by hand. Hallmark fixes that. Give it a contract address and your compiler output (Foundry or Hardhat build-info). Hallmark recompiles with the exact same solc version and settings and compares the result with the bytecode on chain. When they match, the contract gets a public Hallmark page: - the verified source, readable in the browser - a PQC report: whether the contract calls pqcVerify (0x0a01) or pqcKeyStatus (0x0a02), and from which functions - whether the deployer has a registered ML-DSA-87 key - a README badge: "Hallmarked on QoreChain" Every result is recorded in the Hallmark registry contract on diana. The developer then claims the contract with QoreX in one hybrid-signed (secp256k1 + ML-DSA-87) transaction, linking it to their repo. A CLI (npx hallmark check) reruns any verification locally, so nobody has to trust our server. Built for the builders of this fest first: verify your contract, add the badge, and let anyone check deployed code against your repo in one click.

How it's made

Plan, updated as we build: - Web app: Vite + React + wagmi with the QoreX wallet, scaffolded with create-qorechain-dapp (viem-wagmi template); the verification API runs as Vercel serverless functions. - Verification engine: @ethereum-sourcify/lib-sourcify (MIT, credited in the README) recompiles the Solidity standard JSON input with the matching solc build and compares runtime bytecode, handling the metadata hash and immutables. - PQC detector: finds the pqcVerify / pqcKeyStatus precompile addresses in the runtime bytecode, maps the calls back to source functions, and reads the deployer's ML-DSA-87 key status over REST. - Registry: a Solidity contract on qorechain-diana, with tests. Only the Hallmark verifier account can record results. Claims require a registered ML-DSA-87 key, checked in-contract through pqcKeyStatus (0x0a02). Every EVM write goes through an authorisation window opened with a hybrid-signed native message. - Wallet: QoreX through the QoreX integrations kit; claims are hybrid-signed. - CLI: npx hallmark check / submit, same engine, so any result can be reproduced locally. - AI use is documented in AI_USAGE.md from the first commit.

Timeline

HallmarkQuantum Pass

Pushed 1 commit to main

  • b82f035 Record the Vercel Firewall rate limit (B3) and the production checks · agvswira
HallmarkQuantum Pass

Pushed 2 commits to main

  • ade4e88 Red-team fixes: proxies, stored-source poisoning, link and terminal injection · agvswira
  • 40fa8d4 Document the red team and the first review · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 6f69ffe Deploy to Vercel: hallmark-jade.vercel.app · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 41f81e7 Add the hallmark CLI: check a record from your own machine · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 6ad6484 Keep the verifier's EVM window open, scoped to the registry · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 4b5d762 Redesign the web app around the H-Seal · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 6041927 Add the Hallmark web app and API · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 91e2ec0 Hand registry ownership to the project owner's wallet · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 702e062 Deploy HallmarkRegistry to diana and hallmark it with itself · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • f80c1fa Add the verification engine with a PQC precompile report · agvswira
HallmarkQuantum Pass

Pushed 1 commit to main

  • 55f38b9 Docs: start the AI log from the problem Hallmark solves · agvswira
HallmarkQuantum Pass

New project.

Comments and questions

  • No comments yet.