×
Turboflakes Grade
era 9713
· captured 2026-06-27T22:16:48.171919
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
F
✗ poor
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: F - Likely a problem on your node - see possible causes.
Calculated by Turboflakes from on-chain parachain backing data for era 9713.
MVR - Missed Vote Ratio
100.0%
✗ flagged
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. (0 this era)
- Implicit - you trusted another validator's signed vote. (0 this era)
- Missed - you cast neither. (912 this era - these hurt your grade)
Formula filled with your numbers:
MVR = missed / (missed + implicit + explicit)
= 912 / (912 + 0 + 0)
= 100.0%
Bands:
- < 5% - excellent
- 5–10% - healthy
- 10–20% - slightly elevated
- > 20% - flagged with ✗ glyph by Turboflakes
Network median this era: 0.22%
- yours is
significantly above median - likely a node-side problem.
Likely causes (in order of frequency, with diagnostic commands):
- Node out-of-sync - even a few seconds behind misses votes. Check:
curl -s -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","method":"system_health","id":1}' localhost:9933
isSyncing must be false.
- CPU/disk under-resourced - para-validation runs WASM in ~2s. Check:
htop # sustained CPU > 80% on validator process is a red flag
iostat -x 1 # await > 20ms on the data disk is bad
- Slow network to other validators in your group - your "group" is the ~5 para-validators backing the same parachain as you this session. Check libp2p peer count and ping to your peers.
- Crashes or restarts during the era - parachains produce a block every ~6s, so even brief downtime misses many votes:
journalctl -u polkadot-validator --since '6 hours ago' | grep -iE 'panic|restart|killed'
Calculated by Turboflakes from on-chain parachain backing data for era 9713.
BAR - Bitfield Availability
0.12%
✗ 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)
= 4 / (4 + 3474)
= 0.12%
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 9713.
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
·
1 amber, 17 red
in last 28
- this era is your
18th
non-healthy era
Avg MVR: 62.97%
Best: 0.0% (era 9292)
Worst: 100.0% (era 9696)
σ: 48.28 pp (drifting)
Hover any bar to see the era's data
network median MVR
era 9292
■ para-validator era
era 9713
Pattern:
drifting.
MVR varies a lot between eras - likely intermittent issues worth investigating.
Last 7 eras:
worsening - recent avg 100.0% vs prior 50.02% (Δ +49.98pp). Worth investigating recent changes (config, OS updates, hardware).
Network rank:
Bottom 30% by MVR in 21/27 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