defirisk.co
rubric v1.7.0

Bridge validator count (M)

A cross-chain & bridge factor in the v1.7.0 rubric. Measured per protocol on a s cadence.

Methodology how we score#

What this measures
This factor records the number of distinct validators or signers in the bridge's signer set — or, for LayerZero OFT integrations, the count, threshold, and operator diversity of the Decentralised Verifier Network (DVN) configuration. The count is derived from bridge contract reads and protocol documentation. This factor applies only to bridge-touching protocols; non-bridge protocols show this factor as N/A.

Why it matters
Validator count directly determines the minimum attacker footprint required to forge a bridge message. Harmony Bridge ($100M, 2022) used a 2-of-5 multisig with hot-wallet signers; compromising two keys was sufficient to drain the bridge. The Kelp DAO rsETH hack ($292M, 2026) exploited a 1/1 DVN configuration on a LayerZero OFT adapter — a single validator node controlled the entire message verification path, reducing the attack surface to a single key compromise. The T-01 evidence base links low validator counts to approximately 7 protocols, and the Kelp DAO incident has elevated the threshold-of-1 edge case to a near-critical finding for LayerZero deployments.

Green / Yellow / Red
Green is scored when the bridge uses 7 or more independent validators (or DVN operators for LayerZero) with documented geographic and organisational independence. Yellow is scored when the count is 3–6 with partial independence documentation. Red is scored when the validator count is 1 or 2, or when a LayerZero OFT uses a single DVN operator.

Common gray cases
Gray is applied when validator identity and independence cannot be confirmed from public on-chain or documentation sources.

Notable historical examples
- Kelp DAO ($292M, 2026): 1/1 LayerZero DVN configuration; single validator controlled rsETH message verification.

Measurement what to look for#

Count the number of distinct validators or signers in the bridge's signer set (for non-LZ bridges; use F179 for LayerZero OFT).

Data & output #

Data source
Bridge contract `getValidators()` / `signers()` or equivalent via RPC + bridge docs
Output format
Green / Yellow / Red
Evidence artifact
Validator address list + count + bridge contract address
Confidence signal
green = ≥7 validators; yellow = 4–6 validators; red = ≤3 validators; gray = LayerZero OFT (use F179 instead) or bridge contract not identifiable

Scored protocols 0 carry this factor#

No protocols have been scored for this factor yet.

Linked hacks 1 historical incident#

causalKelp DAO (rsETH liquid restaking): Forged cross-chain message via LayerZero EndpointV2 lzReceive — exploitation of 1/1 DVN (single-validator) configuration2026-04-18 · $292M · Forged cross-chain message via LayerZero EndpointV2 lzReceive — exploitation of 1/1 DVN (single-validator) configuration · Bridge validator count (M) — LayerZero DVN sub-field [via cross-hack: Factor 80: DVN / Multi-Validator Configuration on Cross-Chain Messages]
rubric_version v1.7.0factor RD-F-148category 10carried 0critical no