Bridge signer-set change proposed/executed
Beefy Finance's assessment for RD-F-103 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 v1 production signal (tier-A). BIFI xERC-20 uses four bridge adapters: LayerZero OApp (0xdddaEc9c267dF24aD66Edc3B2cBe25dB86422051, deployed ~2023-10-21 by Beefy Deployer), Axelar, Chainlink CCIP, canonical Optimism bridge. No signer-set change event detected on any adapter at assessment date. Yellow because: (1) LayerZero DVN configuration is unresolved — data-cache shows dvn_configs:[] as a FALSE NEGATIVE; the actual DVN threshold could be 1-of-1 (catastrophic, Kelp DAO class) and this cannot be confirmed or denied from available public data; (2) Axelar and CCIP adapter addresses not resolved. The signal is applicable and production-live; current quiescence is assessed but full bridge security posture is unverified.
Sources #
- DocsBeefy Token Bridge DocumentationBeefy BIFI token bridge — four adapters (LZ, Axelar, CCIP, Optimism canonical)retrieved 2026-05-16
- Beefy LayerZeroBridge Adapter — EtherscanLayerZeroBridge adapter — 0xdddaEc9c267dF24aD66Edc3B2cBe25dB86422051 (Ethereum, deployed by Beefy Deployer)retrieved 2026-05-16
- Beefy XERC20Lockbox — EtherscanXERC20Lockbox — 0xc6e3d0CAF52E057Fb8950ae9d07aE67602919AcD (Ethereum)retrieved 2026-05-16
Methodology #
Detect whether a bridge validator or signer-set change has been proposed or executed.
See the full factor methodology and distribution across all protocols →