Technical Migration Guide: LayerZero V2 DVN & Executor on Metis Andromeda

Audience: OApp and OFT developers, and owners of contracts that bridge to or from Metis Andromeda.

LayerZero Labs' default DVN (Decentralized Verifier Network) and Executor stop serving Metis Andromeda on October 30, 2026. Any OApp or OFT that still relies on them for a Metis pathway will stop verifying and executing messages on that date.

You have two options:

1. ‍Keep supporting Metis Andromeda: get your pathways enabled on the DVNs and Executor listed below, and update your LayerZero V2 ULN Send and Receive configurations.‍
2. Migrate your OFT or assets to another EVM chain that LayerZero continues to support.

If your project already completed this migration, no further action is needed.

Key dates

1. Supported pathways

The new DVNs and Executor support these LayerZero V2 pathways:

• Metis Andromeda ↔ GOAT Network
• Metis Andromeda ↔ BNB Chain
• Metis Andromeda ↔ Ethereum

Pathways between Metis Andromeda and any other chain are not covered. Applications using them should migrate before October 30, 2026.

2. LayerZero V2 configuration

Configure both DVNs as required DVNs on every pathway, with no optional DVNs.

Recommended values

LayerZero requires requiredDVNs to be sorted in ascending address order. On Ethereum this means 0x2c4679… (Metis) comes before 0x812ed6… (GOAT Network). On Metis, GOAT Network and BNB Chain, the order shown in the tables is already ascending.

The Send configuration on one chain must match the Receive configuration on the other chain for the same pathway. Apply identical values on both sides.

Metis Andromeda (Chain ID 1088) · EID 30151

GOAT Network (Chain ID 2345) · EID 30361

BNB Chain (Chain ID 56) · EID 30102

Ethereum (Chain ID 1) · EID 30101

3. Before you switch: request pathway enablement

The new DVNs and Executor only serve pathways that have been enabled for your application. Each one checks pathwayConfig[dstEid][yourOApp] when a message is sent, and a send to a pathway that has not been enabled reverts. The Executor additionally enforces a maximum message size and minimum and maximum lzReceive gas per pathway.

Send the following to the Metis team before you update your configuration:

• OApp / OFT contract address on each chain
• Each source → destination pathway (EIDs)
• Expected message size and the lzReceive gas your application uses

Also note:

• Do not pass DVN-specific options. The new DVNs reject messages that include DVN options.
• ‍Executor options are unchanged. Keep setting lzReceive gas in your enforced or message options as usual, within the limits agreed for your pathway.

4. How to migrate

For every supported pathway your OApp or OFT uses:

1. List the source and destination chains your application uses.
2. Ask the Metis team to enable your OApp on the DVNs and Executor for each pathway, and wait for confirmation.
3. On both chains of the pathway, call EndpointV2.setConfig on the SendUln302 with the ULN config and the Executor config above.
4. On both chains, call EndpointV2.setConfig on the ReceiveUln302 with the same ULN config.
5. Send a small test message in each direction and confirm that it is verified and executed.

Complete all of the above before October 30, 2026.

Working reference: GOAT Network's BTCB and DOGEB OFTs already run on the GOAT Network ↔ BNB Chain pathway with exactly this setup: confirmations 20, two required DVNs, and maxMessageSize 10000.

5. Bridging back in: keeping both directions working

Users need to be able to move assets in as well as out. After you migrate:

• Configure both directions. Complete steps 3 and 4 on both chains so Send and Receive match on each side of the pathway. A pathway configured in only one direction will leave users able to bridge out but not back in.
• ‍Test both directions. Send a small test message from Metis to the remote chain and from the remote chain to Metis before announcing the migration to users.
• ‍Tell your holders. If you are migrating your OFT to another chain, give holders a clear window and instructions to bridge back to Metis Andromeda before your cut-off.
• ‍LayerZero V1 owners: holders of your bridged tokens on other chains should bridge back to Metis before October 23, 2026. Publish this to your community.

6. LayerZero V1 applications

The sections above apply to LayerZero V2 only. The following integrations on Metis Andromeda still use the LayerZero V1 endpoint (0x9740FF91F1985D8d2B71494aE1A2f723bb3Ed9E4). The new DVNs cannot be configured for them.

Owners of these contracts should contact the Metis team to discuss options before October 23, 2026. Holders of the bridged versions of these tokens on other chains should bridge back to Metis before that date.

7. Known LayerZero V2 integrations on Metis Andromeda

At the time of writing, these V2 OFTs on Metis still use the LayerZero Labs DVN (0x32d4f92437454829b3fe7bebfece5d0523deb475) and are not yet enabled on the new DVNs:

 If your project is listed, or you run any other OApp on Metis Andromeda, please contact the Metis team.

Appendix A: Stargate contracts (for liquidity providers)

Stargate support for Metis Andromeda ends October 23, 2026. Withdraw liquidity before this date. If your LP tokens are staked, unstake first:

• Stargate V2 LP tokens: StargateStaking 0xF1fCb4CBd57B67d683972A59B6a7b1e2E8Bf27E6
• Stargate V1 S*m.USDT: LPStakingTime 0x45A01E4e04F14f7A4a6702c74187c5F6222033cd

Stargate V2 pools

Stargate V1 pools (close on all chains Dec 15, 2026; on Metis, cross-chain messaging stops earlier, so withdraw by Oct 23)

Appendix B: Tokens issued by the Metis canonical bridge (not affected)

These are issued by the Metis canonical bridge (L2StandardBridge 0x4200000000000000000000000000000000000010), not by Stargate or LayerZero. Minting and redemption continue as normal.

Integration support

For pathway enablement, the LayerZero V2 DVN and Executor migration, or any Metis integration, contact the Metis team:

• Telegram: https://t.me/MetisL2

For questions about LayerZero's own services, see the LayerZero documentation. For questions about withdrawing from Stargate, see the Stargate app.

References

• LayerZero Labs: Support Update [September 25,2026]
• LayerZero docs: EVM DVN and Executor Configuration
• LayerZero docs: Metis deployment (chain ID 1088, EID 30151)
• Stargate docs: (V2) Supported Networks and Assets
• Stargate: Bridge