DeFi•

Wormhole Gives Users Until December 2 to Move Bridged Assets Off Linea, Moca and Plume Before Its Guardians Disconnect

Wormhole will end support for Linea, Moca and Plume on December 2, 2026, and is telling holders of bridged assets to return them to their origin chains first.

Written By :MINRK
Wormhole Gives Users Until December 2 to Move Bridged Assets Off Linea, Moca and Plume Before Its Guardians Disconnect

Photo by John Barkiple on Unsplash

1. Wormhole crypto bridge sets a December 2 cutoff for three networks

The Wormhole crypto bridge will stop supporting three blockchains, Linea, Moca and Plume, on December 2, 2026. The cross-chain protocol announced the change on November 4, 2026, and is urging anyone holding bridged assets on those networks to send them back to their origin chains before its Guardian network disconnects.

The notice period amounts to roughly four weeks. Within that window, holders of tokens that reached Linea, Moca or Plume through Wormhole are expected to reverse the journey, returning the assets to the blockchain where they were first issued. After the deadline, the infrastructure that carries messages out of the three networks will be switched off.

The decision was taken by the Guardian Network, the group of validators that operates the protocol. Its stated aims are stronger security and the long-term sustainability of the system. The removal is the latest in a series of similar steps this year, as the protocol narrows the list of chains it connects.

2. What is Wormhole?

Wormhole is a cross-chain messaging protocol that lets tokens and data move between otherwise separate blockchains. It is best known for token bridging, which allows an asset issued on one network to be used on another.

Blockchains cannot read each other's records directly. A bridge solves that by having a set of independent parties observe an event on one chain, such as a deposit of tokens into a contract, and then attest to it so that a matching action can be taken on a second chain. In Wormhole's case those parties are called Guardians. There are 19 of them, and a message is treated as valid only when a supermajority has signed it.

When a token is bridged in this way, the original is typically locked on its home chain and a representation of it, often described as a wrapped asset, is issued on the destination chain. The wrapped version has value because it can be redeemed for the original. That redemption depends on the bridge continuing to carry messages between the two networks, which is why the withdrawal of support for a chain matters to anyone holding wrapped tokens there.

Portal, found at portalbridge.com, is the interface most individual users rely on to make these transfers. It is a front end for the underlying protocol, not the protocol itself, a distinction that becomes important in the way the shutdown has been structured.

3. How the two-stage shutdown works

Support will be withdrawn in two phases, not in a single step. In the first, Portal removes Linea, Moca and Plume from its interface, so that the three networks no longer appear as options for users making a transfer.

The second phase is the decisive one. The Guardians disconnect the full nodes they run for each of the three networks. A full node is a complete, independently verified copy of a blockchain, and a Guardian needs one for every chain it monitors in order to see what has happened there. Once those nodes are switched off, the Guardians can no longer observe events on Linea, Moca or Plume, and outbound messages and token transfers from the three chains come to a halt.

The ordering creates a practical trap for anyone who delays. The removal of the chains from the front end may come before the node shutdown. A user who waits until the final days could find that the familiar interface has already dropped the network, even though the official deadline has not yet passed. The protocol would still be processing messages at that point, but the simplest route for making a transfer would no longer be available.

4. Why 13 of 19 Guardians matters for inbound transfers

One exception applies to traffic flowing in the opposite direction. Transfers into Linea, Moca and Plume may keep working after the disconnection, but only on the condition that at least 13 of the 19 Guardians continue to sign messages.

The number is not arbitrary. Wormhole's security model relies on a supermajority of Guardians attesting to every message, and 13 of 19 is that supermajority. A message with fewer signatures does not go through. Requiring agreement from such a large share of the set is what makes it difficult for a small group of compromised or faulty operators to forge a transfer.

The asymmetry between the two directions follows from what Guardians must do in each case. To approve a message leaving one of the three chains, a Guardian has to watch that chain, which requires the full node being switched off. To approve a message bound for one of them, the Guardian observes the sending chain instead, which it continues to support.

Nothing about this should be read as a service commitment. The inbound route survives only for as long as enough Guardians are willing and able to keep signing, and no guarantee has been given that they will. For users, the more important point is that inbound is the wrong direction: sending assets toward a chain that is being disconnected increases exposure to the problem instead of reducing it.

5. Why the Guardians are cutting chains

Security and sustainability are the reasons the Guardian Network has put forward, and both are tied to cost. Every chain Wormhole supports obliges each Guardian to run and maintain a full node for it. That means hardware, bandwidth, software upgrades and monitoring for every network on the list, multiplied across all 19 operators.

When a chain carries little traffic through the bridge, that expense becomes hard to justify, and removing it turns into a question of how resources are allocated. Dropping lower-activity networks allows the Guardians to concentrate on the connections that handle the most volume. Each additional integration is also one more piece of software that has to be kept current and one more place where something could go wrong, which is where the security argument comes in.

Linea, Moca and Plume are not the first networks to be trimmed in 2026. Berachain and Injective were deprecated earlier in the year. The pattern is one of periodic review, in which the list of supported chains is examined and those that no longer warrant the upkeep are removed.

The three networks leaving in December differ from one another. Plume, a chain compatible with the Ethereum Virtual Machine and aimed at real-world asset applications, was added to Wormhole only in 2025. Linea and Moca will lose their connections on the same date. A short period of support is not unusual in an industry where new blockchains launch frequently and bridge operators must decide early, with limited information, which of them will attract lasting activity.

6. What should users on Linea, Moca and Plume do?

Anyone holding Wormhole-bridged tokens on Linea, Moca or Plume should bridge them back to their origin chains through Portal before December 2, 2026. That is the action the protocol itself is recommending, and it is the only step that removes the risk entirely.

The reason for urgency is what happens afterwards. Once the Guardians disconnect, outbound transfers stop, and there is no guaranteed route out for wrapped assets that remain on the three chains. A wrapped token whose path back to the original has been closed may still exist in a wallet, but the mechanism that gave it value, the ability to redeem it for the underlying asset, would no longer be functioning through Wormhole.

Acting early is the safer course for the reason set out above: the interface may drop the networks ahead of the formal deadline. Leaving the transfer until the last moment risks discovering that the front end has already changed.

The notice applies to assets that crossed through Wormhole. Tokens issued natively on Linea, Moca or Plume, or brought there through a different bridge, do not depend on Wormhole's Guardians and are not affected by the withdrawal in the same way. Holders who are unsure how a particular token reached the chain should establish that before the deadline, since the distinction determines whether they need to act.

7. What happens after December 2

December 2, 2026, is the date on which support formally ends, and the sequence leading to it has already been laid out: removal from the Portal interface, followed by the disconnection of Guardian nodes. From that point, messages originating on the three chains will no longer be carried by the protocol.

For the affected networks, the change removes one of the routes by which assets can enter and leave. It does not stop the chains themselves from operating. Linea, Moca and Plume are independent blockchains that continue to run regardless of which bridges connect to them. The loss is one of connectivity through a single provider.

The wider implication concerns how users think about bridged assets in general. A wrapped token is only as durable as the bridge behind it, and bridges revise their lists of supported networks. The removals of Berachain and Injective earlier in 2026, followed now by three more, show that inclusion on such a list is not permanent. Holders of wrapped assets on smaller or newer chains have reason to keep track of deprecation notices, because the window to act, about four weeks in this case, is finite.

Whether further networks follow will depend on the same test the Guardians have applied here: whether the traffic a chain generates justifies the cost and risk of maintaining a connection to it.

Related Articles

NEWSLETTERS

Don't miss another story.

Subscribe to the MINRK Newsletter today.

Tick the newsletters you want. No selection? You'll get MINRK Headlines.

By signing up, you will receive emails about MINRK products and you agree to our terms of use and privacy policy.

MINRK Daybook

Market analysis for crypto traders and investors.

EVERY WEEKDAY

MINRK for Advisors

Defining crypto, digital assets and the future of finance for financial advisors.

EVERY THURSDAY

MINRK Protocol

Exploring the tech behind crypto one block at a time.

WEEKLY

MINRK Long & Short

A must read for institutions. Insights, news and analysis delivered weekly.

EVERY WEDNESDAY

MINRK Headlines

The biggest crypto news and ideas of the day.

EVERY WEEKDAY

MINRK Policy

Examining the intersection of cryptocurrency and government.

WEEKLY

MINRK Research

Join thousands of readers who rely on MINRK for data-driven insights on the latest digital asset trends.

MONTHLY