The Lisk [LSK] blockchain has halted all processes on the blockchain over an automated security measure. Max Kordek, the CEO of Lisk mentioned that all the funds were safe and a fix was implemented.
The measure was triggered due to an individual broadcasting a faulty transaction to the Lisk network. This triggered a rare “edge-case scenario” bug wherein the transaction was deemed valid and went through every node. It was mentioned to be a “maliciously customized” piece of code that utilized a previously undiscovered bug in the system.
The security measurements built into the Lisk Core that were meant to prevent the blockchain from forking triggered in response to the malicious code. This resulted in all of the nodes on the blockchain prevent the processing of new blocks.
This, in turn, resulted in a complete halt of the Lisk network. The 150 transactions in limbo at the moment of the halt of the network were not included in the blockchain. These transactions will not be re-broadcast to the blockchain over security concerns. The funds involved in these transactions will not reflect the changes, as the transactions themselves have been frozen.
Kordek had this to say as the reason to release this to the public:
“In lieu with our commitment to full transparency, we have had similar edge-cases take place 2 or 3 times in the past. In all scenarios, the Lisk blockchain always remained secure, as intended, through the deployment of new Lisk Core versions which fixed such issues and allowed for the Lisk blockchain to continue running as normal.”
He went on to say that the fix for the issue has been discovered and implemented. The release of the new Lisk Core v.0.9.15 will resolve the issues and restore the normal operation of the blockchain. He ended the statement by asking delegates to rebuild their nodes and said that further updates will occur.
Redditor frakilk said:
“I’ve been following the bug resolution on Lisk chat and GitHub. Very quick and level-headed work from the community. It’s a shame this happened but rather now than much further down the line.”
Subscribe to AMBCrypto’s Newsletter