LayerZero OFT DVN config (count, threshold, diversity)
Sushi (SushiSwap) — v2 + v3 + Trident + BentoBox/Kashi + SushiXSwap'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 #
Sushi does NOT operate its own LayerZero OApp or OFT adapter. Data-cache: layerzero.present: false, oapp_address: null, dvn_addresses: []. SushiXSwap v2 routes through Stargate's OApp (not a Sushi-owned OApp); the StargateAdapter and SquidAdapter in the sushixswap-v2 repo are routing wrappers that call into Stargate/Squid — they do not configure DVNs. F179 applies to protocols that own and configure a LayerZero OApp with its own DVN set; Sushi is a consumer of Stargate's OApp, not the OApp owner.
Sources #
- InternalData-cache §layerzero — no Sushi-owned OApp detectedrisk-dashboard/.research/protocols/sushi/00-data-cache.json §layerzero — present: false, oapp_address: null, dvn_addresses: [], dvn_configs: []retrieved 2026-05-16
- SushiXSwap v2 GitHub — no Sushi OAppsushiswap/sushixswap-v2 — StargateAdapter and SquidAdapter are routing wrappers, not Sushi-owned OApp with DVN configretrieved 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 →