Everything required to run a validator on the Quantova network: the consensus rules you are agreeing to enforce, the hardware and stake requirements, the exact commands to build and run a node, the JSON-RPC surface for operating it, the fee and reward economics, and the slashing rules that apply if you misbehave.
Validators secure Quantova by staking QTOV, authoring blocks, and voting in finality. This is a capital and operational commitment: the minimum self-stake is high on purpose, uptime is enforced, and safety faults forfeit the entire stake. Read the consensus rules and slashing rules before you bond anything.
- 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
- Testnet:
wss://testnet.quantova.io· for faucet at https://Qtox.io for free test net assets.
| Step | Guide | What it covers |
|---|---|---|
| 1 | Consensus Rules | NPoS, deterministic no-VRF leadership, and finality — what a validator enforces. |
| 2 | Requirements | Minimum self-stake, hardware, network, and the staking parameters. |
| 3 | Build & Run a Node | Build from source and run a validator node, with every command. |
| 4 | JSON-RPC & Node API | The q_ and author_ namespaces for operating and monitoring the node. |
| 5 | Validator Economics & Fees | The four revenue streams, commission limits, the reward formula, and APR. |
| 6 | Slashing & Penalties | Downtime and safety faults, penalties, and permanent bans. |
| 7 | Activation Checklist | The end-to-end sequence from build to active in the validator set. |
Bond a stash of at least $50,000 USD-equivalent in QTOV, run a node with --validator,
generate and register your session keys, then submit staking.validate. You are considered
at the next era boundary (epochs are 24 hours) and elected into the active set (capped at
200 at maturity) by combined self and nominator stake. You earn block issuance plus shares of
priority fees, MEV, and bridge attestation fees, net of your commission. Miss too many blocks and
you are slashed for downtime; threaten finality or a bridge and you forfeit 100% of stake and
are permanently banned, with the slashed amount routed to the Quantova treasury.
The normative consensus rules are specified in the
Post-Quantum-Consensus-specs repository — NPoS, the no-VRF
slot-leadership design, and deterministic finality. This guide is the operational companion to
that specification.
| Repository | Purpose |
|---|---|
| Post-Quantum-Consensus-specs | Normative consensus specification. |
| developer-content | Developer documentation source, including the node and JSON-RPC reference. |
| dev-base-template | Starter template for building on Quantova. |
| security-documentation-repository | Security policy and bug bounty. |
visit > https://hackenproof.com
© 2026 Quantova Inc. See LICENSE.md. This guide is operational documentation the protocol parameters it describes are enforced by code and amendable only through on-chain governance.