| Validators | Self-bond | Delegators | Delegated | Total | Reward Cap |
|---|---|---|---|---|---|
| 0 | 0 FLR | 0 | 0 FLR | 0 FLR | 0 FLR |
| All validators — per-node metrics | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Provider↑ | Node ID | Total Stake | Cap | Free Space | Fee | Delegators | Start Date | End Date | Time UTC | Time Left | Uptime | Version | Up |
See how validator staking and FTSO delegation rewards compare for your FLR amount.
Compare RewardsData provided by Flare Metrics.
FAQ
How should I evaluate a Flare validator?Show
Evaluating a validator on Flare involves looking at more than just total stake. Uptime, time left in the current staking period, delegation fees, and how close a validator is to key caps all affect both security and potential rewards. On this page, Flare Builders surfaces self-bonded stake, delegated stake, free space, delegator counts, version information, and whether each node is currently connected. You can sort by any of these columns to build a shortlist of validators that match your preferences.
As a delegator, it is often sensible to prefer validators with strong uptime, up-to-date software, and capacity remaining rather than those that are already near reward caps. Diversifying across multiple well-performing validators can also reduce the impact if a single operator experiences issues or changes their fee policy.