This page is the authoritative guide for teams who want to run validators or full nodes on RVA SmartChain. RVA is looking for experienced operators with a professional approach to infrastructure.
Participation is subject to technical review, security checks and ongoing performance monitoring.
Validators are responsible for producing blocks and participating in the Proof of Staked Authority consensus that secures SmartChain. By proposing and signing blocks, they confirm transactions, keep the ledger consistent and help enforce protocol rules.
Non-validator node operators play an important supporting role. Full nodes maintain a complete copy of the blockchain, relay transactions and blocks, and provide reliable RPC endpoints for wallets, dApps and exchanges.
Uphold network integrity
Consistent uptime required
Participate in protocol decisions
Participate directly in PoSA consensus. Propose blocks, validate transactions and sign blocks. Requires stake, reliable infrastructure, and strong monitoring.
Keep a complete and up to date view of SmartChain, verifying every block. Act as trusted RPC endpoints for wallets, exchanges, indexers and dApps.
Maintain extended historical state for analytics or regulatory reporting. Useful for projects that need to reconstruct detailed on-chain history.
Running SmartChain infrastructure is not a casual activity. Operators are expected to treat their nodes as production systems that carry real economic value.
RVA does not prescribe a single vendor or cloud provider. What matters is that node operators can demonstrably keep systems running, patched and monitored to the standard expected of institutional infrastructure.
Modern, server-grade hardware or cloud instances sized for consistent performance.
High-availability network with stable bandwidth and low latency.
Hardened OS configurations, access control and regular patching.
Operational playbook covering monitoring, alerts, backups and incident response.
A typical SmartChain validator deployment follows a layered architecture. Consensus nodes should be kept lean and locked down, holding validator keys and connecting to a limited set of peers. API traffic should be served from separate full nodes to offload query load.
[Image of EVM architecture diagram]
Infrastructure should be deployed behind firewalls and private networks. Access is controlled via VPN or zero trust mechanisms. Backups of chain data and configuration must be created and tested regularly to ensure rapid recovery.
Validator keys must be generated and stored in secure environments. Use hardware security modules or secure key stores. Never transmit keys in plaintext.
Disable unnecessary services, enforce least-privilege access, and use strong authentication. Keep systems patched against known vulnerabilities.
Monitor logs for intrusion attempts. Have a predefined incident response plan including isolation and key rotation ready.
Healthy nodes are observable nodes. SmartChain operators are expected to measure and monitor performance in real time. Key indicators include node availability, block height, sync status, and block production success.
Tools such as Prometheus for metric collection and Grafana for visualization are recommended.
Becoming a SmartChain validator is a structured process. It begins with an expression of interest, outlining infrastructure experience and security practices. Selected candidates are invited to a testnet probation period to demonstrate reliability.
Upon successful evaluation and meeting stake requirements, operators may be added to the mainnet active set. Participation is not permanent; validators remain subject to performance monitoring.
Validators earn rewards for consistently producing valid blocks. Rewards are distributed proportionally to stake and performance. Consistent uptime and correct block signing are key to maximising rewards.
Conversely, failure to meet expectations carries penalties. Extended downtime or malicious behavior can result in slashing of stake, temporary jailing, or removal from the active set. The goal is to align incentives for a stable, professional network.
Treat validator keys as highly sensitive assets.
Run nodes on dedicated, hardened environments.
Monitor continuously and respond to alerts promptly.
Test backups and recovery procedures instead of assuming they will work.
Document runbooks for team incident response.
RVA maintains dedicated channels for validators to raise issues, share observations, and receive updates on releases. Official announcements regarding upgrades and governance are published here. During incidents, RVA coordinates closely with validators to restore operations.
Contact RVA SmartChain Team