A minimal starter template for building on Quantova, the sovereign post quantum Layer 1 built from scratch. Use this template to scaffold a project that reads chain state, deploys a contract to the Quantova Virtual Machine, and sends signed transactions through the gateway. It targets the testnet today.
Quantova is post quantum end to end. Every signature is ML-DSA-65 and every key exchange is ML-KEM-768, and there is no elliptic curve and no classical public key cryptography anywhere in the chain, so nothing in it is vulnerable to Shor's algorithm. The chain is at the testnet and pre audit stage and external audits are still ahead. Do not treat it as audited or production ready.
- Reading chain state from the gateway with a small client.
- A QAsset fungible token written in Quanta and compiled to a QVM container.
- The shape of a deploy transaction, signed with QCore.js and submitted to the gateway.
The virtual machine is the QVM, a register machine that runs compiled containers. It is not the Ethereum virtual machine and it is not wasm. Consensus is QORUS, a committee byzantine fault tolerant protocol with ML-DSA-65 finality and a budget bounded sortition committee. Cryptography is Q-Crypto, a from scratch NIST post quantum suite with ML-DSA-65 for signatures, ML-KEM-768 for key exchange, SLH-DSA, SHA-3 and SHAKE, and ChaCha20-Poly1305 for the transport channel. Addresses are Q1 bech32m strings written with a capital Q. The asset is QTOV and its base unit is the Quon, where one QTOV is one million Quon. The testnet asset is TQTOV. The contract language is Quanta, where whole classes of exploits fail to compile. The fungible standard is QAsset and the non fungible standard is QCollectible. The name service is QNS, with domains under a capital Q top level like Jeff.Q.
git clone https://github.com/Quantova/dev-base-template.git my-quantova-app
cd my-quantova-app
npm installPoint the client at a gateway.
export QUANTOVA_GATEWAY="http://127.0.0.1:8080"
npm run interactSet QUANTOVA_GATEWAY to your gateway endpoint. The current testnet gateway URL is listed in the developer documentation. A local node serves the gateway on port 8080 by default.
client.jsis a dependency light client over the gateway. Every call is an HTTP POST to /v1/ with a flat JSON body.interact.jsreads node info, the chain head, chain parameters, supply, and an optional account balance.ExampleQAsset.quantais a QAsset fungible token written in Quanta.deploy.jsbuilds a deploy transaction, signs it with QCore.js, and submits it to the gateway.getting-started.md,interacting.md,deploying.md, andproject-structure.mdare the guides.
The gateway is an HTTP POST to /v1/ with a flat JSON body. The methods are node_info, head, validators, chain_params, get_account, get_transaction, submit_transaction, get_block, supply, get_container, get_storage, and get_events. The full reference is in the developer documentation.
The client SDK is the QCore family. QCore.rs is the Rust core. QCore.js is published on npm as @qunatovainc/qcore. QCore.py is the Python binding. Use QCore.js for key management and for signing transactions with ML-DSA-65.
- Addresses are Q1 bech32m strings written with a capital Q. There are no 0x addresses.
- Amounts are denominated in Quon, and one QTOV is one million Quon. Divide a Quon amount by one million to read QTOV.
- Reads and submissions go through the gateway over HTTP POST to /v1/.
- Transactions are signed locally with an ML-DSA-65 key using QCore.js, then submitted with submit_transaction.
- A recorded transaction is included. Value is settled on QORUS finality, and a finalized block does not reorg.
- Website https://quantova.org
- Developer documentation, listed on the website
- Developer content, the developer-content repository
- Consensus specifications, the consensus-specs repository
- Security policy and how to report, the security documentation repository
Quantova Inc, 2026. See LICENSE.