Hello Lisk Community!
Over the past week, the Lightcurve Development team has mainly been working on QA (quality assurance) for Lisk Core 1.0.0-rc.2. This is the most crucial process prior to the release to Mainnet, therefore we are making sure to take our time to ensure with utmost precision the stability of the product. We are also still communicating with many exchanges that will need to properly migrate to Lisk Core 1.0.0.
Lisk Core 1.0.0-rc.2:
We have continued testing the second release candidate for Lisk Core 1.0.0, performing several intensive rounds of QA. In the process, we have been able to identify several issues that required fixing before the actual release.
Issue #2199 — The logic of the isValid function that is responsible for validating the blocks’ version property was not correct. The function was returning an invalid result when the blockVersions object in the exceptions file contained only one entry. We had to rewrite the entire logic of that function. We also added more test cases that have proven that the above mentioned function works as expected now.
Issue #2249 — As mentioned in last week’s Development Update, this issue is very important for the security of the network and to ensure a smooth migration process. During the migration tests, we noticed some incorrect behavior — after the node restart at the migration height, the last block of the blockchain was detected as invalid, therefore deleted from the database. After extensive debugging, we identified that the cause of the misbehavior was the additional sorting of transactions performed during the loading of the last block from the database. Because the order of the transactions was different than the one from the time at which the block was created and signed, the block verification function generated a ...
This content is synced from the rightful owners. Copyright on text and images belong to the original source.
This article was first published on: Lisk Blog - Medium