Stargate Sunset and LayerZero V2 DVN & Executor Migration

Stargate support for GOAT Network ends on October 23rd, 2026, and LayerZero Labs' default DVN (Decentralized Verifier Network) and Executor will stop serving GOAT Network on October 30th, 2026.

Official source: LayerZero Labs, Support Update - July 24, 2026 (last updated September 25th, 2026). LayerZero is winding down its off-chain services and Stargate support across several chains. For GOAT Network, Stargate support ends on October 23rd, 2026 and LayerZero's DVN and Executor services end on October 30th, 2026. The announcement covers LayerZero's off-chain services and Stargate only. The LayerZero V2 contracts on GOAT Network (EndpointV2, SendUln302, ReceiveUln302) remain deployed, and the chain itself, the GOAT canonical bridge, and all GOAT-native assets continue to operate as normal.

This announcement asks two groups to act:

1. Everyone holding Stargate-issued assets on GOAT Network - USDC.e, USDT and WETH - must bridge these assets off GOAT Network through Stargate before October 23rd, 2026. These three tokens are issued by Stargate (Hydra), and Stargate is their only redemption path. See Section 1 below.

2. OApp and OFT developers that bridge to or from GOAT Network must complete the LayerZero V2 DVN and Executor migration before October 30th, 2026. The replacement DVNs and Executor are live today - GOAT Network's own BTCB and DOGEB OFTs already run on them. See Section 2 below.

Deadlines: Bridge out USDC.e, USDT and WETH by October 23rd, 2026 · LayerZero V2 configuration migration by October 30th, 2026

1. Token Holders: Bridge Out USDC.e, USDT and WETH by October 23rd, 2026

Unlike chains where stablecoins are issued by a canonical bridge, USDC.e, USDT and WETH on GOAT Network are issued by Stargate in Hydra mode. Stargate is their only redemption path. When Stargate support for GOAT Network ends on October 23rd, 2026, these tokens can no longer leave GOAT Network through Stargate, and there is no other issuer-backed exit for them.

In its support update, LayerZero Labs states that USDC.e, Hydra USDT and WETH holders on GOAT should bridge their funds to Stargate Pool chains before October 23rd, 2026 to avoid a loss of funds, and recommends bridging to chains with deeper liquidity such as Ethereum, Arbitrum, Base and BNB Chain.

Addresses are as published in Stargate's developer documentation and can be checked on explorer.goat.network.

How to bridge out

1. Withdraw from DeFi first. If any of these tokens sit in DeFi positions on GOAT Network, for example Oku or GoatSwap liquidity pools or Avalon lending markets, remove the liquidity or withdraw the deposit so the tokens are back in your wallet. Positions do not bridge themselves: only tokens held directly in your wallet can be moved. If you have borrowed against them, repay the loan first.

2. Open Stargate. Go to the Stargate app, connect your wallet, and select GOAT Network as the source chain. The links in the next step open Stargate with GOAT Network and the token already selected.

3. Bridge each token. Bridge USDC.e, USDT and WETH to Ethereum, Arbitrum, Base and BNB Chain are recommended for the deepest liquidity.

4. Confirm arrival. Check the destination chain's explorer or your wallet to confirm the tokens have arrived before considering the transfer complete.

5. Finish before October 23rd, 2026. Do not wait until the final days. Each transfer depends on liquidity being available on the destination chain at that moment, and transfers submitted close to the deadline may not complete in time.

Warning: LayerZero Labs states that failure to act before support is fully deprecated will result in losing access to funds. USDC.e, USDT and WETH left in wallets or DeFi positions on GOAT Network after October 23rd, 2026 may become difficult or impossible to redeem.

Bridging back in

GOAT Network remains open in both directions. BTC continues to move in and out through the GOAT canonical bridge (https://bridge.goat.network), and BTCB and DOGEB continue on the BNB Chain pathway - none of this changes on October 23rd or October 30th.

For USDC.e, USDT and WETH the exit is one-way: Stargate is the only route these assets have had onto GOAT Network, so once support ends on October 23rd, there is currently no route back for them.

2. OApp & OFT Developers: Complete the DVN and Executor Migration

LayerZero Labs' default DVN and Executor stop serving GOAT Network on October 30th, 2026. Any OApp or OFT that still relies on them for a GOAT Network pathway will stop verifying and executing messages on that date. Developers that currently bridge to or from GOAT Network must act before October 30th, 2026. There are two options:

1. Keep supporting GOAT Network by getting your pathways enabled on the DVNs and Executor listed below and updating your LayerZero V2 ULN Send and Receive configurations to use them; or

2. Migrate your OFT or assets to another EVM chain that LayerZero continues to support.

The replacement infrastructure is not new: it is live today, and GOAT Network's own BTCB and DOGEB OFTs already run on it in production on the GOAT Network ↔ BNB Chain pathway. If you have already completed this migration, no further action is needed.

Supported pathways

The new DVNs and Executor support these LayerZero V2 pathways:

• GOAT Network ↔ BNB Chain

• GOAT Network ↔ Ethereum

• GOAT Network ↔ Metis Andromeda

Pathways between GOAT Network and any other chain are not covered by the new DVNs. Applications that use such pathways should migrate before October 30th, 2026.

LayerZero V2 configuration

On every pathway, set both DVNs listed for that chain as required DVNs (requiredDVNCount = 2) and leave the optional DVN list empty (optionalDVNCount = 0, optionalDVNThreshold = 0). This follows LayerZero's production guidance of at least two required DVNs from independent operators (EVM DVN and Executor Configuration), and it is the configuration already running in production on the GOAT Network ↔ BNB Chain pathway.

All addresses below were verified onchain on October 1st, 2026 (see the Appendix below: Address Verification).

Warning: addresses are chain-specific. The same address can be a different contract on a different chain. For example, 0x1bc5…a0f6 is the Executor on GOAT Network but DVN 1 on BNB Chain, and 0x80ee…381b is DVN 2 on GOAT Network but the Executor on Metis. Always take the address from the row of the chain you are configuring.

Recommended values for each pathway:

ULN Send & Receive config

  confirmations:        20

  requiredDVNCount:     2

  requiredDVNs:         [DVN 1, DVN 2] of that chain, sorted ascending by address

  optionalDVNCount:     0

  optionalDVNThreshold: 0

Executor config (Send side)

  executor:             Executor of that chain

  maxMessageSize:       10000

LayerZero requires requiredDVNs to be sorted in ascending address order. On Ethereum this means 0x2c4679… (Metis) comes before 0x812ed6… (GOAT Network); on GOAT Network, BNB Chain and Metis the order shown in the table is already ascending. LayerZero's documentation also requires the Send configuration on one chain to match the Receive configuration on the other chain for the same pathway, so apply identical values on both sides.

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 GOAT Network 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.

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 GOAT Network 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.

6. Complete all of the above before October 30th, 2026.

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

LayerZero V1

GOAT Network is a LayerZero V2-only chain. There is no LayerZero V1 endpoint on GOAT Network, so LayerZero's separate V1 wind-down does not apply here.

Other OApps and OFTs on GOAT Network

The Stargate Hydra OFTs (USDC.e, USDT, WETH) are covered by the Stargate sunset in Section 1 and will not be migrated. Any other V2 OApp or OFT on GOAT Network that still uses the LayerZero Labs default DVN or Executor will stop working on October 30th, 2026. If your project runs an OApp or OFT on GOAT Network and you have not completed the migration above, contact the GOAT Network team now.

Integration Support

For help with pathway enablement, the LayerZero V2 DVN and Executor migration, or any GOAT Network integration, please contact the GOAT Network team:

Telegram: https://t.me/GOATRollup Discord: https://discord.com/invite/goatnetwork

For questions about LayerZero's own services, see the LayerZero documentation or the LayerZero Discord. For questions about bridging out through Stargate, see the Stargate app.

References

• LayerZero Labs: Support Update - July 24, 2026 (source for the October 23rd and October 30th dates and the holder guidance; last updated September 25th, 2026)

• LayerZero docs: EVM DVN and Executor Configuration

• LayerZero docs: GOAT Mainnet deployment (chain ID 2345, EID 30361)

• Stargate docs: (V2) Supported Networks and Assets (source for the Hydra token addresses on GOAT Network)

• Stargate: Bridge

• GOAT Network explorer: explorer.goat.network

The affected-asset addresses in Section 1 (USDC.e, USDT, WETH on GOAT Network) are as published in Stargate's developer documentation, and the affected-asset list matches LayerZero's support update note for GOAT ("USDC.e, Hydra USDT, and WETH holders on GOAT").