QuantovaQstampby Quantova
EN
EnglishEN日本語JAFilipinoFIL한국어KO简体中文ZHFrançaisFREspañolESУкраїнськаUK
GitHub Start building →
Qstamp / Defence
QDefence · The defence branch of the Qstamp family

Post quantum integrity for defence, from evidence and aid to robotic systems.

QDefence brings the Qstamp family to armed forces, defence ministries, allies and the bodies that hold them to account. It proves who ordered, approved, built, handed over, recorded or changed something, and when, with signatures that a quantum computer cannot forge. Quantova describes QDefence as the first defence tooling family built on a network that has been post quantum since its genesis block. Every tool of the defence branch concerns the integrity, provenance, authority and accountability of records. None of them selects, targets or engages, none of them carries weapons functions, and none of them makes the use of force faster or more effective. They are built for defence, for the protection of command, equipment and evidence against forgery by an adversary who may hold a quantum computer.

The problem

Defence records are a target for forgery now and later.

An adversary can copy signed orders, firmware, logs and evidence today and forge them once a large quantum computer exists. Records that must hold for decades, from the custody of equipment to evidence before a court, are signed today with RSA or elliptic curve keys that Shor's algorithm breaks.

Forged authority

A forged order or mandate that verifies like a genuine one undermines command and accountability.

Tampered software

A forged firmware signature lets an adversary load code onto a platform that the platform will trust.

Rewritten history

A mission log, an evidence file or a custody record rewritten after an incident cannot be disproved without an independent seal.

Live today

What defence users can integrate now.

These uses rely on SDKs that are released on npm and GitHub and anchor live on the Quantova network, where every anchor can be checked on QVMScan.

Evidence of violations of the law of armed conflict

Qstamp, QSign and QTrace fix photographs, video and witness statements in time and prove their origin and that they are unaltered, for investigators and international courts.

Accountability of military and humanitarian aid

QAid and QSpend prove that each payment and delivery of aid had an approved basis and reached its stated destination once.

Defence procurement without manipulation

QProcure seals bids before the deadline and every score and award after it, so no tender can be rearranged.

Official communications that can be authenticated

QSign and QTrace let a ministry sign its statements and video, so the public and allies can check that a statement is genuine.

Custody of donated equipment

QSign and Qstamp seal each handover of materiel with the signatures of both parties, so equipment cannot leave the record unnoticed.

Accountability of AI decision support

QLog and QMandate record what an AI advisory system recommended, within which authority, and which person approved or declined it.

Being built

The defence specific stack.

Three parts of the defence branch are being built as a side stack that runs alongside the Quantova network and shares no infrastructure with retail products. Each is released as open source under the same licences as the rest of the Quantova stack, after security review, so any government or auditor can examine it.

QEdge for robotic and uncrewed systems →

An embedded signing core for drones, ground robots and maritime systems, with signed mission mandates, firmware provenance and a tamper evident flight and mission recorder.

Sovereign Quantova networks →

Private networks run entirely inside a national or coalition secure environment, with their own genesis and validators and no connection to the public network.

CNSA 2.0 profile →

Every SDK of the family with ML DSA 87, ML KEM 1024 and SHA 384 or SHA 512, together with hardware security module support and preparation for FIPS 140 3 validation.

The QDefence SDKs →

Eight SDKs for orders, oversight, sources, builds, custody, evidence, maintenance and credentials.

Live flow

How a defence record travels, in motion.

Live flowQDefence, from a defence system to independent verification
  1. Your systemsDefence systemA command system, logistics system, evidence store or platform creates a record
  2. Your systemsQDefence SDKThe record is signed under a role key held in a hardware security module
  3. Your systemsRecorder chainRecords are chained by hash, so none can be removed or reordered
  4. Your systemsExport gatewayOnly a salted 32 byte commitment of each batch is released, after approval
  5. Quantova networkSovereign or public networkThe commitment is anchored on a sovereign Quantova network or the public one
  6. PublicAllies and courtsAn authorised verifier proves the record and its time, without the source system
Inside your systemsQuantova networkPublic and verifiable
Open by design

Open source, so anyone can verify the claims.

Every part of the defence branch is published as open source under the Apache License 2.0 or the MIT licence, the same licences as the rest of the Quantova stack, and Quantova Inc owns the Qstamp, Quantova, QVM and Quanta trademarks. The construction, the code and the verification procedure are public so that governments, allies and independent auditors can test what is built. Operational data, keys and the content of records never leave the systems of their owner.

Engagement

Working towards engagement with defence and national security agencies.

Quantova Inc is working towards engagement with defence, national security and public sector agencies in the jurisdictions it serves. Any engagement will follow the procurement, security accreditation, export control and legal requirements of each agency and jurisdiction. No agency has endorsed, approved, certified or contracted for the Qstamp family or its defence branch, and nothing on this website states or implies otherwise.