Ethereum: Cancun-Deneb hard fork deployed on Goerli testnet

Ethereum: Cancun-Deneb hard fork deployed on Goerli testnet

L2 are jubilant. Sew Ethereum is about to experience a major deployment update Cancun-Deneb hard fork. After a few devnets, the update is now coming to the Goerli testnet.

Cancun-Deneb deployed on Goerli testnet

Directly after deployment hard fork ShanghaiEthereum developers have started working on the following update: Cancun-Deneb.

After a couple of nines without major hiccups, the hard fork will now continue its journey towards the mainnet. That’s how it will be deployed on various Ethereum testnets.

So on January 17th around 7:35 French time the Cancun-Deneb hard fork was deployed on the Goerli testnet. The announcement was made by the developers during a live stream that took place after the deployment.

However, the deployment was not without problems.According to information reported ParithoshDevOps at the Ethereum Foundation.

the nodes have there are synchronization problems at the time of branching. Fortunately, the validators synced successfully after patch deployment. Finally, the pipeline could be completed, marking the end of the update deployment. The whole process will take a total 4 hours before showing channel completed.

Once Cancun-Deneb is verified to work optimally on Goerli, the fork will deployed to Sepolia on January 31. It will finally be deployed on the testnet Holesky February 7. Cancun-Deneb could thus be on the mainnet in the weeks following Holesky.

L2 no longer holds in place

The Cancun-Deneb update will be introduced EIP 4844also called Proto-danksharding. Without going into too much detail, this EIP introduces a new type of transaction, the so-called transaction carrying the blob.

These transactions will specialize large data storage. These will be especially useful for different layers 2 which revolve around Ethereum and store data regarding transactions that have taken place on L2.

In practice, this update should increase the performance of Layer 2 by a factor of 10. Additionally, it should reduce the cost of publishing from L2 to L1, and consequently, reduction of transaction fees on L2.

The storage of transactional data is a central part of summaries. Indeed, this data is necessary for an external verifier to check the summary status from L1.

Other solutions choose to store data on dedicated blockchains called data availability layers or DAs. These solutions are called validium and have recently become the subject of debate following Vitalik Buterin’s statement.

Leave a Comment

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