01
Consensus
Keep the system in agreement.
A distributed validator set confirms network activity and supports reliable block production.
Validator network
Secure the network. Earn its trust.
Run reliable infrastructure, participate in consensus, and help keep Ramestta available for the applications built on it.
Built for the full stack
Operators turn infrastructure into trust.
Validators maintain the execution environment, participate in consensus and keep the network accountable.02
Operations
Run infrastructure with a visible role.
Operator performance connects directly to the network availability applications depend on.
03
Incentives
Stake aligns participation with health.
RAMA supports the economics that reward reliable validation and long-term security.
Validator checkpoint lifecycle
From Bor blocks to a checkpoint commitment.
Validators participate in the checkpoint path through Heimdall: a proposer builds the checkpoint, the validator set verifies it, and the signed commitment is submitted to the Polygon RootChain contract.- Bor block range
Blocks accumulate
Bor produces the block range that will be represented by the checkpoint.
- Checkpoint proposer
Build the commitment
The selected Heimdall proposer constructs the block-range and Merkle-root commitment.
- Validator quorum
Verify and sign
Validators attest the proposed checkpoint. The protocol requires 2/3+ agreement.
- Polygon RootChain
Submit checkpoint
The signed checkpoint is submitted to the Polygon-side RootChain contract.
- Protocol outcome
ACK or NO-ACK
A successful submit advances the checkpoint lifecycle; a failed attempt follows the NO-ACK/proposer-change path.
A successful submission produces the protocol ACK path. A failed or timed-out submission enters the NO-ACK and proposer-change lifecycle; it is not a reason to restart unrelated node services.
Checkpoint lifecycle, visually
Bor blocks → proposer → 2/3 signatures → RootChain → ACK
A checkpoint bundles a Bor block range and its Merkle root. The Heimdall proposer builds it, the validator set signs it with 2/3+ agreement, and the signed commitment is submitted to Polygon's RootChain — producing an ACK, or a NO-ACK that triggers a proposer change.
Validator Requirements
Meet these requirements to become a Ramestta validator
Minimum Stake Amount
1,000,000 RAMA required to become a validator
99.9% Uptime
Maintain high availability for network reliability
Validated Checkpoints
Sync checkpoints with Polygon PoS layer
Hardware Requirements
Recommended specifications for running a production validator node
CPU
Minimum:8 Cores
Recommended:16+ Cores
Modern x86-64 processor (AMD EPYC or Intel Xeon recommended)
Storage
Minimum:2 TB SSD
Recommended:4+ TB NVMe
High IOPS NVMe SSD for optimal block processing
RAM
Minimum:32 GB
Recommended:64+ GB
DDR4 ECC memory for production workloads
Network
Minimum:100 Mbps
Recommended:1 Gbps
Low-latency connection with static IP
Earn Rewards by
Multiple ways to earn as a Ramestta validator
Validating Blocks
Earn rewards for successfully validating network transactions and maintaining consensus
Participating in Governance
Vote on network proposals and earn governance rewards (coming soon)
Supporting Network Health
Contribute to network security and decentralization while earning consistent rewards
How to Get Started
Follow these steps to become a validator
1
Setup Node Infrastructure
Deploy and configure your validator node with proper hardware specifications
2
Stake Required Amount
Lock the minimum stake amount to become eligible for validation
3
Register as Validator
Submit your validator registration through the validator portal
4
Start Validating
Begin validating transactions and earning rewards
Network Statistics
Current validator network metrics
60+
Active Validators
99.9%
Network Uptime
2s
Block Time
10K+
TPS Capacity
Validator Economics
Understand how validators earn rewards on Ramestta
Block Rewards
~2.5 RAMA
Per block validated (from 1% annual inflation pool)
Transaction Fees
~30%
Share of priority fees from transactions in your blocks
Checkpoint Rewards
Variable
Additional rewards for checkpoint submissions to Polygon
Annual APY
8-15%
Estimated annual return based on stake and uptime
Reward Calculation Example
For a validator with 5,000,000 RAMA stake:
- ~180 blocks validated per day
- ~450 RAMA in block rewards daily
- ~135 RAMA in transaction fees daily
- ~213,000 RAMA annually (~4.3% APY base)
Note: Actual rewards vary based on:
- • Network transaction volume
- • Your stake weight vs total staked
- • Uptime and block production
- • Delegator commissions (if applicable)
Slashing Conditions
Understand the penalties for validator misbehavior
Double Signing
Signing two different blocks at the same height
5% of stake
Extended Downtime
Missing more than 50% of blocks in a 24-hour period
1% of stake
Checkpoint Miss
Failing to sign checkpoint submissions
Reduced rewards
Slashing Protection Tips
- • Never run the same validator keys on multiple machines
- • Use a remote signer to prevent key exposure
- • Set up comprehensive monitoring and alerting
- • Maintain backup infrastructure for failover
Frequently Asked Questions
Common questions about running a Ramestta validator
Validator Resources
Everything you need to run a successful validator