Skip to content
QORECHAIN
Register

Quantum Pass

Qommit

Quantum-proof signatures for your git commits, bound to your QoreChain identity.

Share on X

About

Every git commit says who wrote the code, but today's commit signatures (GPG/SSH) will be forgeable after Q-Day. Git history is permanent, so attackers could forge "verified" commits from trusted maintainers, a supply-chain attack on all open source. Qommit plugs into git's standard signing interface and signs commits and tags with ML-DSA-87 (FIPS 204). It binds each signing key to a qor1 address with a hybrid-signed QoreChain transaction, so anyone can verify who signed, in the terminal, on the web or in CI. Every commit in this repo is quantum-signed.

How it's made

A Node.js CLI registered as git's gpg.x509.program. It signs with @qorechain/pqc (ML-DSA-87) and speaks git's GPG status protocol, so git commit -S and git log --show-signature work unchanged. Key-to-address binding goes through QoreX signAndBroadcast (hybrid secp256k1 + ML-DSA-87). A Foundry-built QommitRegistry contract on the qorechain-diana testnet stores bindings, revocations and release anchors. The web verifier (Vite + React, scaffolded with create-qorechain-dapp) checks any GitHub repo's commit signatures in the browser.

Timeline

QommitQuantum Pass

Pushed 2 commits to main

  • 79fa0dc feat: qommit init and signed qor1 identity claims · Anjali7070
  • fa4035b feat: post-quantum git commit signing with ML-DSA-87 · Anjali7070
QommitQuantum Pass

New project.

Comments and questions

  • No comments yet.