The Kintsugi network, where the error occurred, was launched less than a month ago.
Preparations are underway for the launch of Ethereum 2.0 on this testnet.
One bug caused the Ethereum 2.0 testnet Kintsugi to fork into at least 3 different networks. This causes this network to take 3 days without being able to properly validate the blocks.
The downside was due to the error checking test within the network, which the tool is known as Fluzzer. This is intended to create invalid blocks by changing certain properties, In order to verify that validators can identify the failure and invalidate the block. This, as detailed by Ethereum developer Marius van der Wijden, in a welcome from Twitter.
However, it seems that some of these auditors, which ran clients such as Nethermind and Besu, identified the invalid blocks as valid, creating a new chain, which Geth validators rejected.
But the network section was much worse, because the validators are on Teku, another Kintsugi customer, has also been flagged as valid bad blocks, and create a new fork.
The programmer commented on August 7 through Twitter, that the creation of invalid blocks lasted for two days, and that the chain is still in place for the time being. has errorsWhich made the developers work to find it.
At the time of writing, developer van der Wijden has not provided updates on whether the network is no longer forked. On January 8th share a profile welcome From Twitter about the status of the issue, where they commented that they fixed what happened.
Regarding Kintsugi, it is worth noting that this testnet was launched last December, according to mentioned Crypto News. In this network, the first instances of what would be Ethereum 2.0 are being tested, with Proof of Stake (PoS).
Forked Ethereum 2.0 mainnet, is it possible?
The error in question that gave rise to this large fork was intentional, however, The results were not as expected. Although it was deliberately produced, such a scenario could happen on the Ethereum 2.0 mainnet.
as Picks CryptosLate Portal In an interview with Marius van der Wijden, the programmer commented that such an error would be “very annoying” on the main network. Although they are detectable errors, the resulting branching levels can end in complete network failure.
However, for the programmer, these types of scenarios that happened in the testnet are a good sign because they show developer response times for errors. In addition, it highlights that such situations do not affect or delay the arrival of Ethereum 2.0.
“Beeraholic. Friend of animals everywhere. Evil web scholar. Zombie maven.”