LayerZero OFT DVN config (count, threshold, diversity)
Concrete's assessment for RD-F-179 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
LayerZero v2 confirmed for PredepostVaultOApp (import @layerzerolabs/oapp-evm-upgradeable; __OApp_init(); no trustedRemote mapping — all LZ v2 indicators; no LZ v1 indicators present). DVN configuration (count, threshold, operator diversity) for the Ethereum-to-Stable-Network and Ethereum-to-Berachain pathways is NOT encoded in the OApp contract source — it is set per-pathway at the LZ v2 endpoint level via SendUln302.setConfig(). The layerzeroscan.com API returned HTTP 429 (rate-limited); no alternative public data source returned the DVN config for this OApp. Honest-null: gap_reason external_api_blocked. HIGH-RISK CURATOR ESCALATION CONDITION: if on-chain query of LZ v2 SendUln302.getAppConfig(oappAddress, dstEid) for either pathway (dstEid for Stable Network or Berachain) reveals DVN threshold = 1/1, Cat 10 becomes RED and F179 is flagged as a critical-candidate warranting T-14 post-launch promotion per the Kelp-DAO $292M Apr 2026 / usual-USD0 / veda-F179 precedent class applied to
Sources #
- GitHubShareDistributor.sol — LZ v2 confirmed; DVN config absentsrc/periphery/predeposit/ShareDistributor.sol — also OAppUpgradeable LZ v2; no DVN configretrieved 2026-05-17
- PredepostVaultOApp.sol — LZ v2 confirmed; DVN config absent from source (endpoint-level only)src/periphery/predeposit/PredepostVaultOApp.sol — import @layerzerolabs/oapp-evm-upgradeable confirms LZ v2; no trustedRemote, no v1 indicators; __OApp_init() in initialize(); no DVN config in source — endpoint-level config requiredretrieved 2026-05-17
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 →