Quantova Dev Base Template

A minimal, opinionated starter for building on Quantova, the post-quantum Layer 1 for institutional settlement. Click Use this template to scaffold a new project that can read chain state, deploy a QRC20 contract to the Quantova Virtual Machine (QVM), and send signed transactions through the q_ JSON-RPC API — against testnet today, mainnet later with only a config change.

New to Quantova? Read the developer documentation first. This template assumes you understand Q-format addresses, the post-quantum signing model, and the QVM at a high level.

---

Quickstart

# 1. Use this template (or clone it)
git clone https://github.com/Quantova/dev-base-template.git my-quantova-app
cd my-quantova-app

# 2. Install dependencies
npm install

# 3. Configure your environment
cp .env.example .env
#   then edit .env with your RPC endpoint and (testnet) deployer key

# 4. Read chain state to confirm connectivity
npm run interact

# 5. Deploy the example QRC20 to testnet
npm run deploy:testnet

Full, step-by-step instructions are in docs/getting-started.md.

---

What's inside

Path	What it is
src/	A reusable q_ JSON-RPC client and network config.
contracts/	An example QRC20 token contract for the QVM.
scripts/	Deploy and interact scripts using the SDK + RPC client.
test/	A starter test that exercises the RPC client against a node.
docs/	Setup, project structure, deploying, and interacting guides.
.github/workflows/ci.yml	CI: install, lint, test.
.env.example	Template for endpoints and keys (never commit .env).

---

Documentation

Guide	Covers
Getting Started	Toolchain, install, .env, testnet faucet, first read.
Project Structure	What every folder and file is for.
Deploying	Compiling and deploying a QVM contract via q_sendRawTransaction.
Interacting	Reading balances, sending transactions, waiting for finality.

---

Networks

Environment	WebSocket	HTTP JSON-RPC
Testnet	wss://testnet.quantova.io	https://testnet.quantova.io
Local dev node	ws://127.0.0.1:9944	http://127.0.0.1:9933

Get free TQTOV for testing from the faucet (see Getting Started). Moving to mainnet changes only the RPC endpoint and chain id — the Q-address scheme and SDK are identical.

---

Conventions this template follows

• Addresses are Q-format strings (Q-prefixed), never 0x EVM addresses.
• Numeric RPC results are QUANTITY hex; convert with parseInt(x, 16) (÷ 10^18 for QTOV).
• Block references are block-number QUANTITY values — the named tag "latest" is not implemented.
• Transactions are signed locally with a post-quantum key, then broadcast with q_sendRawTransaction.
• Value is settled on finality (~3s), not on inclusion.

Links

• Website: https://quantova.org
• Developer documentation: https://quantova.org/static/pdfjs/web/viewer.html?file=/static/pdf/Gitbook-Quantova-Developer-Documentation.pdf#nameddest=cover&page=1&pagemode=bookmarks
• Developer content: the developer-content repository
• Consensus specifications: the consensus-specs repository
• Security policy & bug bounty: the security-documentation-repository

Contributing

See CONTRIBUTING.md.

License

© 2026 Quantova Inc. See LICENSE.md.