From 1dc80d77df0f791c8fefba817953128524ff144d Mon Sep 17 00:00:00 2001 From: Kody Sale Date: Wed, 8 Jul 2026 13:48:11 -0700 Subject: [PATCH] Document nuances and limits from user feedback --- pages/methodology.tsx | 66 ++++++++++++++++++++++++++++++++++++++++++ styles/methodology.css | 7 +++++ 2 files changed, 73 insertions(+) diff --git a/pages/methodology.tsx b/pages/methodology.tsx index df8b5ed..1c2a8c6 100644 --- a/pages/methodology.tsx +++ b/pages/methodology.tsx @@ -145,6 +145,72 @@ export default function MethodologyPage() { Client diversity uses a simplified banded model; live network client share thresholds are deferred to a future operator registry (v1.2 spec).

+

+ If no answer fits your setup, pick yellow — the{" "} + nuances and limits section lists the known cases. +

+ + +
+

Nuances and limits

+

+ This section lists the nuances the assessment leaves out, so you can weigh them + yourself. +

+ +

Why three colors

+

+ 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.

+ +

The remote signer stack

+

+ 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. +

+ +

Hosting provider type

+

+ 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. +

+ +

CPU generation

+

+ 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. +

diff --git a/styles/methodology.css b/styles/methodology.css index 5bee7fc..59e642e 100644 --- a/styles/methodology.css +++ b/styles/methodology.css @@ -32,6 +32,13 @@ color: var(--vb-green); } +.vb-methodology__main h3 { + font-size: 15px; + font-weight: 700; + margin: 20px 0 8px; + color: var(--fg-1); +} + .vb-methodology__lede { font-size: 15px; line-height: 1.6;