QUANTARA • QUANTUM-RESISTANT L1
Quantara glossary for Devnet-0
A shared vocabulary for validators, builders, and operators working on Quantara Devnet-0 — and later, the public testnet and mainnet.
Docs • Glossary
Quantara glossary for Devnet-0
Use this page as a quick reference for the terms we use across Devnet-0 docs, runbooks, and status updates. Clear language makes it easier to debug, coordinate, and upgrade together.
Quantara sits at the intersection of blockchains, infrastructure, and security engineering. That comes with a lot of jargon. This glossary focuses on the words you'll see most often in Devnet-0 docs and incident notes.
The definitions here are intentionally short and practical. When in doubt, we link to the deeper docs — like the Devnet-0 overview, Validator runbook and Incident Response pages.
As Devnet-0 evolves into public testnet and mainnet, we'll expand this glossary with more protocol, governance, and tokenomics terms.
If you see a term in any Quantara doc that doesn't make sense, assume it's our documentation's fault, not yours. Ask questions and help us keep this glossary sharp.
Sections on this page
1 • Network stages & environments
How we talk about Devnet-0, testnet, and mainnet
These terms describe which network we mean and what level of stability / expectation comes with it.
- Devnet-0 (Devnet)
- Our internal-first, builder-focused rehearsal network. We regularly upgrade, restart, and stress-test it. Test tokens only; not for real value.
- Public Testnet
- The open, long-running network that follows Devnet-0. Used for wallets, explorers, and dApps to integrate before mainnet.
- Mainnet
- The production Quantara network carrying real value. Changes are slower and heavily scrutinized. Devnet-0 and testnet exist to make mainnet boring.
- Localnet
- A local, single- or multi-node network you run yourself, usually via our scripts. Safe place to experiment with configs and new code.
- Epoch / Era
- A repeating period of blocks used for session rotation, staking, and rewards. Exact parameters will be published closer to mainnet.
- Devnet snapshot
- The current canonical set of RPC endpoints, explorer URLs and metadata for Devnet-0. Surface on this site and in docs.
- Status page (/status)
- The public page where we announce incidents, maintenance and network state. Always the source of truth for live updates.
- Explorer
- A web UI to browse blocks, extrinsics, accounts and events. Useful for checking heights, finality, and chain health.
- RPC endpoint
- An HTTP or WebSocket URL exposing JSON-RPC methods for the node. Wallets, explorers and tools connect here.
2 • Protocol & chain concepts
Core on-chain and runtime terminology
Short, operator-friendly definitions for the pieces that make Quantara tick under the hood.
- Block
- A batch of transactions and state changes, produced roughly every fixed interval (e.g. 6 seconds) on Quantara.
- Finality
- The point where a block is economically and cryptographically locked in. On Quantara, GRANDPA handles finality for Devnet-0.
- Runtime (state transition function)
- The Wasm-compiled business logic of the chain: pallets, extrinsics and on-chain rules.
- Node
- The Quantara binary running on a server or VM, responsible for syncing blocks, verifying state and serving RPC. Can run as a full node, validator, or RPC node depending on flags.
- Chain specification (chain-spec)
- A JSON file describing network identity, initial validators, genesis state and properties. Devnet-0 specs are built via our tooling and scripts.
- Genesis state
- The initial on-chain state at block zero: balances, authorities, and configuration values.
- QTR / decimals / SS58
- Quantara's native token uses symbol QTR, 12 decimals and SS58 prefix 73 for addresses.
- Extrinsic / transaction
- A signed or unsigned request to execute some runtime logic, such as transfers, staking operations, or governance actions.
- Benchmarking
- Systematic measurement of runtime and node performance to set weights and capacity limits. See the Benchmarks guide.
3 • Roles, keys & security
Who runs what — and which keys they use
These definitions show up across the validator runbook, incident response, and security checklist docs.
- Validator
- A node that participates directly in block production and finality. Validators stake tokens and can be slashed for bad behavior.
- Nominator / delegator
- An account that backs one or more validators with stake to share in rewards and risks. Exact mechanics will be documented closer to public testnet.
- Operator / SRE
- The human responsible for running and monitoring the validator or infra nodes. Often the primary audience for runbooks and this glossary.
- Stash / controller / session keys
- A three-part key model for validators: stash holds stake, controller manages actions, session keys live on the node for consensus. See the Key Management & Backups doc.
- Slashing
- A mechanism where stake is reduced for misbehavior such as downtime or equivocation. Devnet-0 uses mostly simulated slashing to practice habits.
- Incident (Sev-1/2/3)
- A network or infra issue classified by severity. See Incident Response for exact definitions.
- Postmortem (incident report)
- A structured write-up after an incident covering impact, timeline, root cause and follow-ups. See the Postmortem template.
- Runbook / checklist
- A step-by-step operational guide (runbook) or a concise set of checks (checklist). Examples: validator runbook, security checklist, rollback runbook.
- Threat model
- A document outlining what we're defending against: attacker capabilities, targets, and assumptions. Forms the backdrop for security decisions on Quantara.
4 • Tooling, endpoints & docs
How wallets, faucets, and scripts fit together
Short definitions for the Quantara tooling ecosystem around Devnet-0.
- Quantara wallet
- The official web wallet and account manager for Quantara networks. Connects to Devnet-0 and future testnets via RPC.
- Quantara faucet
- A service that dispenses small amounts of test QTR to developers and validators on Devnet-0 and testnet. See Wallet & Faucet runbook.
- Local scripts / tooling
- Shell scripts and utilities that build runtimes, generate specs, start localnets and run smoke tests. Referenced throughout the Devnet-0 docs.
- RPC guide & integration guide
- Docs that explain which RPC methods to use, how to connect safely, and how to integrate wallets or apps. See RPC guide and Integration guide.
- Release artifacts
- The binaries, Wasm runtimes, chain-specs and checksums we publish for a Devnet-0 or testnet release. See Release artifacts doc.
- Spec signing & verification
- The process of cryptographically signing chain-specs and verifying hashes so operators know they're running the same network. See Spec signing & verification.
- Known issues & troubleshooting
- Living docs that list recurring problems, rough edges and their current status. See Known issues and Troubleshooting.
- Validator FAQ
- A companion doc answering common validator questions about hardware, upgrades, rewards and more. Linked from the validator hub.
- Devlog
- An ongoing engineering journal of Devnet-0 changes — useful context when reading older incidents or specs.
Next steps
Keep our language sharp as Quantara grows
A good glossary is never finished. As we add new features, we’ll keep the vocabulary clear and aligned across docs, tooling, and status pages.
If you're writing new docs, incident notes, or community posts, reuse the terms and definitions on this page. Consistent language makes it easier for new validators and builders to join Devnet-0 without confusion.
When you find a missing or unclear term, open an issue or PR against the docs repo — or bring it up in the validator channels. The stronger our shared vocabulary, the smoother our path from Devnet-0 to public testnet to mainnet.