LayerZero OFT DVN config (count, threshold, diversity)
Midas's assessment for RD-F-179 — scored not_assessed on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
LayerZero OFT DVN configuration cannot be assessed — OFT adapter contract addresses for mTBILL/mBASIS are not publicly available (pipeline: layerzero_oapp_address: null; docs.midas.app: 403; Etherscan: no labeled Midas OFT adapter found). Without the OFT adapter address, the DVN configuration (required DVN count, optional DVN threshold, operator diversity) cannot be read from the LayerZero endpoint. This is the primary Cat 10 evidence gap. Context: post-Kelp DAO ($292M, April 2026), 1-of-1 DVN configurations are the key scrutiny point (Blockaid DVN audit gist confirms requiredDVNCount + optionalDVNThreshold <= 1 = catastrophic exposure). Midas's DVN config is material given approximately $56M estimated cross-chain TVL. If 1-of-1 DVN, this factor would be red.
Sources #
- Docs00-data-cache.json — LayerZero sectionpipeline config 00-data-cache.json: layerzero.oapp_address: null, layerzero.dvn_addresses: [] — OFT adapter not registeredretrieved 2026-05-16
- Blockaid LayerZero DVN Configuration Audit GistBlockaid DVN audit gist post-Kelp DAO: requiredDVNCount + optionalDVNThreshold <= 1 = EXPOSED — single DVN compromise enables forged lzReceiveretrieved 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 →