0x178d3a69178d…178d3a6c

ConfirmedInfrastructure661 vB25 sat/vB3 min decode

Wormhole to cut Linea, Moca and Plume support on December 2

Wormhole will disconnect Linea, Moca and Plume on December 2, 2026. Users must move bridged assets back before a phased shutdown halts outbound transfers.

Wormhole to end support for Linea, Moca, and Plume on December 2, 2026
WitnessWormhole to end support for Linea, Moca, and Plume on December 2, 2026AI-generated

Outputs

  1. Support for Linea, Moca and Plume ends on December 2, 2026.

  2. Wormhole announced the change on November 4, 2026, leaving a four-week migration window.

  3. Portal removes the three chains before the Guardians disconnect their full nodes.

  4. Inbound transfers may continue only if at least 13 of 19 Guardians sign messages.

  5. Wormhole already deprecated Berachain, X Layer, Mantle, Injective and Fantom in 2026.

By Elena Vasquez

Wormhole will end support for Linea, Moca and Plume on December 2, 2026, requiring holders of bridged assets to return them to their origin chains before disconnection. The protocol announced the change on November 4, leaving a four-week window; its notice tells users to “send them home to their origin networks” before that date.

The decision came from Wormhole’s Guardian Network, the validator group that runs the protocol’s operations. Wormhole’s stated goal is to “strengthen security and keep the platform sustainable,” although the announcement provides no chain-level traffic, cost or security data showing how each retirement meets that objective.

What changes on December 2?

The shutdown will unfold in two phases. First, Portal, Wormhole’s bridge interface at portalbridge.com, will remove the three chains from its frontend. Second, the Guardians will disconnect the full nodes they operate for those networks. After that step, outbound messages and token transfers from all three chains will stop.

Wormhole’s instruction for affected holdings is direct: bridge Wormhole-bridged tokens back to their origin chain through Portal before December 2. After the Guardians disconnect the nodes, the protocol gives no guarantee of a clean exit for wrapped assets that remain behind.

Portal may remove the chains before the December 2 node cutoff, so waiting until the final days could leave users without the familiar interface while the stated deadline has not passed. Wormhole gave no separate delisting date, making the possible earlier removal the practical deadline for moving funds.

Can inbound transfers still work?

Wormhole leaves one conditional exception. Inbound transfers to the three affected chains may stay available during the transition, but only if at least 13 of the 19 Guardians keep signing messages.

The threshold represents more than two-thirds of the validator set, reflecting Wormhole’s security model’s requirement for a supermajority to attest to each message. Without 13 signatures, a message does not pass.

The announcement does not state how long inbound support will remain available, how a falling signer count would be handled, or whether another bridge offers an exit. It also does not preserve outbound transfers after node disconnection. The conditional inbound route is therefore an exception, not an extension of the exit deadline.

Why is Wormhole pruning networks?

Wormhole has already deprecated Berachain, X Layer, Mantle, Injective and Fantom during 2026. The removals fit a broader effort to drop lower-activity connections in favor of higher-volume routes, according to the protocol.

Every supported chain requires Guardians to run and maintain a full node. Wormhole says a connection without enough traffic may not justify that expense, which makes each retirement a resource decision as well as a network change.

The current cuts also expose how quickly support can turn over. Plume, an EVM-compatible chain focused on real-world applications, joined Wormhole’s supported set in 2025, while Wormhole integrated Moca in early 2026. Moca’s connection would therefore last less than one year before the December cutoff.

Wormhole did not disclose chain-level activity, node-cost figures, incident data or a specific threat assessment for the three removals. That omission prevents independent verification of the claimed savings and security benefit, even though node maintenance carries a real cost in the protocol’s model. The removals may reduce operating expense, but the announcement does not quantify the savings or substantiate a specific security case.

What should users verify next?

Users should first identify whether they hold Wormhole-bridged tokens on Linea, Moca or Plume, then use Portal to send those assets back to the networks from which they originated. This action does not depend on the inbound exception, because outbound transfers cease after the node disconnection.

The next concrete checkpoint is the Portal delisting, but Wormhole has not supplied a separate date for it. Until the protocol confirms that Portal will remain available through December 2, users should assume the interface may disappear before the headline node cutoff.

via Crypto Briefing (Source)

More from Elena Vasquez

Elena Vasquez

Show full bio

Staff writer covering regulation, policy and their impact on crypto and web3 industry at Mempool Brief.

1,525 articles