×
Turboflakes Grade
era 10252
ยท captured 2026-11-09T11:13:13.171352
This grade does not affect your rewards or slashing risk.
It measures parachain-backing performance only - useful as a quality signal for nominators, not a financial penalty.
One or more signals are flagged - open the explainers for likely causes.
Grade
C+
โผ below par
Explain
What this is. Turboflakes grades each para-validator per era. A para-validator is a validator picked by the relay chain each session to verify parachain blocks - assignment rotates so every active validator takes turns.
The 9 bands (best to worst): A+, A, B+, B, C+, C, D+, D, F. The grade is computed from your vote ratio (75%) and bitfield ratio (25%) - see MVR and BAR tiles for the inputs.
Yours: C+ - Worth investigating - see explanation below.
Calculated by Turboflakes from on-chain parachain backing data for era 10252.
MVR - Missed Vote Ratio
0.87%
โฒ excellent
Explain
What this is. When you back a parachain block as a para-validator, you cast one of three votes:
- Explicit - you ran the block yourself and signed off. (86 this era)
- Implicit - you trusted another validator's signed vote. (141 this era)
- Missed - you cast neither. (2 this era - these hurt your grade)
Formula filled with your numbers:
MVR = missed / (missed + implicit + explicit)
= 2 / (2 + 141 + 86)
= 0.87%
Bands:
- < 5% - excellent
- 5โ10% - healthy
- 10โ20% - slightly elevated
- > 20% - flagged with โ glyph by Turboflakes
Network median this era: 0.24%
- yours is
significantly above median - likely a node-side problem.
Calculated by Turboflakes from on-chain parachain backing data for era 10252.
BAR - Bitfield Availability
6.73%
โ falling behind
Explain
What this is. Separately from voting, every validator (not just para-validators) signs a small message each block - called a bitfield - declaring which parachain blocks they currently have the data for. This is how the network knows a parachain block is safe to finalise.
Formula filled with your numbers:
BAR = signed / (signed + missed)
= 235 / (235 + 3256)
= 6.73%
Bands:
- > 99% - healthy
- 95โ99% - mild lag, usually transient
- < 95% - node not keeping up with relay-chain block production
Likely causes (relay-chain side, not parachain-side):
- Relay-chain sync lag - different from parachain sync. Verify the relay-chain client is current:
curl -s localhost:9933 -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"chain_getBlock","id":1}' | jq -r '.result.block.header.number'
- Network partition - you can produce votes but can't gossip bitfields. Verify libp2p listening port is reachable from outside.
- Clock skew - bitfields are time-bounded; NTP drift can invalidate them:
chronyc tracking | grep 'System time' # offset should be < 100ms
Calculated by Turboflakes from relay-chain block data for era 10252.
Para-validator inclusion:
100.0%
- fraction of sessions in this era when you were picked to back parachains.
Random rotation (every ~10 sessions on Polkadot) - informational, not a quality signal.
Per-parachain breakdown (current session - live)
Loading current session dataโฆ
Last 28 eras
ยท
12 amber, 1 red
in last 28
- this era is your
13th
non-healthy era
Avg MVR: 4.7%
Best: 0.0% (era 10227)
Worst: 64.48% (era 10238)
ฯ: 13.74 pp (drifting)
Hover any bar to see the era's data
network median MVR
era 10225
โ para-validator era
era 10252
Pattern:
drifting.
MVR varies a lot between eras - likely intermittent issues worth investigating.
Last 7 eras:
improving - recent avg 1.07% vs prior 5.91% (ฮ -4.84pp).
Network rank:
Bottom 30% by MVR in 16/28 eras - your node is below network norm.
Para-validator role:
picked in 28/28 eras
- this is rotation by the relay chain, not a quality signal. Eras where you weren't picked have no MVR/grade.
Data calculated by Turboflakes ONE-T - open-source para-validator scoring.
turboflakes/one-t