|
|
"The upgrade to Cancun, launched on August 16th, appears to be running smoothly, according to Barnabas Busa, a DevOps engineer at the Ethereum Foundation, with a developer-centric testnet. Busa mentioned that nodes running the Nethermind (EL) client software seem to have some issues. Lukasz Rozmej, a developer of the Nethermind client, explained that the root of the problem was due to a configuration error in the Blob transaction pool implementation. (Translator's note: Devnet 8 is the first dedicated testnet containing all finalized EIPs for the Cancun/Deneb upgrade.)
Regarding EIP 4788, developers briefly reaffirmed the new deployment strategy for code changes. Contracts that publicly beacon chain data on EL will be deployed like regular smart contracts, requiring someone to provide funds for the contract address before the upgrade is activated. The next testnet for the Cancun upgrade, Devnet #9, will follow this workflow and ensure developers are familiar with the process.
Developers did not postpone the release date of Devnet #9 but agreed to continue testing on Devnet #8 until all client implementation issues are resolved. ""I'd rather have confidence in Devnet #9 than say we hope these things work. ... I'd rather address the problems we know. Otherwise, if we encounter difficult issues in Devnet #9, we'll certainly have Devnet #10, and I'm not saying we shouldn't have Devnet #10. We should have a meaningful number of development networks. I think now we can try to make Devnet #9 really reliable,"" said Danny Ryan, Ethereum Foundation researcher and ACDC conference call chair.
Others in the conference call, including Tim Beiko, Marius Van Der Wijden, and Justin Florentine, supported spending more time testing on Devnet #8 and testing the changes in EIP 4788 on Devnet #9 later. Beiko suggested reconvening for Devnet #9 during the next ACDC conference call. Regarding the deployment strategy for testnets, Beiko proposed the following sequence:
Devnet #9: Another Devnet with the Cancun specification frozen. Stress test the network and assume developer satisfaction before moving to the public testnet. Otherwise, initiate Devnet #10.
Holesky: Fork the newly launched Holesky testnet and deploy the Cancun upgrade on it.
Goerli: Deploy Cancun on Goerli. As the penultimate testnet before the mainnet upgrade, the upgrade specification should be final by this time, allowing users and applications ample time to test their software before the mainnet upgrade. Dencun is likely to be the last fork on Goerli before it gets deprecated and replaced by Holesky.
Sepolia: Finally, deploy Cancun on Sepolia for a good effect.
There was no objection to Beiko's proposal to release testnets after Devnet #9. Beiko mentioned that once the Holesky testnet officially launches on September 15th, this schedule will be shared with the wider Ethereum community in a blog post. Additionally, Beiko stated that another testnet called Ephemery is in development. Ephemery is an Ethereum testnet aimed at validator node operators and will reset back to genesis state every one or two weeks. More information about the Ephemery network can be found on its GitHub page.
Before continuing the discussion on Verkle Tries, Busa emphasized the open pull requests (PRs) on GitHub regarding the Holesky testnet. At the request of the Erigon (EL) team, the PRs suggested removing the specific activation time for the Cancun upgrade on Holesky. Developers will later set a value for the activation of Cancun on Holesky rather than overwriting the existing value. Busa also raised the issue of testing 3/6 blob targets/maximum values (instead of 2/4 limits). On this topic, Beiko suggested bringing up the question again at the next ACDC conference call next week, and Ryan mentioned that recent experiments with larger block sizes would provide new insights." |
|
Post time 7-9-2023 11:05:55
