Ethereum welcomes a new testnet

Ethereum Developers launched a new test network, Hoodi, on Monday that will be used to carry out the next ‘sicking’ update of Blockchain.

Pin will go to Hoodi on March 26, and if everything goes well, the expected update will proceed to the main network of Etheruem approximately 30 days later, according to the main developers of the network.

Hoodi was created after the defective sicking tests in the other test balls of Ethereum, Holesky and Sepolia, which could not be finalized correctly due to problems with the way they were configured.

Test networks such as Holesky, Sepolia and Hoodi aim to imitate the main Ethereum network, allowing developers the opportunity to test code changes or important updates such as sicking in a low risk environment before implementing them in the Netnet.

Originally, the pein update would have been activated in Ethereum after those two previous tests. Because they were not well, the developers decided to build Hoodi to test the ambitious tong update once again, although the testnet can also be used for future tests.

Hoodi is designed to imitate Ethereum’s principal, with the same number of validators in his network. The Ethereum Core developer, Parithosh Jayanthi, argued during the call of Ethereum Core developers last week that Hoodi would be the Testnet for Ethereum Reading Pools and nodes operators to evaluate their infrastructure.

Holesky and Sepolia were built for different purposes: Holesky has a larger set of validated Ethereum, which is supposed to help try scalability problems, while Sepolia is a closed network only for developers, aimed at trying applications.

Pin contains a series of updates designed to make Ethereum easier to use and efficient for developers and end users. One of the biggest changes includes adding “intelligent contract” capabilities that could give new features to wallets, such as the ability to pay gas rates in different cryptocurrencies of Ether (ETH).

Read more: Ethereum developers launch a new testnet for sicking update after previous setbacks



Leave a Comment

Your email address will not be published. Required fields are marked *