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

Quantum safe infrastructure that was never classical.

Durable evidence depends on the infrastructure that witnesses it. The Quantova Virtual Machine and its validator network have used post quantum signatures since the first block. Other infrastructure can adopt post quantum keys for the future, but its past remains signed with keys that a quantum computer will break.

PropertyQuantova with QstampLedgers secured by elliptic curve signaturesClassical time stamp authoritiesHardware enclave notaries
Account and transaction signaturesML DSA 65 since the first blockECDSA or EdDSARSA or ECDSAECDSA attestation keys
Finality signaturesML DSA 65 committee certificatesBLS or ECDSA where usedSingle authority signatureSingle enclave signature
History verifiable after quantum computers arriveYes, every blockOnly blocks after a future migrationRequires renewed time stampingDepends on fused classical keys
Who witnesses the recordIndependent validator committeeNetwork validatorsOne providerOne hardware vendor
Control over executed codeAttested compiler signature requiredAny bytecode may be deployedNot applicableVendor attestation
Confirmation timeAbout 0.2 secondsSeconds to many minutesImmediateImmediate
Record content disclosedNever, salted commitment onlyDepends on applicationDigest onlyDepends on design

The comparison reflects typical deployments of each category as of 2026. Hash based chains secured by proof of work retain hash security for ordering, but signer identities on them remain classical.

The stack

Every layer chosen for longevity.

Q Crypto

An implementation of FIPS 202, FIPS 204 and FIPS 205 written for the Quantova stack, with constant time sampling, validated against the NIST test vectors.

Quantova Virtual Machine

A metered register machine with native ML DSA and SLH DSA verification, hashing and hash tree instructions, executing only attested contract code.

Quanta smart contracts

A contract language whose authority model comes only from verified signatures. Reentrancy cannot be expressed, and code that forges authority does not compile.

QORUS consensus

Byzantine fault tolerant finality from a sampled committee whose certificates are signed with ML DSA 65.

QCore SDKs

Client libraries for JavaScript, Rust and Python that sign with ML DSA 65 and treat signing seeds as wipeable byte buffers.

Qstamp SDK

The evidence layer described on this site, published as open source with three Quanta contract templates.

Timelines are already set

The United States requires federal systems to adopt post quantum signatures by the end of 2031. The European Union and India target 2030 for high risk and critical systems, and the United Kingdom and Canada 2031. The European Union, the United Kingdom and Canada set 2035 for completion. Australia sets 2030. Records created today will be inspected well within these horizons.

Reviewed before release

Before publication, the Qstamp SDK and contract underwent a security review covering cryptographic design, code and chain integration, and every finding was resolved or documented. An external audit by an independent qualified firm is recommended before reliance in production.