From 1dc80d77df0f791c8fefba817953128524ff144d Mon Sep 17 00:00:00 2001
From: Kody Sale
+ If no answer fits your setup, pick yellow — the{" "} + nuances and limits section lists the known cases. +
+ + ++ This section lists the nuances the assessment leaves out, so you can weigh them + yourself. +
+ ++ Real setups don't fall into neat green, yellow, and red buckets. We use three + colors anyway because they keep a result easy to read at a glance. If your setup falls + between two answers, pick yellow. If the gray area hides a single point of failure, + pick red. +
+Known cases the questions don't spell out:
+If you hit an ambiguity we haven't listed, pick yellow.
+ ++ Every current signing stack keeps a single point of failure somewhere, whether you run + Web3Signer, Dirk, Vero, Vouch, or Charon. Validator Beat doesn't score it: + penalizing something no setup can avoid would push everyone toward one architecture. +
+ ++ Validator Beat doesn't rank residential, bare metal, or cloud hosting. The + Infrastructure slice already scores provider concentration, which catches the real + trap: five regions all on AWS still fall to one provider incident. +
+ ++ Validator Beat counts instruction sets and ignores chip generations. Hardware bugs + sometimes hit one generation and sometimes a vendor's entire line, so mixing + generations guarantees nothing. +