> For the complete documentation index, see [llms.txt](https://support.lisk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.lisk.com/faq/lisk-chain-closure.md).

# Lisk Chain Closure

Everything you need to know regarding the Lisk Chain Closure.

{% hint style="warning" %}
**Action required:** Withdraw all assets from Lisk Chain by 31 October 2026. The Lisk Chain is shutting down. If you hold LSK, ETH, stablecoins, bridged assets, DeFi positions, or any other assets on Lisk Chain, please withdraw them as soon as possible and no later than 31 October 2026.
{% endhint %}

#### What is being announced?

Lisk is winding down the Lisk Chain on October 31st, 2026, following the announcement of our new product. For projects considering what comes next, we've put together a [guide](/guides/lisk-chain/celo-migration.md) to exploring a move to Celo. Projects remain free to redeploy wherever they choose. This FAQ covers what's changing, the timeline, and the options available to projects, partners, and users.

#### Why is this happening?

This wasn't a decision we made lightly. A lot of teams have put real time and energy into building on the Lisk Chain, and we don't take that for granted. With the announcement of our new product, we've made the strategic decision to commit fully to that direction. Winding down the Lisk Chain is a difficult but deliberate part of that, and we're committed to supporting projects through the transition with clear communication and a path to explore what comes next.

#### What does this mean for projects building on Lisk?

Projects currently building or deployed on Lisk can review their options and decide what path makes the most sense for their product, users, and team. If you're interested in exploring a path to Celo, you can complete this form to share your project, current deployment, and technical considerations with the Celo team.

#### When is the Lisk Chain shutting down?

The Lisk Chain will be shut down on October 31st, 2026. We'd encourage any project still building or deployed on the chain to review its options and, if relevant, begin exploring a path forward well ahead of that date.

#### Do I need to move my LSK before shutdown?

Only if you hold it on the Lisk Chain or have it staked. LSK on Ethereum or an exchange is unaffected and needs no action.

#### What happens to my LSK on the Lisk Chain after it shuts down?

It becomes inaccessible. Once the Lisk Chain shuts down on 31 October 2026, there is no way to withdraw or recover LSK left on it. If you hold LSK on the Lisk Chain, or have it staked, you must move it to Ethereum before that date. The withdrawal takes at least 7 days, and unstaking adds a 3-day waiting period first, so start now rather than waiting until the final weeks. For stakers, penalty-free unstaking is now live, so there is no reason to wait.

#### How do I move LSK off the Lisk Chain?

You bridge it back to Ethereum using the Lisk Bridge at [https://bridge.lisk.com](https://bridge.lisk.com/). It is the only bridge that still works, so do not rely on any other route.\
\
The most important thing to get right is that you are bridging LSK to LSK, not swapping LSK for ETH. The bridge opens with Ethereum and ETH preselected, so you need to change both rows before you enter an amount.

1. Open [https://bridge.lisk.com](https://bridge.lisk.com/) and connect your wallet.
2. Click the top row (the "from" side). Select the Lisk network, then select LSK as the token.
3. Click the bottom row (the "to" side). Select the Ethereum network, then select LSK as the token.
4. Check that the screen now reads Lisk LSK on top and Ethereum LSK below. Enter the amount and confirm the withdrawal.
5. About an hour later, return to the bridge and submit the "prove" transaction on Ethereum. The 7-day countdown starts at this step, not the first one, so do not skip it.
6. After the 7-day challenge period, submit the final transaction to claim your LSK on Ethereum.

You will need a small amount of ETH on Ethereum to pay for the prove and claim transactions. The whole process takes around 8 days, so we recommend starting immediately.

#### How do I move WETH off the Lisk Chain?

WETH itself can’t be bridged back to Ethereum through the native Lisk bridge. The way to move it is to first unwrap the WETH into native ETH on Lisk, and then bridge the ETH back to Ethereum as usual.

1. Open the WETH contract on Blockscout: <https://blockscout.lisk.com/address/0x4200000000000000000000000000000000000006>
2. Connect the wallet holding the WETH.
3. Go to Write Contract → withdraw.
4. Enter the amount to unwrap in wei — e.g. 1 ETH = 1000000000000000000 wei.
5. Confirm the transaction. The corresponding native ETH should then appear in the same wallet.
6. The ETH can then be bridged back to Ethereum through <https://bridge.lisk.com/>.

#### Are projects required to migrate to Celo?

No. Migration is optional. Each project should decide independently whether Celo is the right fit for its product, users, and roadmap.

#### Is every project eligible to apply for migration to Celo?

Yes. Migration is open to every Lisk ecosystem project. Any team interested in exploring a migration or redeployment can submit the interest form.

#### How can projects express interest?

Projects interested in exploring a migration or redeployment path to Celo should complete the migration interest form. The form will help Celo understand the project, current deployment, technical setup, user or liquidity considerations, and potential next steps.

#### What happens after a project submits the form?

The Celo team will get in touch to share relevant resources and work through timing, redeployment, technical requirements, and what makes sense for the project’s users.

#### What information should projects prepare?

Projects should be ready to share basic information such as:

* Project name and description
* Website and social links
* Main contact
* Current deployment status on Lisk
* Smart contract addresses, if relevant
* User, liquidity, or asset considerations
* Key technical dependencies
* Any specific questions or migration needs

#### Will Celo provide technical migration support?

The Celo team is committed to supporting projects that choose to migrate and has prepared resources to help teams get set up in the Celo ecosystem. The specific support provided will depend on each project’s technical requirements and migration approach.

#### Will there be funding or incentives for projects that migrate?

No funding or incentives should be assumed. Any potential support will be reviewed on a project-by-project basis and must be confirmed directly by the relevant team.

#### Who can projects contact with questions?

Projects should use the [migration interest form](https://docs.google.com/forms/d/e/1FAIpQLSe_hWNMi7A_6l6k8VQEprVvQ0cMc0UzvGQF6G0FWgx24Vh_Mw/viewform) as the first step.

The Celo team will then follow up with relevant resources, questions, and next steps.

<br>
