Wormhole will stop supporting three more networks next month, telling users to bridge assets off Linea, Moca and Plume before the protocol’s validator set disconnects.
Support ends on December 2, 2026, closing a four-week window that opened when the decision was announced on November 4. The call came from the Guardian Network, the group of validators that operates Wormhole, which said the cuts are meant to strengthen security and keep the platform sustainable.
The shutdown runs in two phases. First, Portal, the bridge interface at portalbridge.com, will drop the three chains from its front end. Then the Guardians will disconnect the full nodes they run for those networks, at which point outbound messages and token transfers from Linea, Moca and Plume stop.
There is one partial safety valve. Inbound transfers to the affected chains may remain available, but only if at least 13 of the 19 Guardians keep signing messages during the transition. That threshold is structural rather than incidental: Wormhole’s security model depends on a supermajority of Guardians attesting to each message, and a message that falls below 13 signatures does not clear.
The pruning is part of a pattern. Wormhole has already deprecated several networks in 2026, including Berachain, X Layer, Mantle, Injective and Fantom, generally shedding lower-activity connections to concentrate on higher-volume routes. Every chain the protocol supports requires Guardians to run and maintain full nodes, so a route that does not carry enough traffic to justify the cost becomes a candidate for removal. Timing has been short for two of the three: Plume was added in 2025, while Moca was integrated in early 2026 and will not have lasted a year.
For holders, the action is time-sensitive and simple in principle. Assets bridged through Wormhole on any of the three chains should go back to their origin network through Portal before December 2. After the Guardians disconnect, outbound transfers stop and there is no guarantee of a clean exit for wrapped assets left behind.
Because front-end removal precedes the node shutdown, waiting until the final days carries its own risk: users may find the familiar interface gone while the underlying deadline has not yet technically passed.