Development Update — Lisk Core 1.0 Beta Testing
Hello Lisk Community,
Since last week’s development update, we have continued to make strong progress with beta testing Lisk Core 1.0.0. The Lisk Core team completed all remaining issues on beta.8 earlier this week and released the latest update on Tuesday. A short release summary can be viewed below:
Issue #2080: This issue was solved through extensive testing to ensure the correct propagation of blocks and peers data over the network, guaranteeing proper consensus and resulting in a decreased number of missed and deleted blocks.
Issue #2046: We added config.json migration script from version 0.9.x to ensure the update will be a simple process for those who are running nodes.
Issue #1956 and #1988 were in relation to changes to the API. Issue #1956 was solved to make the use of the node/status/forging endpoint easier, while issue #1988 removed the rank parameter in delegates endpoint.
Issue #2010 was fixed to make blacklisting IPs of peers connecting to our node via the P2P layer possible.
Since Lisk’s inception, a large part of our community has been involved in the development of the project. This has been particularly evident throughout the beta testing of Lisk Core 1.0.0. The #network channel on Lisk.Chat has been the meeting point for technical discussions; we also receive high quality feedback in this channel. Following the release of Beta.8, community member Simon Warta (Prolina) identified two issues:
Issue #2126: The rewards for blocks and transactions in the first round (first 101 blocks) had been applied twice to account balances when creating snapshots. On Betanet, it resulted with inconsistent data for a few genesis delegates. Testnet and Mainnet are unaffected. We have published new valid snapshots for Betanet which can be viewed here.
Issue #2123: With the approval from the community, we removed the extra 0.1 LSK transaction fee for an extra data field — the new functionality introduced by 1.0.0 version. There are five transactions with extra data fields already sent on Betanet — 1.0.0-beta.9 adds them to the exceptions list.
Prior to releasing beta.9, we refactored the entire snapshotting logic to close a number of issues related to snapshot creation together with corresponding tests. As a result, issues #1949, #1927, #1869, #1868 and #1933 #1963 have been resolved, enabling valid snapshots to be taken on betanet.
Next Steps
Once Lisk Core 1.0.0 beta.9 is released at 10:00 CET on Friday, we will kickstart our final round of QA where the team will focus on the following:
0.9.16 -> 1.0.0 Mainnet and Testnet data migration, synchronization and snapshot creation.
0.9.16 -> 1.0.0 Network migration which will take into account many variants: updating the version manually, using dedicated script for automatic migration, delays in migration etc.
Large public betanet testing with 500 nodes to test scalability of the network. During this large-scale test, multiple transactions will be broadcasted to confirm that the network behaves as expected when put under stress. The commencement of this process will be announced on Lisk.Chat.
Test every feature that 1.0.0 introduces.
We expect the QA process to be finalized by the end of next week. Upon completion, we will announce the expected date of arrival for Testnet.
We will communicate all of these updates and any potential changes via the Announcements and Network channel on Lisk.Chat. Please contact Maciej (Lisk Core Lead), Juan (DevOps) or Mat (Community Manager) if you have any inquiries.
Thank you again for your great feedback and support!
-The Lisk Team
Is this one of the first posts that you're seeing about Lisk? See more at Lisk.io or Github.
Soo Good