Lisk Core 1.0 Testnet Release
Hello Lisk Community!
We’re incredibly excited to announce that the migration to Lisk Core version 1.0.0 on our Testnet network was smooth and successful! If you missed the block height of Testnet migration (5,594,490), please upgrade your nodes manually as soon as possible by starting the latest Testnet build from the provided snapshot.
Once again, we kindly ask everyone to familiarize themselves on the migration process with our recently published and comprehensive documentation. The documentation contains the Migration Guide and will constantly be updated and improved over time.
The last remaining changes included in Testnet 1.0.0-rc.1 version are:
Issue #2161: When running the update_config.js script, there was the possibility that it could fail in some edge cases. To avoid this and give users more flexibility, we made the password parameter optional now, so the config.json file can be migrated properly.
Issue #2157: The Testnet 1.0 configuration template (config.json.tmpl) for Docker had not been updated for a little while, therefore we updated it and confirmed that all of the configuration variables are correct.
Issue #2145: We set the block height for when to release Lisk Core 1.0.0 to our public testnet network at 5,594,490. We updated the milestone to reject type 6 and 7 transactions so it will no longer be possible to send them using the 1.0.0 version.
Issue #2134: We updated the README.md file — please check out of newest main page on our Lisk Core repository. We refreshed the Install section as well as the Test Suite section.
Progress on Lisk Core 1.1.0
For Core 1.1.0, we have already solved 16 issues (eight completely closed issues and eight with open pull requests). Progress for this version can be tracked on our GitHub.
Our releases will be predominantly focused on improvements, code refactors and minor bug fixes. The most significant accomplishments are the following:
Issue #398: We now support multiple networks with one installation. To make that possible, we placed all network-specific files into corresponding directories (with a separate one per network). Users will be able to only use a single parameter from the command line to switch between networks (such as testnet/mainnet/etc.). This, in turn, will also simplify the process of how we manage our branches. The version-naming convention will also change to be network-independent.
Issue #2170: Forge should be called after fillPool rather than before. It will fix cases in which some forged blocks are empty (contain no transactions). This can happen, for example, if network is under very heavy load.
Issue #2138: In the past, the /api/delegates endpoint was sorted by rank in descending order — it will now be sorted by ascending order by default.
Issue #216: The issue that has been opened twice by our community has now been solved. It improves both consistency and performance when rounds need to be finished (after every 101st block).
Next Steps
We’re looking forward to the next big step — Core 1.0.0 on Mainnet! We will keep you up-to-date during this important time via the #announcements and #network channels on Lisk.Chat. Please contact maciek (Lisk Core Lead), JuanG (DevOps) or Mat (Community Manager) if you have any inquiries.
We want to extend a special thanks to everyone that migrated and gave feedback. And thank you to the rest of community for the continued support!
-The Lisk Team
Is this one of the first posts that you're seeing about Lisk? See more at Lisk.io or Github.