THELOGICALINDIAN - During the aboriginal hours of Saturday morning affairs fabricated on the Lisk blockchain came to a abounding stop as a adulterated transaction triggered automatic aegis systems on the network
Lisk Blockchain Shutdown
The President and CEO of Lisk, Max Kordek, bound wrote a Reddit post that explained the bearings to the Lisk community.
Max noted:
During European morning hours, an bearding alone broadcasted a adulterated transaction to the Lisk network. Due to a attenuate edge-case bug in transaction processing, this transaction was accounted accurate and went through the processing accomplish on anniversary alone node. However, it was an invalid, maliciously customized transaction blazon that utilised this accurate cipher bug.
To action the problem, the Lisk blockchain immediately stopped processing new blocks, causing all affairs fabricated on the arrangement to freeze. As the arrangement froze, hundreds of affairs began to accession on the network, with none of these affairs extensive their final destination.
At the accepted time, it is cryptic whether the alone was acting with awful intent. Kordek says that the bug was begin and accomplished upon, whether it was as an agreement or advance is still unknown.
Is Centralization a Risk For Lisk?
At aboriginal glance, the affected acting abeyance in the Lisk blockchain may be beheld as article an alone centralized blockchain could do.
However, Max acicular out that the account of the arrangement abeyance was due to an automatic failsafe arrangement which helps assure the Lisk blockchain. Many users of the belvedere were quick to accurate their account for this avant-garde and defended system. One Reddit user said, “Almost like Lisk has its own congenital antivirus. That’s awesome, haven’t heard of this in any added project.”
Lisk uses a ‘Delegated Proof Of Stake’ arrangement to advice verify the network. This acts analogously to a approved POS arrangement but uses a set bulk of agent nodes to advice verify the network
However, abounding critics accept that a DPOS arrangement introduces absorption to the decentralized attributes of cryptocurrencies. In abounding cases like with Lisk and ARK, DPOS systems accept been accurate to be adequately successful at accepting blockchains account hundreds of millions of dollars.
At about 5:00 PM GMT, the Lisk aggregation appear a fix, which absolutely antipodal the problems acquired by this adulterated and ‘malicious’ transaction.
Community administrator Jan wrote:
We accept aloof now appear the fix and band-aid to this amount and are now abiding to a accustomed and consistently operated network. Within the abutting moments, aggregate will be optimally activity and will acquiesce for all users to use the Lisk blockchain and their tokens as they did above-mentioned to this. To admonish you all, everyone’s armamentarium is safe.
Max did point out that already the arrangement does alpha active again, it will act as if the affairs broadcasted afterwards the abeyance did not exist.
This aspect of the fix was capital in authoritative abiding that all funds on the arrangement backward defended as if the bug never occurred.
From a macro view, it is abundant to see that Lisk had systems in abode to stop bugs such as this one, but seeing as Lisk had problems with “edge-case bugs, 2 or 3 times in the past,” it makes faculty why this is article anchored into Lisk’s code.
LSK amount was not affected, in actuality it was trading up 7% on the day to $9.30 at the time of writing.
