Skip to content

Quantova/become-a-validator

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Become a Quantova Validator

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 an operational commitment: the minimum bond is 1,000 QTOV, you must stay online to author your assigned blocks, and safety faults forfeit the entire stake. Validator yield is intentionally low (capped at 0.2%/yr) — security rests on slashing, not on a high APR. Read the consensus rules and slashing rules before you bond anything.

Read in order

Step Guide What it covers
1 Consensus Rules NPoS, deterministic no-VRF leadership, and finality — what a validator enforces.
2 Requirements Minimum bond, 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 0.2%/yr yield cap, disinflation schedule, fee split, and commission limits.
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.

In one paragraph

Bond a stash of at least 1,000 QTOV, run a node with --validator, generate and register your session keys, then submit staking.validate. You are considered at the next era boundary (an era is ~24 hours; an epoch/session is ~4 hours) and elected into the active set — which has no fixed cap — by combined self and nominator stake. Your reward is capped at 0.2%/yr on bonded stake (the rest of issuance goes to the treasury), plus a 0.2% share of tips and bridge fees, net of your commission. Your bond unlocks 30 eras (~30 days) after you unbond and stays slashable throughout. Miss your assigned 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.

Consensus specification

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.

Related repositories

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

ConsensusLicense

become-a-validator & join our network, We are gretaful for your support

© 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.

About

Everything required to run a validator on the Quantova network — the consensus rules you enforce, hardware and stake requirements, build and run commands, the JSON-RPC operating surface, fee and reward economics, and the slashing rules. Validators secure Quantova by staking QTOV, authoring blocks, and voting in finality.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors