Updated March 12, 2024: Since the initial publication of this post, several client teams have made Dencun compatible releases with significant performance and stability improvements. Previously announced versions are still considered sufficient for upgrades, but columns have been added Client Release A table highlighting the latest recommended versions for all clients.
- The mainnet blob is here: Two years after Esten's launch, dozens of test calls and developers later, then Protodanksharding will finally be live on the mainnet!
- Dencun will be active on Ethereum Mainnet on Epoch 269568It will occur at 13:55 UTC on March 13, 2024. Node operators and stakers must upgrade their software to the releases listed in this announcement.
- Subscribe to receive email alerts for future network upgrade announcements here.
Dencun network upgrades have been successfully activated on all testnets. Currently, you are configured for deployment on Ethereum Mainnet and are active on Epoch's network 269568It will occur at 13:55 UTC on March 13, 2024.
Last year's upgrade Shapella Upgradecontains some changes. Most notably, the introduction of short-lived data blobs using EIP-4844, also known as “Protodanksharding,” helping to reduce L2 trading fees.
If you want to follow up when an upgrade occurs, please join Community Live Stream.
Upgrade specifications
The Dencun upgrade combines the changes into both the consensus and execution layers of Ethereum. The complete list of protocol changes is EIP-7569. For reference, they are:
Deneb
The complete Python specification for changes affecting the Ethereum consensus layer is Deneb folder of Ethereum/Consensus-specs Repository.
Cancun
The EIP above contains the full specifications for changes that affect the Ethereum execution layer.
Furthermore, these Python specifications are implemented in Ethereum/execution-specs Repository.
Finally, DeneB requires a change in the engine API used to communicate between the consensus layer node and the execution layer node. These are specified in cancun.md file of Ethereum/execution-apis Repository.
Client Release
The following clients will release support Dencun on Ethereum Mainnet: Minimum version The column shows that the client has the lowest DenCun compatible release, Recommended version The columns highlight the latest recommended version. Recommended version Releases usually include performance and stability improvements. If you upgrade from a minimum In Recommended Be sure to read the version and release notes. Releases with significant corruption changes are not listed as follows Recommended.
When selecting clients to run, the validator should be particularly mindful of the risk of running a majority client in either the execution layer (EL) or the consensus layer (CL). You can find an explanation of these risks and their outcomes. here. You can find estimates of the current distribution of EL and CL clients and a guide to switching from one client to another here.
Consensus Layer Mainnet Release
Notes: When running a validator, both the consensus layer beacon node and the validator client must be updated.
Run layer mainnet release
Note:
- While Les supports Dencon, the client is fully audited; It may not be suitable for all production use cases. Please see Reth Readme For other contexts.
FAQ
As an Ethereum user or an ether holder, is there anything I need to do?
In short, no. You can join us Live stream It happens live to see everything!
If you are using a replacement, digital wallet, or hardware wallet, you don't need to do anything unless your replacement or wallet provider informs you to take additional steps.
If you want to run your own Ethereum node, see the following questions:
As a non-staking node operator, what should I do?
Update the node execution and consensus layer client to the versions listed in the table above to be compatible with MainNet Dencun upgrades.
As a stander, what should I do?
Update the node execution and consensus layer client to the versions listed in the table above to be compatible with MainNet Dencun upgrades. Check that both the beacon node and the validator client are updated, and external dependencies such as external block building software.
Additionally, the stakers who want to perform further upgrade process before the mainnet is used ephemery.devnow supports Dencun.
What happens if I'm a staker or node operator and don't take part in the upgrade?
If you are using an Ethereum client (above above) that has not been updated to the latest version, the client will sync to the pre-fork blockchain when an upgrade occurs.
Following old rules, you are trapped in an incompatible chain, unable to send ether or work with post-dencon Ethereum networks.
As an application or tool developer, what should I do?
Check the EIPs included in Dencun to determine if and how the project will affect the project. The only EIP with the meaning of reverse compatibility is EIP-6780, EIP-7044 and EIP-7514.
Why “Denkon”?
Upgrading to a consensus layer uses the star name, and upgrading the running layer follows the Devcon City name. “Dencun” is a combination of Deneb, the first star of Cygnus Constellation, and Cancun, the location of DevCon 3.
Thank you to everyone who helped make the chunks exist. Self-destruct Generally, we'll provide another big overhaul to Ethereum Network .oo!
Original cover image Darren LawrenceThere may be changes due to Tomowaite.
