Validator self-assessment

A neutral resource for validator fault tolerance

How resilient is your validator setup?

Six quick questions about how you run. Each one checks for a single point of failure — any party, client, provider, machine, or place that, if it broke or turned hostile, could get you slashed, knocked offline, or censored. Your answers fill the pizza and set your Stage. About a minute · nothing is submitted or stored.
All six green = no single point of failure — upholding Ethereum's core values: decentralization, credible neutrality, and censorship resistance.
Stage 0Getting started
One failure could get you slashed
↓
Stage 1Safety
No single failure can get you slashed
↓
Stage 2Liveness
No single failure can take you offline

Or let your AI walk you through it

Paste this into ChatGPT, Claude, or any assistant that can read a URL. It asks the same six questions and hands back your share link.

Read https://validatorbeat.com/skill.md and use it to run the Validator Beat assessment with me (full reference: https://validatorbeat.com/llms-full.txt).

Ask me the six questions one at a time. If my setup falls between two answers, help me pick the worse one; if I can't tell, use "not sure". Then tell me my Stage, which slices hold me back and the cheapest fix for each, and give me my Validator Beat share link.

My setup, to start: [validators, execution and consensus clients, hosting providers and regions, signer / key setup].
For agents: llms.txt · llms-full.txt · skill.md
KeysClientsProviderOSCPUGeoSTAGE–
Your pizza fills in as you answer →
Green · no single point of failure
Yellow · could take you offline, or partly mitigated
Red · one failure could slash you
Not sure · treated as a gap