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 proves	Builds on
QOrder	Orders and authority	Seals orders, delegations of authority and countermands, so the chain of command behind any order can be proven.	QSign, QMandate, QLog
QOversight	AI decision accountability	Seals the approval of AI models, each recommendation and the human review and decision that followed it.	QMandate, QLog, QTrace
QSource	Sensor and intelligence provenance	Seals capture, processing history and release decisions of sensor data, recording the digest of its security label rather than its content.	Qstamp, QTrace
QBuild	Software and firmware provenance	Seals build history, software bills of materials and release approvals, with release keys held in hardware.	QTrace、Qstamp
QCustody	Materiel custody	Seals every handover of equipment against its unique item identifier, with two signatures and reconciled running totals.	QSign, QGov engine
QEvidence	Evidence custody	Seals the collection and every transfer of evidence for investigations under the law of armed conflict.	Qstamp, QSign, QTrace
QMaint	Maintenance and release to service	Seals maintenance work and release to service, which fails unless a separate inspector has signed.	QSign, QGov engine
QCredential	Qualifications and credentials	Seals 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.

テストネットワークで最初のファイルをスタンプするにはどうすればよいですか？

自分だけが読み取れる署名鍵を作成します。

openssl rand -hex 32 > signer.key
chmod 600 signer.key

次のスクリプトを account.js として同じフォルダに保存し、node account.js で実行します。アカウントのアドレスが表示されます。

const fs = require('fs');
const { Client, core } = require('@quantovainc/qcore');

const seed = Uint8Array.from(Buffer.from(fs.readFileSync('signer.key', 'utf8').trim(), 'hex'));
const client = new Client('https://rpc-testnet.quantova.org', { expectedChainId: 'Q-test-net-1' });
const address = core.address(seed, 0);

client.account(address).then(async (account) => {
  console.log('address  ' + address);
  console.log('balance  ' + account.balance + ' quon');
  if (account.has_key) return console.log('status   registered, ready to stamp');
  if (account.balance === '0') return console.log('status   claim test TQTOV at the faucet');
  const { outcome } = await client.register(seed, 0, '100000');
  console.log('status   registration ' + outcome.verdict);
});

テストネットワークのフォーセットで、そのアドレス宛てに無料の TQTOV テスト用ユニットを請求します。
もう一度 node account.js を実行します。ユニットが届いた時点で、アカウントがネットワークに登録されます。登録は、アカウントごとに1回だけ必要です。
ファイルをスタンプし、そのレシートを検証します。

npx qstamp stamp report.pdf --seed-file ./signer.key --index 0 --kind record
npx qstamp verify report.pdf.qstamp.json --file report.pdf

テストネットワークでは、アンカリングトランザクション1件あたりの費用は、ファイルの数にかかわらず 0.005 TQTOV です。signer.key は秘密にし、バックアップを取っておいてください。signer.key を持っている人は誰でも、ご自身のアカウントとして署名できてしまいます。

Eight SDKs for the integrity of defence records.

What each SDK seals.

Profiles for robotic and uncrewed systems.

QMission · Signed mission mandates

QBoot · Firmware signing and secure boot

QRecorder · Flight and mission recorder

QTelemetry · Telemetry and sensor provenance

QKeyring · Platform key lifecycle

Shared by every defence SDK.

Separate role keys

Sequenced series

CNSA 2.0プロファイル

Sovereign anchoring

独立検証

オープンソース

Qstamp とは何ですか？

レシートは何を証明し、何を証明しないのですか？

公開記録とは、当社のプロンプトやデータが公開されることを意味するのですか。

Qstamp はどの程度のエネルギーを使用しますか？

Qstamp SDK はどのように入手できますか？

テストネットワークで最初のファイルをスタンプするにはどうすればよいですか？

Qstamp を AIエージェントと連携させるにはどうすればよいですか？

どの記録種別を使用できますか？

qdock.io の QIDE を使って Quanta コントラクトテンプレートをデプロイするにはどうすればよいですか？

Qstamp は規制要件にどのように対応していますか？

AIエージェント企業が今 Qstamp を導入すべきなのはなぜですか？

Qstamp は最も高度なAIエージェントにも使用できますか？

Quantova は私の記録を閲覧したり保存したりしますか？

費用はどのくらいかかりますか？

監査人や規制当局は、どのようにレシートを検証しますか？

Qstamp の証跡が耐量子で安全なのはなぜですか？

サポートにはどのように連絡すればよいですか？