Qstamp / Sovereign networks

Sovereign Quantova networks

A private post quantum ledger that never leaves the secure environment.

Classified and operationally sensitive records can never be anchored on a public network, because even a salted commitment reveals the timing and volume of activity. A sovereign Quantova network runs the same post quantum ledger entirely inside a national or coalition secure environment, with its own genesis and validators and no connection to the public network. It is being built for release as open source under the same licences as the rest of the Quantova stack.

Design

What a sovereign network is.

Own genesis

Each network starts from its own genesis block, created in a witnessed ceremony, and shares no state or history with the public network.

Own validators

Validators are run by the operating authority inside its accredited environment and sign finality with ML DSA.

No external connection

Nodes connect only to each other through ML KEM and ML DSA handshakes, and the network has no route to the internet.

Offline installation

Nodes are installed from a signed offline kit, verified against published fingerprints before use.

Controlled export

Where policy allows, an approved commitment can be passed outward through an accredited cross domain solution, and never inward.

Same verification

Records anchored on a sovereign network are verified by the same open procedure, by verifiers inside the environment.

Live flow

Inside the secure environment, in motion.

Live flowSovereign network, from a classified system to an authorised verifier

Your systemsClassified systemA record is created and signed inside the secure environment
Your systemsQDefence SDKThe record is fingerprinted and batched under its record kind
Quantova networkSovereign networkThe commitment is anchored by validators inside the environment
Quantova networkFinalityThe block is finalised by the authority's own validator committee
PublicAuthorised verifierA cleared auditor verifies the record against the sovereign anchor
PublicApproved exportOnly where policy allows, a commitment passes outward through a cross domain solution

Inside your systemsQuantova networkPublic and verifiable

Release path

How a sovereign network is delivered.

01Node package
A reproducible package of the Quantova node with its configuration for a private network.
02Genesis ceremony
A witnessed procedure that creates the genesis and the validator keys of the network.
03Offline kit
A signed installation kit that can be verified and installed without any network.
04Export gateway
A one way export of approved commitments for use with a cross domain solution.
05Pilot
A first network on an isolated environment, verified end to end.
06Review and release
Security review and open source release of the kit.

Périmètre

What a sovereign network does not change.

A sovereign network is a separate deployment of the Quantova software for one operator. It does not change the rules of the public Quantova network, and accreditation of each deployment remains with the authority that operates it.

Comment horodater mon premier fichier sur le réseau de test ?

Créez une clé de signature que vous seul pouvez lire.

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

Enregistrez le script suivant sous le nom account.js dans le même dossier et exécutez-le avec node account.js. Il affiche l’adresse de votre compte.

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);
});

Obtenez gratuitement des unités de test TQTOV pour cette adresse auprès du distributeur (faucet) du réseau de test.
Exécutez de nouveau node account.js. Une fois les unités reçues, le script inscrit votre compte sur le réseau. L’inscription n’est nécessaire qu’une seule fois par compte.
Horodatez un fichier et vérifiez son reçu.

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

Chaque transaction d’ancrage coûte 0.005 TQTOV sur le réseau de test, quel que soit le nombre de fichiers. Gardez signer.key secret et sauvegardé. Toute personne qui le détient peut signer au nom de votre compte.

A private post quantum ledger that never leaves the secure environment.

What a sovereign network is.

Own genesis

Own validators

No external connection

Offline installation

Controlled export

Same verification

Inside the secure environment, in motion.

How a sovereign network is delivered.

What a sovereign network does not change.

Qu’est-ce que Qstamp ?

Que prouve un reçu, et que ne prouve-t-il pas ?

Un registre public signifie-t-il que nos prompts ou nos données deviennent publics ?

Quelle quantité d’énergie Qstamp consomme-t-il ?

Comment obtenir le SDK Qstamp ?

Comment horodater mon premier fichier sur le réseau de test ?

Comment intégrer Qstamp à un agent d’IA ?

Quels types d’enregistrement puis-je utiliser ?

Comment déployer les modèles de contrat Quanta au moyen de QIDE sur qdock.io ?

Comment Qstamp contribue-t-il au respect des exigences réglementaires ?

Pourquoi les entreprises d’agents d’IA devraient-elles intégrer Qstamp dès maintenant ?

Qstamp fonctionne-t-il pour les agents d’IA les plus avancés ?

Quantova voit-elle ou stocke-t-elle mes enregistrements ?

Combien cela coûte-t-il ?

Comment un auditeur ou un régulateur vérifie-t-il un reçu ?

Pourquoi les preuves Qstamp offrent-elles une sécurité post-quantique ?

Comment contacter l’assistance ?