March 12, 2024 update: Since the initial release of this post, multiple client teams have rolled out Dencun-compatible versions that offer substantial enhancements in performance and stability. Although previously shared versions are still deemed adequate for the upgrade, a new column has been incorporated into the Client Releases tables to highlight the most recent suggested versions for all clients.
- Mainnet blobs are on the way .oO: After two years following its inception at ETHDenver, numerous testing calls, and development networks, protodanksharding is set to launch on the mainnet!
- Dencun will go live on the Ethereum mainnet at epoch 269568, scheduled for March 13, 2024, at 13:55 UTC. Node operators and stakers must upgrade their software to the versions specified in this announcement.
- To receive email notifications for upcoming network upgrade announcements, subscribe here.
The Dencun network upgrade has successfully been applied across all testnets. It is now prepared for deployment on the Ethereum mainnet, activating at epoch 269568, on March 13, 2024, at 13:55 UTC.
This upgrade, following last year’s Shapella upgrade, introduces several modifications, with the most noteworthy being the implementation of ephemeral data blobs through EIP-4844, referred to as “protodanksharding”, aimed at lowering L2 transaction fees.
For those interested in observing the upgrade as proceedings unfold, please join the community livestream.
Upgrade Specification
The Dencun upgrade encompasses modifications to both Ethereum’s consensus and execution layers. The complete list of protocol updates can be accessed in EIP-7569. For reference, they include:
Deneb
Comprehensive python specifications for changes affecting Ethereum’s consensus layer are available in the deneb folder of the ethereum/consensus-specs repository.
Cancun
The EIPs referenced above contain detailed specifications for alterations affecting Ethereum’s execution layer.
Moreover, a python specification for these changes is being developed in the ethereum/execution-specs repository.
Finally, Deneb necessitates adjustments to the Engine API, which facilitates communication between the consensus and execution layer nodes. These modifications are detailed in the cancun.md file of the ethereum/execution-apis repository.
Client Releases
The following client releases facilitate Dencun on the Ethereum mainnet. The Minimum Version column signifies the lowest release compatible with Dencun for each client, while the Recommended Version column showcases the latest suggested version. Recommended Version releases usually incorporate performance and stability enhancements. When upgrading from a Minimum to a Recommended version, please ensure to read the release notes. Releases with significant breaking changes have not been included as Recommended.
Validators should carefully consider the risks associated with running a majority client on either the execution layer (EL) or consensus layer (CL) when selecting a client. An explanation of these risks and their implications can be found here. An estimation of the current EL and CL client distribution as well as guides for transitioning from one client to another can be located here.
Consensus Layer Mainnet Releases
Note: When operating a validator, both the Consensus Layer Beacon Node and Validator Client must be updated.
Execution Layer Mainnet Releases
Notes:
- While Reth supports Dencun, it is currently under a complete audit and may not be suitable for all production scenarios. For further details, refer to the Reth README.
FAQ
As an Ethereum user or Ether holder, is there anything I need to do?
In a nutshell, no. You can tune in to the livestream to watch the process unfold live!
If you utilize an exchange, digital wallet, or hardware wallet, no action is needed on your part unless your exchange or wallet provider issues a notice suggesting additional measures.
If you operate your own Ethereum node, refer to the subsequent question.
As a non-staking node operator, what do I need to do?
To ensure compatibility with the mainnet Dencun upgrade, update your node’s execution and consensus layer clients to the versions outlined in the table above.
As a staker, what do I need to do?
For compatibility with the mainnet Dencun upgrade, update both your beacon node and validator client to the versions specified in the table above, and ensure any external dependencies, such as block-building software, are also updated. It is crucial that both your beacon node and validator client are up-to-date.
Moreover, stakers looking to practice the upgrade process multiple times before the mainnet launch are encouraged to utilize ephemery.dev, which currently supports Dencun.
What happens if I am a staker or node operator and I do not participate in the upgrade?
If you are using an Ethereum client that has not been updated to the current version (as listed above), your client will be aligned with the pre-fork blockchain following the upgrade.
Consequently, you will remain on an incompatible chain adhering to the previous rules, thus preventing you from sending Ether or interacting with the post-Dencun Ethereum network.
As an application or tooling developer, what should I do?
Examine the EIPs incorporated in Dencun to assess how they might impact your project—numerous exciting features are being introduced across the execution and consensus layers! The only EIPs with potential backwards compatibility concerns include EIP-6780, EIP-7044, and EIP-7514.
Why “Dencun”?
Upgrades to the consensus layer are named after stars, while those to the execution layer follow the names of Devcon cities. “Dencun” represents a fusion of Deneb, a prominent star in the Cygnus constellation, and Cancun, the venue for Devcon 3.
A heartfelt thank you to all who contributed to the realization of the blobs, (almost) liberated us from SELFDESTRUCT, and generally enabled yet another major enhancement to the Ethereum network .oO!
Original cover image by Darren Lawrence, with modifications by Tomo Saito.
