Ethereum Lead Developer Says Rinkeby Testnet Fork Was a Successful Clean Split


Earlier this week BitcoinExhangeGuide had presented the story about Ethereum lead developer Péter Szilágyi announcing the schedule for the Rinkeby Testnet hardfork event. Earlier today, he proclaimed that the event has been successful.

Developers and enthusiasts exploring the Rinkeby testnet will need to upgrade their client to Geth 1.8.20 or newer. Due to the Constantinople upgrade, other versions will be rendered incompatible. As such, avoiding any potential issues is crucial.

Notably, Rinkeby is one of the three Testnet of Ethereum. The other two are Ropsten and Kovan. Rinkeby is a Proof-of-Authority network, so uses a different consensus mechanism to the main net. The Ropsten testnet is Proof-of-Work, so more similar to the public main net. However, unlike Ropten, Rinkeby doesn’t run on miners.

The successful testing of the Testnet was crucial for the upcoming Ethereum hard fork, which has been much anticipated by the crypto community. A consensus bug found in the Parity implementation of Ethereum and the lack of miners had led to the failure of Ropsten Testnet. This resulted in people being that the Ethereum hardfork would be delayed.

Although when asked what’s wrong with the difficulty, Szilágyi gave a passive-aggressive reply. He said:

“Nothing, this is a PoA testnet chain based on the Clique engine. Block difficulties are either 1 or 2 depending on some ordering, so the total diffs are relatively tiny. Ah, the difficulty chart? Some javascript dependency screwed something up and I can’t be bothered to fix it. Would gladly accept a PR, though if the new ethstats server is in the works it may not be worth it to patch the old one.”

People were not too happy with the answer and asked him to fix it. They said that saying “I can’t be bothered” doesn’t look professional. Although there were others who supported the developer by saying if people want change, they should do it themselves.

Constantinople hardfork is scheduled to take place around January 16, 2019, on block #7080000.





Source link