Lisk reaches shutdown deadline while status page still shows mainnet online

Lisk reached its scheduled October 31 chain-closure date with an important unresolved detail: the project’s public status page still listed Mainnet, RPC, Sequencer and Batcher as operational during Coinburn’s late-October 31 Eastern Time publication check.

That does not cancel the shutdown plan. Lisk’s own closure notice says the chain will be shut down on October 31, and its documentation warns that assets left there will become unrecoverable once closure occurs. But the live status reading means the available public evidence did not yet establish that block production and supporting services had actually stopped. The distinction matters for anyone interpreting the deadline as a confirmed technical event rather than a scheduled one.

The deadline and the live signal diverged

Lisk announced the wind-down in August as part of a strategic shift away from operating an Ethereum layer-2 network and toward a business money-operations platform. The company said applications could explore an optional migration to Celo, while the LSK token itself would continue on Ethereum.

The official closure FAQ is categorical about the intended end state. It says users holding LSK, ETH, stablecoins, bridged assets or decentralized-finance positions on Lisk Chain should withdraw by October 31. It also says LSK left on the chain cannot be withdrawn or recovered after shutdown.

Yet Lisk’s status page presented a different kind of evidence at the publication check: all monitored systems were marked operational, including mainnet infrastructure. The page also showed no incident for October 31. A status dashboard can lag an operational change or remain green until planned maintenance is posted, so it is not definitive proof that transactions were still being finalized. Conversely, a calendar deadline alone is not proof that infrastructure has been disabled.

Coinburn could not independently establish the last produced block or a precise shutdown timestamp from the accessible records. Lisk’s public notice specifies the date but not a cutoff hour or timezone. The safest conclusion is therefore that the scheduled deadline had arrived while technical completion remained unconfirmed.

LSK continues, but only Ethereum is meant to persist

The closure applies to Lisk Chain, not to the LSK token everywhere. Lisk’s token FAQ says the canonical Ethereum contract is unchanged and that the move from Lisk Chain is a bridge transfer, not a token swap or redenomination. The project describes Ethereum as LSK’s network going forward.

That separation is also visible in exchange operations. OKX said it stopped Lisk-network deposits before its September 29 notice and ended withdrawals on that network at 6:00 a.m. UTC on October 6, while keeping LSK trading and transfers on other supported networks unaffected. The exchange notice does not prove the chain itself closed; it shows that one major access route was removed weeks before the deadline.

Lisk estimated that its official bridge process took about eight days because users had to prove a withdrawal and then wait through a seven-day challenge period before claiming on Ethereum. Staked LSK required an additional three-day waiting period after unlocking, producing Lisk’s recommendation to allow at least 11 days. Those were project estimates, not guarantees, and they had already made the final date operationally earlier than October 31 for many users.

What remains to verify

The next verifiable milestone is not another announcement but evidence that Lisk Chain’s sequencer, RPC and explorer have stopped advancing, followed by an official confirmation of closure. It will also matter whether already initiated bridge withdrawals can still be proved or claimed on Ethereum after the source chain stops.

Until those records appear, the evidence supports a scheduled shutdown whose deadline has arrived—not a fully verified shutdown.