Validator Hub
Run a validator on Quantara
Join the core security set for Devnet-0 and the upcoming public testnet. Harden the network, earn reputation, and get ready for mainnet.
Quantara is built for long-term security in a post-quantum world. Validators are the first line of defense — producing blocks, finalizing chains, and proving that our cryptography and runtime design hold up under real load.
Devnet-0 is a curated validator set focused on stability and incident drills. The public testnet opens up to a wider group of operators, infra providers, and community validators ahead of mainnet in 2026.
If you want to be early on Quantara — as a validator, RPC provider, or infra partner — this is where you start.
Network snapshot
Final validator set, slashing parameters, and economics will be published in the Devnet-0 and testnet docs. Treat all test networks as experimental and non-financial.
Overview
Why Quantara cares so much about validators
Elite Devnet-0 and the public testnet are where we prove Quantara’s validator story under real-world conditions before mainnet.
Validators are the backbone of Quantara’s security model. They produce blocks, participate in finality, and give us continuous feedback on how the node, runtime, and ops tooling behave under pressure.
Elite Devnet-0 is our proving ground for validator operations: key management, upgrades, incident response, and monitoring. The public testnet opens this up to a broader set of operators before we flip the switch on mainnet.
Every drill, fork, and runtime upgrade here is intentional: we want validators who can handle real chaos, not just happy-path uptime.
Current snapshot of the active network stage you’ll be targeting as a validator, plus core identity parameters for QTR.
Requirements
What we expect from Quantara validators
Elite Devnet-0 and the public testnet are where we prove out validator operations before mainnet. Here’s what you should be ready for.
Running a validator on Quantara is more than keeping a node online. We’re looking for operators who treat security, observability, and automation as first-class citizens.
As a validator, you should be comfortable with:
- • Managing Linux servers (systemd services, log files, updates, firewall rules).
- • Using monitoring and alerting (Prometheus/Grafana or similar) for CPU, disk, memory, networking, and block production.
- • Rotating keys and keeping signing material safe — never storing secrets in plain text or on shared machines.
- • Applying runtime upgrades and node releases without excessive downtime.
- • Participating in incident drills and reporting issues with clear logs and diagnostics.
Networks are test-only:
- • All QTR on Devnet-0 and the public testnet is non-financial test QTR.
- • Expect chain resets, parameter changes, and deliberate failure scenarios.
- • The goal is to harden the path to mainnet, not maximize short-term rewards.
Recommended baseline for Devnet-0
These requirements will evolve as we publish more benchmarks and finalize mainnet parameters. Always check the latest validator docs before committing hardware at scale.
Step-by-step
Validator readiness checklist
A practical sequence to go from zero to Devnet-0 and public testnet-ready validator on Quantara.
Step 1
EnvironmentPrepare your infrastructure
- • Provision a dedicated Linux server or high-quality VPS.
- • Configure SSH, firewall rules, and basic hardening.
- • Ensure reliable power, connectivity, and backups.
Step 2
NodeInstall and run the Quantara node
- • Follow the Devnet-0 node install guide from the docs.
- • Sync against the current Devnet-0 chain-spec.
- • Verify logs, peers, and basic block import.
Step 3
MonitoringWire telemetry & monitoring
- • Expose Prometheus metrics from your node.
- • Set up dashboards for CPU, RAM, disk, p2p, and blocks.
- • Configure alerts for downtime and missed authorship.
Step 4
Keys & SecurityGenerate and protect validator keys
- • Generate keys on a secure machine using the documented flow.
- • Store seed phrases and key material offline.
- • Never paste secrets into shared terminals or chats.
Step 5
Devnet-0Join Elite Devnet-0 as a validator
- • Follow the validator onboarding steps in the docs.
- • Register your keys and confirm authorship is working.
- • Participate in incident drills and upgrade rehearsals.
Step 6
Testnet & MainnetPrepare for public testnet and mainnet
- • Track changes to hardware, networking, and slashing in docs.
- • Automate upgrades and restarts as much as possible.
- • Stay active in Discord validator channels and status updates.
FAQ
Questions about validating on Quantara
Quick answers about running validators on Devnet-0, incentives, and the path toward mainnet.
Who can become a validator on Quantara?
ValidatorsWe’re looking for operators who take security, monitoring, and automation seriously—whether you’re an individual, a small team, or an infra provider. If you can reliably run Linux servers, handle upgrades, and participate in incident drills, you’re in the target group.
Does Devnet-0 or the public testnet use real QTR?
ValidatorsNo. All QTR on Devnet-0 and the public testnet is test-only and has no financial value. These networks exist to harden the protocol, runtime, and validator operations before mainnet launches.
Do I need bare metal hardware, or is cloud OK?
ValidatorsFor Devnet-0 and the public testnet, high-quality cloud instances are acceptable as long as you can meet uptime, performance, and security expectations. As we approach mainnet, we’ll publish clearer guidance on bare metal vs cloud tradeoffs.
Will there be slashing on Devnet-0 and testnet?
ValidatorsWe’ll experiment with slashing-style behavior during Devnet-0 and testnet to model mainnet conditions, but any penalties remain purely testnet-only. Final slashing parameters will be documented before mainnet.
How do Devnet-0 and testnet connect to mainnet?
ValidatorsPerformance, uptime, and participation on Devnet-0 and the public testnet help us identify high-quality operators. This doesn’t guarantee a mainnet spot, but it strongly influences validator program design and early invitations.
Where do I get help if I’m stuck?
ValidatorsStart with the validator docs, then jump into the Discord validator channels with logs, config snippets, and a clear description of the issue. We’ll use real incidents to improve both the protocol and the documentation.