Development Update — Lisk Core 1.0 Beta Testing

Hello Lisk Community,

As stated in our previous development update blog post, keeping you up-to-date about our development progress is very important to us. Today, we have another update regarding the current state of Lisk Core 1.0.0 Betanet testing and the release of Version 1.0.0 Beta 8.

Our developers are working incredibly hard day in and day out. This morning, we had 11 issues remaining on this version, but now, there are only six. Out of these, issue #2080 has, so far, proven to be the most challenging to solve. The Lightcurve development team is currently running a number of tests that are investigating the most efficient way to decrease the number of missed or deleted blocks. The aforementioned issue #2080 needs to be addressed before migrating the Core code to Testnet and Mainnet as the issue would become more visible as the network grows, likely contributing to potential scalability issues. At the forefront of our development goals is a secure, stable and scalable network.

The backport issue relating to release 0.9.15, #2097, has been addressed and successfully merged. Following the network interruption on June 2, we were prompted to fix issue #2098, which was completed earlier today.

We started the day with open issues #1988, #2101, #2102 and #2010, but have since closed them all. #2022 has been open for some time, as tests are currently failing at the integration level. When the issue was tested in a 10 node environment, many blocks were skipped due to a lack of broadhash consensus while tests were running in ‘sync-only mode’ (a mode in which all nodes have broadcast disabled). Following this, the sync process tests were simplified and executed on two nodes — one node that is forging and another node that is being synced based on the forging node. This issue has now been closed.

Based on the feedback from delegates regarding improvements to our technical documentation, Lightcurve developers are contributing to issue #2004, which aims to provide high quality guidelines.

As Jan mentioned in the previous Lisk Core Betanet update, while rigorous testing of the network through Betanet, any issue can arise and have an impact on the timeframes we currently have set. Not only is this the nature of software development, but especially true in the creation of cutting edge and scalable blockchain technology. Having said that, the team is ready for anything and working harder than ever.

The preparations for transitioning to Core 1.0.0 Testnet have already begun. With large scale code quality and migration tests planned, we’re ready to make this transition as seamless as possible.

Core 1.0 is Lisk’s biggest development and release to date. Given its level of importance, we need to pay close attention to every detail. To see our progress in real-time, please follow our Lisk Core GitHub Repository.

We’re on the road to an exciting milestone for Lisk and in that vein, have decided to create a video unpacking all elements of Core 1.0.0 and what it means for the future of our network. Our Motion Designer Julian has already kicked off the preparations and will start shooting next week. However, we will continue to update our dedicated community on the status of Betanet on our social media and community channels.

Thank you again for your continued support!

-The Lisk Team