Lisk has recently announced on Twitter that the migration to its current Testnet was a complete success. The company has been testing Lisk Core 1.0.0-rc.2, the newest version of the testnet, and after ensuring the quality of the product, it decided to launch it officially for users all over the world.
🔧 We're excited to announce that the Testnet migration was a success! Learn more about what the @lightcurveHQ development accomplished over the last week with this week's #LiskDevUpdate.https://t.co/XWiKTbOrW8
— Lisk (@LiskHQ) August 9, 2018
The company used Lisk Core 1.0.0-rc.1 and this upgrade makes it closer to the awaited Lisk Core 1.0.0, the release of the Lisk MainNet.
Technical Issues Corrected In Lisk Core 1.0.0-rc.2
Lisk Core 1.0.0-rc.2’s final issue, which was the largest one, was one of the last ones to be solved, which was made by populating blockVersions property in the exceptions in the proper heights range.
The Progress Of The New Version
This new version of the Lisk testnet will support several types of transactions that it did not before. You can send simple messages, register a passphrase to use as a signature, vote to choose and remove particular delegates, register applications, send and withdraw funds from a decentralized application and more.
However, it should be noted that the team has disabled the option to send and withdraw funds for the moment, although it is still on the code, it has to be tested further before it can be used safely.
Some new bugs were also found on this version, including some cases in which critical errors require the whole process to be shut down. There is a lot of work to be done as many features are still missing assertions and some parts of the code are still not completely optimized to function properly.
The Next Steps
At the moment, the team is fixing bugs and implementing the features that still do not work as intended. The QA phase for Lisk Core 1.1.0 is already underway and the product may face significant changes before it is properly fixed and it works as expected by the users.
Regarding the 1.2.0 version of the program, development will be extended and it will still take some time to be complete, as there are several issues still to be fixed. If you want, you can always visit the code of the company on GitHub, as the project is open source.
When the testnet is completely stable and the tests are finished, the team will finally release the MainNet.