Celo Migration

Exploring a Path to Celo

This guide explains how projects currently building or deployed on Lisk can explore a potential migration or redeployment path to Celo following our recent announcement.

Migration is open to every project and remains entirely optional. Each team should decide what makes the most sense based on its product, users, technical setup, and future plans.

The Celo team is committed to supporting projects that choose to make the move and has prepared resources to help teams get established in the Celo ecosystem.

If you think Celo is the right path for your team, here’s how to get started:

1. Review your current deployment

Prepare a short overview of your project, including:

• Project name and description

• Website and socials

• Main contact

• Current deployment status on Lisk

• Smart contract addresses

• Active users, liquidity, or assets, if relevant

• Key infrastructure dependencies, such as RPCs, indexers, bridges, or oracles

2. Share your interest

If your team is interested in exploring a migration or redeployment to Celo, fill out this short interest form.

3. Connect with Celo

After receiving your submission, the Celo team will get in touch to share relevant resources and discuss what a potential move could look like for your project.

Considerations may cover:

• Product fit

• Technical requirements

• User or liquidity considerations

• Ecosystem relevance

• Potential next steps

4. Define the migration approach

Together with the Celo team, you can determine the most appropriate migration or redeployment approach based on your product, technical requirements, and users.

There is no single migration path for every project. The goal is to help each team understand its options and work through an approach that makes sense for its specific setup.

Important Notes

• Migration is optional.

• Celo will review projects individually.

• No funding, technical support, or ecosystem support should be assumed unless confirmed.

• Projects with users, liquidity, or assets should prepare a more detailed migration plan.

• Public communication should only happen once the migration path is clear and aligned.