LayerZero OFT DVN config (count, threshold, diversity)
Beefy Finance's assessment for RD-F-179 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
The BIFI LZ bridge adapter (0xdddaEc9c267dF24aD66Edc3B2cBe25dB86422051) is LayerZero v1 — confirmed by NonblockingLzApp inheritance and ILayerZeroEndpoint v1 interface. DVN (Decentralized Verifier Network) is a LayerZero v2 concept; LZ v1 uses Oracle+Relayer pair model. F179 measures DVN count, threshold, and diversity for LZ v2 OFT integrations — not applicable to LZ v1 adapters. Cache data (dvn_addresses=[], dvn_threshold=null, dvn_configs=[]) accurately reflects the v1 architecture despite the layerzero_bridge=false false negative (U6).
Sources #
- InternalBeefy data cache — LZ DVN fields empty due to v1 architecture00-data-cache.json sources.layerzero — dvn_addresses:[], dvn_threshold:null, dvn_configs:[] accurately reflect LZ v1 architecture (not a data gap)retrieved 2026-05-16
- LayerZero bridge adapter — confirmed LZ v1 (not DVN-based v2)LZ adapter 0xdddaec... — 'NonblockingLzApp' inheritance, 'ILayerZeroEndpoint' v1 interface, 'setTrustedRemote' pattern; confirmed LZ v1 not v2 OAppretrieved 2026-05-16
Methodology #
For any LayerZero OFT adapter, read the DVN configuration: count of DVNs, k-of-N threshold, and operator diversity (independent operators vs same-operator multi-DVN).
See the full factor methodology and distribution across all protocols →