Lisk v0.3.3 — Release Announcement

  • The latest Lisk client v0.3.3 has been released, and is now available for download via our downloads server. This version is a mandatory update, and is being released due to a critical bug encountered at block 808831. In order for all nodes to remain operative past this block, all node operators are required to update immediately.

    Block 808831 contained one transaction 8742556801784407667, a special type of transaction used to initiate a LSK transfer between a sidechain and the mainchain. Due to a bug found in the OutTransfer module that handles this type of transaction, the nodes on the network were unable to save the block to the underlying database, and subsequently closed down with an error. The bug was caused by an incorrect assumption in the client code, the assumption being that the sidechain initiating the withdrawal is actively running on the same node, and able to receive message broadcasts that reflect the withdrawal on the sidechain. The new version fixes the bug causing this error, and allows for block 808831, and any future blocks containing this type of transaction to be processed successfully.

    As part of the current work-in-progress “Mainchain Stablisation” milestone, recently outlined in the Lisk Development Roadmap, we are making huge efforts to overhaul the existing test-suite that is central to our development process. This should ensure errors similar to which we encountered at block 808831 will become increasingly rare, and eventually non-existent.

    To install or update to Lisk v0.3.3 please read our official documentation.

    v0.3.3 Changelog

    • Backported inTransfer / outTransfer module fixes. Resolves critical issue when saving outTransfer (type 7) transactions, used to initiate LSK transfers between a sidechain and the mainchain. The supporting test-suite has been improved to ensure this basic functionality is maintained between releases.

    Please join our forum or chat if you have any further questions, or are interested in supporting the network by running a node.

    For reference, you can always track our development progress via GitHub:

    Kind regards,

Log in to reply

Looks like your connection to Cryptocentral was lost, please wait while we try to reconnect.