LayerZero OFT DVN config (count, threshold, diversity)
Lista DAO's assessment for RD-F-179 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
DVN configuration NOT CONFIRMED via available tooling — pipeline returned dvn_addresses: [] and dvn_threshold: null (false negative confirmed). Direct on-chain getConfig() call to EndpointV2 required. OFT deployed July 2024 — prior to Kelp DAO (Apr 2026) public awareness of 1/1 DVN risk. Audits (BlockSec + PeckShield, June 2024) pre-date heightened 1/1 DVN scrutiny. setEnforcedOptions() function confirmed in ABI suggests customization was likely applied but DVN count not readable. 47% of LZ OApps post-Kelp analysis use 1/1 DVN. Transfer limiter (daily cap per-address, per-chain) provides partial exposure control. Yellow: real but unconfirmed 1/1 risk; transfer limiter partially mitigates. F179 is NOT a critical factor; not counted in 19 star critical total.
Sources #
- AuditBlockSec OFT Audit June 2024BlockSec OFT audit June 2024 — covers OFT contract code but pre-dates Kelp DVN scrutinyretrieved 2026-05-12
- Dune: 47% OApps use 1/1 DVN post-KelpPost-Kelp Dune analysis: 47% of LZ OApps use 1-of-1 DVN configurationretrieved 2026-05-12
- ListaOFTAdapter BSC — enforced options ABIbscscan.com/address/0x82f5bcD1473BDa5794239D01073797093a413f02 — setEnforcedOptions() ABI confirmed; source verifiedretrieved 2026-05-12
- Lista DAO data cache DVN false negative00-data-cache.json layerzero.dvn_threshold: null — false negative confirmed per U6 patternretrieved 2026-05-12
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 →