QuantovaQstampby Quantova
EN
EnglishEN日本語JAFilipinoFIL한국어KO简体中文ZHFrançaisFREspañolESУкраїнськаUK
GitHub Start building →
Qstamp / Integrations
Integrations

What the Qstamp family works with today, and what comes next.

The family is designed to be called by the systems organisations already run, at the moment a record is created. This page lists the runtimes, formats, network services and enterprise systems the family supports, and states plainly which are available now and which are being built.

Runtimes and tools

Where the SDKs run.

ComponentIntegrationStatus
Node.js 20 or laterEach SDK is an npm package with its own WebAssembly signing module and no native build stepAvailable
Command lineEach SDK ships a command line tool for keys, sealing, anchoring and verification, with stable exit codes for scriptsAvailable
Other languagesSystems in other languages call the command line tool or a local service wrapping the SDKAvailable as a pattern
TypeScriptType declarations are published with every packageAvailable
Network services

The Quantova network and its tools.

ComponentIntegrationStatus
Official Qstamp contractAnchors commitments under a record kind for each productAvailable on the test network
Quanta contract templatesIssuer and council templates for authorised and multi party anchoringAvailable on the test network
QVMScan explorerPublic view of every anchoring transaction and its record kindAvailable
FaucetTest network funds for development accountsAvailable
Production networkAnchoring with evidential weightIn preparation
Formats and standards

Data formats the family reads and writes.

FormatUseStatus
JSON envelopes and receiptsSigned records and their anchors, stored beside the original recordAvailable
RFC 9162 Merkle proofsInclusion of each record in its anchored batchAvailable
C2PA manifestsProvenance of AI content through QTraceAvailable
FIPS 204 and FIPS 202Signatures and hashingAvailable
CNSA 2.0 profileML DSA 87 with SHA 384 or SHA 512Being built
Enterprise and government systems

How the family connects to existing systems.

In each case the existing system remains the system of record. It calls the SDK when a record is created and stores the sealed envelope and receipt beside its own entry.

SystemProductsIntegration point
AI agent runtimes and orchestrationQstamp, QLog, QMandate, QSignThe tool call layer seals each action and checks each mandate before execution
Model registries and data pipelinesQTrace, QstampModels, data sets and outputs fingerprinted at registration and release
Payment and treasury systemsQMandate, QSpendPayment instructions sealed before release and matched to their authority
Tax administration and electronic invoicingQTaxFilings, invoices, assessments and refunds sealed at intake and decision
Electronic procurement platformsQProcureNotices, bid commitments, scores and awards sealed at each stage
Declaration and case management systemsQDeclareDeclarations sealed at filing and verified in investigations
Benefit and grant management systemsQAidDecisions and disbursements sealed against programme rules
Election management systemsQBallot, QLogStation returns and tabulation actions sealed as produced
Security information and event managementQLogHash chained log segments forwarded with their anchored checkpoints
Key custody

Key custody options.

OptionDescriptionStatus
Application supplied keysThe integrating application passes a 32 byte seed from its own key store and wipes it after useAvailable
Protected key filesCommand line key files readable only by their owner and never followed through symbolic linksAvailable
Hardware security modulesSigning inside certified hardware, so keys never exist outside itNot yet available
FIPS 140 3 validated moduleA validated cryptographic module for federal and regulated useNot yet validated