★ Bridge ecrecover checks result ≠ address(0)
Babylon Protocol's assessment for RD-F-151 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Structurally inapplicable. Babylon does not use Ethereum ecrecover for any cross-chain operation. Bitcoin-side uses Schnorr multisig (BIP 340 / Taproot) where invalid signatures are rejected at Bitcoin consensus layer — no separate zero-address check needed or possible. Genesis chain uses CometBFT BLS/Ed25519 and EOTS (Extractable One-Time Signatures). No EVM bridge contract exists. Profile meta.json explicitly lists ecrecover bridge validation (F151) as a non-EVM gray factor. CRITICAL ★ factor is not_applicable (not red) by structural architectural mismatch — do NOT penalize grade.
Sources #
- GitHubBabylon x/finality — EOTS not ecrecoverProfile meta.json non_evm_flags.evm_factors_structural_gray includes ecrecover bridge validation (F151). evm: false, solidity: false.retrieved 2026-05-04
- Babylon staking script — Schnorr / Taproot cryptographic modelStaking script docs — Taproot + Schnorr multisig (BIP 340) on Bitcoin; no ecrecover patternretrieved 2026-05-04
Methodology #
Determine whether the bridge verifier code rejects `ecrecover` returns of `address(0)`.
See the full factor methodology and distribution across all protocols →