0x2d22dfe12d22…2d22dfe4

ConfirmedInfrastructure747 vB167 sat/vB4 min decode

Wormhole Ends Linea, Moca and Plume Support on Dec. 2

Wormhole will remove Linea, Moca and Plume on Dec. 2, ending outbound transfers after node disconnections while inbound transfers need 13 of 19 Guardian signatures.

Wormhole Will End Support for Linea, Moca and Plume Dec. 2
WitnessWormhole Will End Support for Linea, Moca and Plume Dec. 2LoboStudioHamburg / pixabay

Outputs

  1. Dec. 2 cutoff: Wormhole plans to end Linea, Moca and Plume support.

  2. Nov. 4 announcement: Users were given four weeks to return bridged assets.

  3. 13 of 19 Guardians must sign for inbound messages to pass.

  4. Two-stage sequence: Portal removal precedes full-node disconnections and the outbound shutdown.

  5. Five other 2026 removals: Berachain, X Layer, Mantle, Injective and Fantom.

By Elena Vasquez

Wormhole will end support for Linea, Moca and Plume on Dec. 2, according to its Nov. 4 announcement, which set an outbound-transfer cutoff after Guardians disconnect the affected full nodes.

The announcement stated: "Outbound transfers will stop after Guardians disconnect the full nodes they run for the chains." Wormhole urged holders of bridged tokens on the affected networks to return those assets to their origin networks before the cutoff.

The Nov. 4 notice provided four weeks of lead time, but it did not guarantee four weeks of uninterrupted access. Because Portal goes first, users could lose access to the bridge interface before the node shutdown.

The practical deadline may arrive earlier than Dec. 2 for users who rely on Portal.

What changes at the Dec. 2 cutoff?

The change proceeds in two stages. Portal, Wormhole's bridge interface, will first remove Linea, Moca and Plume from its network list. Guardians will then disconnect the full nodes they operate for those chains, after which outbound messages and token transfers stop.

Portal's early withdrawal can prevent users from initiating a return transfer even while some infrastructure still runs. The announcement does not specify a fixed hour for either step, so it provides a date rather than a guaranteed shutdown schedule.

Portal availability, not the calendar alone, determines when users can act.

Can inbound transfers continue?

The announcement also said: "Inbound transfers may continue temporarily if 13 or more of Wormhole's 19 Guardians keep signing messages." Messages fail when fewer than 13 Guardians sign, reflecting a security model that requires most Guardians to approve each cross-chain message.

The threshold permits six of the 19 Guardians not to sign while a message still passes, provided 13 approve it. That arithmetic does not make continued inbound service automatic, because the announcement does not identify which Guardians will continue signing or how long they will do so.

The direction of each transfer matters. Inbound transfers bring assets onto the affected networks, while outbound transfers move them away. Both routes require Guardian signatures, but only the inbound route has a stated possibility of continuing after the node disconnections.

Users cannot treat continued inbound access as a promise that outbound transfers will remain available.

Why is Wormhole removing connections?

Wormhole said the removals form part of a continuing effort to trim lower-activity connections and shift resources toward higher-volume networks. Every supported chain requires Guardians to operate and maintain full nodes, and the protocol characterized the connection reductions as a security and sustainability measure.

The announcement did not disclose traffic volumes, node operating costs, affected user balances or an incident that triggered the decision. Its security framing therefore describes a network-curation rationale, not evidence of a response to a specific exploit.

Periodic reviews over several years have shaped Wormhole's supported-chain set, allowing the protocol to remove connections it considers less critical or sustainable. The Dec. 2 action fits that established process rather than an isolated infrastructure failure.

The case for the change rests on resource allocation, not a disclosed security event.

What do the affected chains' histories show?

Plume, an EVM-compatible chain focused on real-world applications, joined Wormhole in 2025. Moca joined in early 2026, so its connection will have lasted less than a year by the Dec. 2 cutoff.

Linea's onboarding date was not stated. The announcement also supplied no adoption, transfer-volume or user-balance figures. Moca's shorter history therefore cannot establish whether its route carries more or less activity than Plume's or Linea's.

Connection age varies sharply, so Dec. 2 does not affect three integrations with equal operating histories.

How broad is the chain reduction?

The announcement also listed other networks removed during 2026:

  • Berachain
  • X Layer
  • Mantle
  • Injective
  • Fantom

Wormhole said it reviews supported chains periodically over several years and removes connections it considers less critical or sustainable. The December action extends that process of concentrating Guardian resources on a smaller set of networks.

The removals reflect a continuing portfolio decision, rather than a one-time response to one chain.

Dec. 2 remains the next hard deadline: Wormhole urges users to return bridged assets to their origin networks before the cutoff, although Portal's earlier removal can shorten the usable window. Inbound transfers have no fixed expiration in the announcement; they continue only while at least 13 of 19 Guardians sign. That quorum is the operational variable to monitor before and after Dec. 2.

via tokenpost.com (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