LayerZero OFT DVN config (count, threshold, diversity)
Fluid'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 OFT DVN configuration for Fluid's cross-chain operations: the data cache confirms layerzero.present: false for the core Fluid protocol OApp. Fluid Lite uses LayerZero OFT for 'specific tokens' per documentation but specific DVN configuration (count, threshold, operator diversity) not confirmed. No LayerZero OApp address for Fluid or Fluid Lite found in on-chain data or published documentation. Without the OApp address, DVN configuration cannot be read from LayerZero endpoint. Gray — insufficient data to assess. Governance selected CCIP as primary bridge for FLUID token; LayerZero appears secondary for some Fluid Lite token movements. If LayerZero OFT is used, this factor must be re-assessed once OApp address is confirmed.
Sources #
- GovernanceFluid bridge selection — CCIP primarygov.fluid.io/t/fluid-multi-chain-deployment-evaluating-bridge-solutions/1418 — CCIP selected as primary; LayerZero was evaluated but not selected for FLUID tokenretrieved 2026-04-29
- Data cache — LayerZero not detected00-data-cache.json layerzero.present: false — no LayerZero OApp found for core Fluidretrieved 2026-04-29
- Fluid Lite — LayerZero secondary for specific tokenslite.guides.instadapp.io — 'LayerZero OFT bridges depending on the token' — token-specific usage unconfirmedretrieved 2026-04-29
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 →