Method
Why yields differ, and how they are calculated
Two sources of yield
When you stake FLR with a validator on the P-chain, you receive two separate rewards in each reward epoch (3.5 days, i.e. 104.29 epochs per year).
Vocabulary: technically, the P-chain records this staking as a “delegation” of stake to a validator’s node, a legacy of Avalanche, from which it derives. That is why Flare’s documentation and wallets talk about delegation for the P-chain. On this site, “staking” means this operation and “WFLR delegation” means the other mechanism, on the C-chain, with no lock-up.
- The “mirror” share. The validator is also a data provider (FTSO, FDC). Its P-chain stake gives it weight in the protocol, and part of the FTSO and FDC rewards is passed on to those who staked with it. This is the share that varies from one validator to another.
- The “staking” share. A separate pool, split among the nodes by the Flare Foundation. It is almost the same everywhere, apart from the node fee.
Why small validators pay more
A provider’s weight in the protocol follows this formula, checked against the distribution files:
weight = (5 × P-chain stake + delegated WFLR, capped)0.75
Rewards are roughly proportional to weight, and weight grows more slowly than stake. The reward per FLR therefore falls as the validator grows: a validator ten times bigger distributes about 44% less per FLR on the mirror share. The provider’s technical performance adds a spread of around ±10% around this trend.
Over these 8 epochs and 98 validators: median yield 9.11%, stake-weighted average 8.10%.
In practice: a large stake lowers the yield of the chosen validator. The simulator takes this into account.
The calculation, step by step
- Mirror yield = rewards passed on to the validator’s nodes (type 3 claims) ÷ P-chain stake used for vote power × 104.29.
- Staking yield = sum of the stakers' rewards ÷ sum of the amounts staked with the validator × 104.29.
- Net yield = sum of the two, averaged over 4, 8 or 26 epochs. Simple rate, no compounding.
- An epoch in which the validator is not eligible, or not registered, counts as 0 in the average.
Both fees are already deducted: the provider’s FTSO fee on the mirror share, the P-chain node fee on the staking share. They can differ for the same validator.
Where the data comes from
- flare-foundation/fsp-rewards : FTSO and FDC rewards per beneficiary, weights, eligibility, inflation pools.
- flare-foundation/reward-scripts : staking reward per node, self-bond, fee, end date.
Each epoch on record keeps the commit of both repositories and the fingerprint of the files read: any figure shown can be recalculated from these files. Only per-validator aggregates are kept; no data about individual addresses is stored or displayed.
In epoch 450, the protocol emitted 25.6 M FLR: 9.0 M for the FTSO, 9.0 M for the FDC, 7.7 M for staking.
Limits and unverified points
- Two snapshots taken at two different times. The stake used for the mirror share and the one used for the staking share are not taken at the same block. Each yield is correct on its own basis; their sum is an approximation.
- Remaining capacity. Calculated with the official cap of 15 × the self-bond (source, confirmed by the data: no node above it since epoch 300), based on the P-chain state at 2026-11-18 at 17:09 UTC (public indexer of the Flare Foundation). Nodes created since epoch 450 are not yet linked to their validator. The P-chain state is read every 30 minutes from the Flare Foundation’s public indexer; for epoch 450, this reading reproduces the official snapshot node by node (identical self-bond, end date and fee, total stake within 2 billionths of an FLR). Capacity also takes into account the maximum size of a node, 300 M FLR: FIP.16 (section 5.1) raised it from 200 to 300 M, as the data confirms (no node above 300 M). The documentation page cited still says 200 M.
- Staking share. Read from the Flare Foundation’s calculation code (
reward-scripts,src/utils/rewards.ts): each staked FLR receives the same share, apart from the node fee; the “boost” goes to the validator; an entity’s weight is capped at 5% of the network stake (none reaches it so far, the largest is close to 4.8%). - Differences between the two sources. They are recorded and shown on the validator’s page, without correction. Over epochs 443 to 450:
- Node with an FTSO weight but missing from the staking snapshot : 8
- Provider not registered on the FTSO side for this epoch (yield counted as 0) : 13
- Node linked to an entity that was never registered : 1
- Node present in the staking snapshot but missing from the FTSO registration : 2
- Past yield. It is no guide to future yield: validators' stakes, their eligibility and the pools change.