Bridge validator count (M)
Frax Finance's assessment for RD-F-148 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Applies to FraxFerry and Fraxtal OP Stack bridge (non-LZ bridges; F179 covers LZ). Fraxtal: single whitelisted proposer (EOA) — validator count effectively 1 per L2BEAT ('projects without a proper proof system fully rely on single entities to safely update the state'). FraxFerry: 3 named roles (Captain, Crew, First Officer) controlled by Frax team — not an independent validator set. No evidence of ≥7 independent validators for either non-LZ bridge surface. Red based on Fraxtal single-proposer and FraxFerry team-controlled role structure.
Sources #
- DocsFrax FraxFerry Bridge DocsFraxFerry docs — Captain proposes, Crew validates, First Officer executes; all Frax team rolesretrieved 2026-05-17
- L2BEAT FraxtalL2BEAT Fraxtal — 'the proof system isn't fully functional'; 'projects...fully rely on single entities to safely update the state'; single proposer EOA 0x6017...d1f2retrieved 2026-05-17
Methodology #
Count the number of distinct validators or signers in the bridge's signer set (for non-LZ bridges; use F179 for LayerZero OFT).
See the full factor methodology and distribution across all protocols →