March 12, 2024 update: Since the original release of this article, numerous client teams have introduced Dencun-compatible versions featuring notable enhancements in performance and stability. While previously mentioned releases are still deemed adequate for the upgrade, a column has been included in the Client Releases tables that showcases the latest recommended versions for all clients.
- Mainnet blobs are on the way .oO: Two years following its ETHDenver initiation, numerous testing calls and developer networks later, protodanksharding is finally being launched on mainnet!
- Dencun will activate on the Ethereum mainnet at epoch 269568, scheduled for March 13, 2024 at 13:55 UTC. Node operators & stakers are required to upgrade their software to the versions specified in this announcement.
- To receive notifications via email for future network upgrade announcements, subscribe here.
The Dencun network upgrade has been successfully implemented on all testnets. It is now prepared for rollout on the Ethereum mainnet and will be activated on the network at epoch 269568, occurring on March 13, 2024 at 13:55 UTC.
This upgrade follows last year’s Shapella upgrade and incorporates a variety of modifications, most significantly the introduction of ephemeral data blobs through EIP-4844, also referred to as “protodanksharding”, which will assist in decreasing L2 transaction costs.
If you wish to observe the upgrade in real-time, please join the community livestream.
Upgrade Specification
The Dencun upgrade amalgamates alterations to both Ethereum’s consensus and execution frameworks. The complete list of protocol modifications can be accessed in EIP-7569. For your reference, they are:
Deneb
Comprehensive Python specifications for modifications impacting Ethereum’s consensus layer are available in the deneb folder of the ethereum/consensus-specs repository.
Cancun
The EIPs mentioned above provide the full specifications for changes related to Ethereum’s execution framework.
Moreover, a Python specification for these modifications is currently being developed in the ethereum/execution-specs repository.
Finally, Deneb necessitates modifications to the Engine API, which facilitates communication between the consensus and execution layer nodes. These changes are detailed in the cancun.md file within the ethereum/execution-apis repository.
Client Releases
The subsequent client releases endorse Dencun on the Ethereum mainnet. The Minimum Version column indicates the lowest Dencun-compatible release available for a client, while the Recommended Version column showcases the latest recommended release for it. Recommended Version releases usually contain enhancements in performance and stability. When moving from a Minimum to a Recommended version, be sure to review the release notes. Updates that involve significant breaking changes have not been included as Recommended.
In selecting which client to implement, validators should remain particularly cautious of the risks associated with operating a majority client on either the execution layer (EL) or consensus layer (CL). A detailed explanation of these risks and their implications can be found here. Estimates of the current EL and CL client distribution, as well as guides for transitioning from one client to another, can be found 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:
- Although Reth is compatible with Dencun, the client is currently undergoing a comprehensive audit and might not be appropriate for all production scenarios. Refer to the Reth README for additional information.
FAQ
As an Ethereum user or Ether holder, is there anything I need to do?
In essence, no. You are welcome to join us on the livestream to witness everything occur in real-time!
If you are utilizing an exchange, digital wallet, or hardware wallet, there is no requirement for action unless instructed to undertake additional measures by your exchange or wallet provider.
If you operate your own Ethereum node, please refer to the subsequent question.
As a non-staking node operator, what actions should I take?
To ensure alignment with the mainnet Dencun upgrade, upgrade the execution and consensus layer clients of your node to the versions listed in the table above.
As a staker, what actions should I take?
To be compatible with the mainnet Dencun upgrade, make sure to update your node’s execution and consensus layer clients to the versions specified in the table above. Ensure that both your beacon node and validator client are updated, as well as any external dependencies, including external block building software.
Moreover, stakers wishing to navigate the upgrade process multiple times prior to mainnet are encouraged to utilize ephemery.dev, which now accommodates Dencun.
What transpires if I am a staker or node operator and I choose not to partake in the upgrade?
If you are operating an Ethereum client that has not been upgraded to the latest version (as noted above), once the upgrade takes place, your client will synchronize to the pre-fork blockchain.
You will remain stuck on an incompatible chain adhering to the previous rules and will be unable to send Ether or function on the post-Dencun Ethereum network.
As an application or tooling developer, what steps should I take?
Examine the EIPs contained in Dencun to ascertain if and how they influence your project — numerous new thrilling features are being introduced across both the execution and consensus layers! The only EIPs with implications for backward compatibility are EIP-6780, EIP-7044 and EIP-7514.
Why is it called “Dencun”?
Consensus layer upgrades utilize star names, while execution layer upgrades adopt Devcon city names. “Dencun” is a combination of Deneb, a first-magnitude star in the Cygnus constellation, and Cancun, the venue for Devcon 3.
Thanks to everyone who contributed to the creation of the blobs, (nearly) liberated us from SELFDESTRUCT and generally provided yet another significant enhancement to the Ethereum network .oO!
Original cover image by Darren Lawrence, with alterations by Tomo Saito.