Acala and Karura shutdown proposals: What token holders need to know

Originally reported by Deep Tide TechFlow on November 11, 2026, at 14:05 (UTC+8). The votes and deadlines below reflect that report, not a current status update.

The teams behind Polkadot parachain Acala and its sister chain Karura have put proposed shutdowns to community votes: Acala Referendum #195 and Karura Referendum #137. Neither vote, as reported, was itself an executed shutdown. If the proposals pass and subsequent on-chain execution proposals are carried out, both networks are scheduled to stop producing blocks on February 10, 2027.

For token holders, the key distinction is whether an asset can leave the networks:

  • DOT, KSM, and bridged USDT and USDC: The proposal calls for holders to withdraw these external assets to other networks before February 10, 2027.
  • ACA and KAR: The report says these native tokens cannot be exported cross-chain and would remain on their respective networks’ ledgers after a shutdown. Holding a token does not, by itself, provide a way to move it to another network.
  • Liquid-staking positions: Unbonding takes time, so the proposed application deadlines are earlier. LDOT bound to certain validators has a December 16, 2026 deadline because its unbonding period includes an additional 28 days on top of Polkadot’s usual 28 days. The deadlines for ordinary LDOT and LKSM are January 12 and February 2, 2027, respectively.
Acala and Karura shutdown proposals: What token holders need to know

In a letter to the community, the team attributed the proposal to fragmented funds and insufficient DeFi liquidity across parachains, alongside node and network maintenance costs that it said had continued to exceed returns. It also cited security concerns about leaving assets on networks without ongoing maintenance.

At the time of the report, Subsquare data showed approximately 23.1 million ACA votes in favor of the Acala referendum and 1.28 million KAR in favor of the Karura referendum, with no opposing votes recorded for either. The team said it would submit separate on-chain execution proposals after the signaling votes. It committed to keeping nodes and coretime available before any shutdown, and said it would try—but could not guarantee—to return external assets left unwithdrawn to corresponding Asset Hub addresses.

Source: techflowpost.com (originally published 2026-11-11 14:05 UTC+8)