On this page

Side-by-side breakdowns of validator pairs stakers actively decide between. Each comparison runs the same metric coverage as the directory profiles, presented in parallel, with explicit "where they're similar" and "where they diverge" sections. No winner is declared; the data leads.

Comparison pages exist for pairings stakers actually search ("Helius vs Figment", "Capital Alliance vs Staking Facilities") and for pairings that illuminate a structural trade-off (independent operator vs exchange-custodied; same datacenter vs different ASN; same commission tier vs split). Selection is metric-driven, not editorial.

Validator-specific data lives in the validator directory; ranked lists by criterion live in evaluation hubs; the Glossary defines terms cited throughout.

All comparisons

How comparison pages work

Each comparison page follows an identical structure so that two pages, read together, are themselves comparable:

  • At a glance — single table covering active stake, Wiz Score, skip rate, base and Jito MEV commission, ASN and city, software version, SFDP eligibility. Same metrics, same order, for every comparison.
  • Where they're similar — bullets covering structural attributes both validators share (client choice, SFDP status, vote-credit ratio band, etc.).
  • Where they diverge — paragraphs covering the axes on which the two split, with the staker-facing meaning of each split.
  • Decision context — short closing paragraph framing what a staker is actually deciding between when they compare these two.

Editorial scope

Comparisons cover validator pairs. Out of scope:

  • Three-way or larger groupings (those belong in evaluation hubs ranked by a single criterion).
  • Pairings where one side is fictional, hypothetical, or not in the directory.
  • Pairings that exist only to surface one validator favorably — every comparison must read fairly to both subjects.

A pairing earns a comparison page when (a) stakers actually search for it (brand-vs-brand, top-2 by stake, frequently-confused pairs) OR (b) it illuminates a structural trade-off that other comparisons do not surface.

Comparisons reflect the Stakewiz API cache snapshot at epoch 971 (2026-05-15). Metrics are re-checked on each wiki refresh; comparisons regenerate when underlying validator data changes materially.