The Quantova SDK provides all the components needed to start building on the Quantova network — an independent, post-quantum Layer-1 blockchain. It is built on the Polkadot SDK (Substrate, FRAME, Cumulus, and XCM) and extends it with Quantova's post-quantum cryptography, integrated at the signature layer. Quantova is the first to bring a complete post-quantum signature layer into the Polkadot SDK.
This repository is the protocol/runtime SDK. Application and client development on Quantova is done through Quantova's own official client libraries, qweb3.js and qweb3.py (see Client Libraries).
Build a Quantova node from source:
git clone https://github.com/Quantova/quantova-sdk
cd quantova-sdk
git checkout stable2506-pq
cargo build --releaseA getting-started helper is also available in the repository's scripts/
directory. Building from source as shown above works on any supported toolchain.
Quantova ships and maintains its own official client SDKs. Build applications, wallets, services, and tooling on Quantova with these — not with generic Ethereum or Substrate client libraries:
- qweb3.js — the official JavaScript / TypeScript client SDK for Quantova.
Post-quantum key generation and signing (Falcon, Dilithium, SPHINCS+), the
q_*JSON-RPC namespace, the QVM contract layer, QNS.qname resolution, fee estimation, batch requests, event hooks, a REST gateway client, and a CLI. Ships as CommonJS, ES modules, and TypeScript definitions. - qweb3.py — the official Python client SDK for Quantova. The same surface in a
synchronous, web3.py-style API: post-quantum signing, the
q_*JSON-RPC client, the QVM contract layer, QNS, fees, batching, event hooks, a REST client, and theqweb3-clitoolbelt. Python 3.8+.
Both libraries speak Quantova's post-quantum signature layer natively and are the supported, first-class way to interact with the network. The runtime SDK in this repository is for building and running the chain itself; qweb3.js and qweb3.py are for building on it.
Quantova is post-quantum from the signature layer up — there is no ECDSA/secp256k1 anywhere in the account or transaction model. This is the core of what the Quantova SDK adds on top of the Polkadot SDK.
- NIST post-quantum signature schemes. Every account is secured by one of three
schemes, sharing a single address space:
- CRYSTALS-Dilithium (ML-DSA, Dilithium2)
- Falcon-512 (FN-DSA)
- SPHINCS+ (SLH-DSA, NIST FIPS 205)
- Post-quantum signature type. The runtime's transaction
Signaturetype isQSignature, and theAccountIdis derived directly from the post-quantum public key. - SHA3-256 hashing. Block, transaction, and state hashing use SHA3-256.
- Algorithm agility. All three schemes share one account model; schemes can be added or retired through on-chain governance.
This makes the Quantova SDK a drop-in foundation for building parachains and runtimes whose cryptography is quantum-resistant by default, while retaining the full Substrate/FRAME/Cumulus/XCM toolset underneath. Quantova's own client libraries, qweb3.js and qweb3.py, expose this post-quantum signing to applications.
- Quantova Developer Documentation — the canonical developer reference for the Quantova network, accounts, transactions, staking, governance, bridges, and the QVM. Published through official Quantova channels.
- Client libraries — qweb3.js and qweb3.py each ship their own README and API
reference covering installation, quick start, the
q_*RPC surface, the QVM contract layer, and post-quantum signing. - Framework APIs — because the Quantova SDK is built on the Polkadot SDK, the
upstream component documentation applies to the underlying framework:
- Polkadot SDK rust-docs for Substrate, FRAME, Cumulus, and XCM.
- Polkadot and Substrate StackExchange for framework-level questions.
- Quantova-specific questions can be directed through official Quantova channels.
The Quantova SDK tracks the Polkadot SDK's stableYYMM release cadence. This
repository is maintained on the stable2506-pq branch — the stable2506 base with
Quantova's post-quantum integration. Release notes and process are in
docs/RELEASE.md.
You can use psvm to align Polkadot SDK
dependency versions in a Cargo.toml file.
Polkadot SDK Version Manager (psvm): a tool
to manage and update Polkadot SDK dependencies in any Cargo.toml. Since the
Quantova SDK is based on the Polkadot SDK, psvm applies to the upstream
dependencies it inherits.
The security policy and procedures can be found in docs/contributor/SECURITY.md. Please report security issues privately through the channels described there; do not open public issues for suspected vulnerabilities.
Please follow our contribution guidelines. In every interaction and contribution, this project adheres to the Contributor Covenant Code of Conduct.
This repository is a derivative of the Polkadot SDK, itself the amalgamation of the former Substrate, Polkadot, and Cumulus repositories. The Quantova SDK preserves that foundation and adds the post-quantum signature layer, Quantova-specific pallets and primitives, and the Quantova runtime configuration. We are grateful to the upstream maintainers and the broader Substrate community whose work this builds on.
Quantova SDK is published by Quantova Inc. (Singapore).
The Quantova-developed portions of this repository — including the post-quantum cryptography integration, Quantova-specific pallets and primitives, and the Quantova runtime and protocol code — are licensed under the Business Source License 1.1 (BUSL-1.1), © 2026 Quantova Inc. See LICENSE and LICENSE-OVERVIEW.md for the full text, parameters, and the canonical-network definition. The qweb3.js and qweb3.py client libraries are likewise published by Quantova Inc under BUSL-1.1 in their own repositories.
This repository is built on the Polkadot SDK. Components derived from the Polkadot SDK remain subject to their original upstream licenses — primarily GPL-3.0-or-later (with the Classpath exception) and Apache-2.0, as indicated in the headers of the respective files and crate manifests. Those upstream licenses continue to govern the upstream-derived code; see the individual files and the Polkadot SDK repository for details.