Announcing Lisk Mainnet v3 Migration

Announcing Lisk Mainnet v3 Migration

After the successful Lisk Testnet v3 migration, we are pleased to announce the Lisk Mainnet v3 migration will occur on the block height 16,270,292 which will be reached approximately on 21st of August, 10am CEST. All product dependencies, namely Lisk Core 3.0.0, Lisk Service 0.4.0, Lisk Desktop 2.0.0, and Lisk Migrator 1.0.0, are now ready for production.

 

The Lisk Mainnet v3 will offer a wide range of new protocol features and improved performance. It is of key importance that you read the Actions Required for the Upcoming Mainnet Migration blog post to be fully informed.

 

With the Lisk Mainnet migration within reach, the Next Steps for Lisk Development involve the implementation of our interoperability solution.

 

All Information about the Lisk Mainnet Migration

As previously stated, the Lisk Mainnet migration will occur on the block height 16,270,292 which will be reached approximately on 21st of August 2021, 10am CEST. The exact time is dependent on the current Mainnet conditions and how reliably new blocks are being created. With the migration, all protocol improvements introduced with the Lisk SDK 3.0.0, 4.0.0, and 5.1.0 will be functional on the Lisk Mainnet.

 

Please be advised that the pre-migration delegate selection will persist until the block height 16,332,092 which will be reached approximately one week after the Lisk Mainnet v3 migration on 28th of August 2021, 2pm CEST. Your new votes will only be applied once the new Lisk Mainnet has been running for a period of one week. This delayed transition ensures that the network is still performing correctly as we implemented a change in our delegate selection mechanism.

 

Important Call for Network Stakeholders

Current Lisk Mainnet Delegates

As stated above, it’s important to note that the pre-migration delegate selection will persist for about one week. Therefore, if you are a current Mainnet delegate you should definitely upgrade your full node to Lisk Core 3.0.0 in order to be able to continue forging new blocks after the Lisk Mainnet v3 migration. For that purpose, we have written an easy-to-understand Lisk Core 3.0.0 migration guide in our Lisk documentation.

 

Exchange and Wallet Providers

The Lisk Mainnet v3 migration will not be immediate due to the fact that once we reach the above-mentioned block height, the full node will be waiting for an additional 201 blocks due to security reasons (blockchain reorganizations). After that period of waiting has expired, a snapshot of the Lisk Mainnet v2 blockchain will be taken, and with all its information a new genesis block for the Lisk Mainnet v3 blockchain will be created. We estimate that the whole process will take about two hours to complete. Transactions happening after the above-mentioned height in the Lisk Core v2 blockchain will be ignored for the genesis block computation, i.e., they will not be migrated.

 

Therefore, it is extremely important to stop all deposits and withdrawals during the day of the Lisk Mainnet v3 migration to ensure no funds will be lost.

 

Additionally, it is necessary to implement the new API of Lisk Core 3.0.0 and our Lisk Service infrastructure. All required information is available in our Actions Required for the Upcoming Mainnet Migration blog post.

 

Users and Investors

The upcoming Lisk Mainnet v3 migration is only possible due to a multitude of new software releases. It’s the largest update to the Lisk Mainnet in its history, and likely one of the biggest updates to a running production blockchain ever.

 

At this juncture, it’s important to mention that there won’t be any immediate support available for the Lisk Mobile and hardware wallets. If you require immediate access to your Lisk account please download Lisk Desktop if you have only been using Lisk Mobile. In the case where you have a hardware wallet setup, please ensure you transfer your LSK tokens to a regular Lisk account and initialize it. Additionally, we will Replace the Lisk Explorer with new explorer functionalities inside Lisk Desktop and two community developed explorers, namely Lisk.Observer and LiskScan.com. To access all information from the former Lisk Mainnet we will deploy a legacy version of the Lisk Explorer for a minimum period of 12 months. Be advised, this link will only become available after the Lisk Mainnet v3 migration.

 

Additionally, we would like to reiterate that it is extremely important not to transfer any LSK tokens during the day when the Lisk Mainnet v3 migration is occurring, to ensure no funds will be lost.

 

Conclusion

To summarize, the Lisk Mainnet v3 migration will consist of the largest update ever performed on the Lisk network and will offer numerous improvements.

 

These are covered in more detail in the Actions Required for the Upcoming Mainnet Migration blog post. For all stakeholders in the Lisk network, it’s a must to read and digest this blog post to ensure everything is functioning correctly after the Lisk Mainnet v3 migration has occurred.

Lisk

Blockchain application platform