QuantovaQstampby Quantova
ZH
EnglishEN日本語JAFilipinoFIL한국어KO简体中文ZHFrançaisFREspañolESУкраїнськаUK
GitHub 开始开发 →
Qstamp / Defence SDKs
QDefence SDKs

Eight SDKs for the integrity of defence records.

Each QDefence SDK seals one class of defence record, under separate role keys, in sequenced series that cannot be silently altered, and anchors only a salted commitment. They are built on the engine and released SDKs of the Qstamp family and are being built for release as open source. 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 family

What each SDK seals.

SDK记录What it provesBuilds on
QOrderOrders and authoritySeals orders, delegations of authority and countermands, so the chain of command behind any order can be proven.QSign, QMandate, QLog
QOversightAI decision accountabilitySeals the approval of AI models, each recommendation and the human review and decision that followed it.QMandate, QLog, QTrace
QSourceSensor and intelligence provenanceSeals capture, processing history and release decisions of sensor data, recording the digest of its security label rather than its content.Qstamp, QTrace
QBuildSoftware and firmware provenanceSeals build history, software bills of materials and release approvals, with release keys held in hardware.QTrace、Qstamp
QCustodyMateriel custodySeals every handover of equipment against its unique item identifier, with two signatures and reconciled running totals.QSign, QGov engine
QEvidenceEvidence custodySeals the collection and every transfer of evidence for investigations under the law of armed conflict.Qstamp, QSign, QTrace
QMaintMaintenance and release to serviceSeals maintenance work and release to service, which fails unless a separate inspector has signed.QSign, QGov engine
QCredentialQualifications and credentialsSeals qualification records and their revocation without placing personal data on any network.QSign, Qstamp
Platform profiles

Profiles for robotic and uncrewed systems.

QMission · Signed mission mandates

A signed mandate states the area, the time window and the permitted actions of a platform and the human who authorised them. The platform checks every command against it before execution, and a mandate can only narrow what the platform may do.

QBoot · Firmware signing and secure boot

Firmware and updates are signed with hash based or lattice signatures under CNSA 2.0, and the platform refuses any image that does not verify.

QRecorder · Flight and mission recorder

Every command, decision and event is written to a hash chained record whose head is signed at intervals and anchored when a link is available.

QTelemetry · Telemetry and sensor provenance

Telemetry and sensor output are chained and signed in batches, so later analysis can prove the data came from the platform unaltered.

QKeyring · Platform key lifecycle

Keys are provisioned in a secure element, rotated, revoked when a platform is lost or captured and destroyed on command.

Common construction

Shared by every defence SDK.

Separate role keys

Each role, from issuing an order to approving release, holds its own key, and a key may hold only one role.

Sequenced series

Records of a series carry their position and running totals, so a hidden or forked record is detected.

CNSA 2.0 配置

Each SDK is released with ML DSA 65 and with a CNSA 2.0 profile using ML DSA 87.

Sovereign anchoring

Anchors go to a sovereign Quantova network inside the secure environment, or to the public network for unclassified records.

独立验证

Verification needs only the records, their receipts and the published procedure.

开源

Released under the Apache License 2.0 or the MIT licence, like the rest of the Quantova stack.