Updated March 12, 2024: Since this article was originally published, several customer teams have released Dencun-compatible releases containing significant performance and stability improvements. While the previously announced releases are still considered sufficient for the upgrade, a column has been added to the Client versions tables highlighting the latest recommended versions for all customers.
- Mainnet Blobs Are Coming .oO:Two years after its creation on ETHDenver, dozens of test calls and devnets later, protodanksharding is finally live on the mainnet!
- Dencun will be activated on the Ethereum mainnet at Epoch 269568occurring on March 13, 2024 at 1:55 PM UTC. Node operators and stakers should upgrade their software to the versions listed in this announcement.
- To receive email alerts about future network upgrade announcements, subscribe here.
The Dencun network upgrade has been successfully activated on all testnets. It is now ready to be deployed on the Ethereum mainnet and will be activated on the network at the time 269568occurred on March 13, 2024 at 1:55 p.m. UTC.
The upgrade, which follows last year’s Shapella Upgradeincludes several changes, including the introduction of ephemeral data blobs with EIP-4844, also known as “protodanksharding,” which will help reduce L2 transaction fees.
If you would like to follow the upgrade as it happens, please join the community live stream.
Upgrade Specifications
The Dencun upgrade combines changes to Ethereum’s consensus and execution layers. The full list of protocol changes can be found in EIP-7569For reference, they are:
Deneb
The full Python specification regarding changes affecting Ethereum’s consensus layer can be found in the Deneb case of the ethereum/consensus-specs deposit.
Cancun
The EIPs linked above contain the full specifications of changes affecting Ethereum’s execution layer.
Additionally, a Python specification for these is being implemented in the ethereum/runtime specifications deposit.
Finally, Deneb requires changes to the engine API, which is used for communication between nodes in the consensus layer and the execution layer. These are specified in the cancun.md deposit of the ethereum/execution-apis deposit.
Client versions
The following client versions support Dencun on the Ethereum mainnet. THE Minimal version The column indicates the lowest version compatible with Dencun for a client while the Recommended version The column highlights the latest recommended version for it. Recommended version Releases typically contain performance and stability improvements. If you are upgrading from a Minimum has Recommended version, be sure to read the release notes. Versions with significant changes have not been listed as Recommended.
When choosing which client to run, validators should be particularly mindful of the risks of running a majority client on the execution layer (EL) or the consensus layer (CL). An explanation of these risks and their consequences can be found here. An estimate of the current distribution of EL and CL clients and guides for switching from one client to another are available. here.
Consensus Layer Mainnet Versions
Note:when running a validator, the consensus layer beacon node and the validator client must be updated.
Mainnet Execution Layer Versions
Remarks:
- While Reth supports Dencun, the client undergoes a full audit and may not be suitable for all production use cases. To see the Reth README for more context.
FAQ
As an Ethereum user or holder, is there anything I should do?
In short, no. You can join us on the direct to see everything live!
If you’re using an exchange, digital wallet, or hardware wallet, you don’t need to do anything unless your exchange or wallet provider asks you to take additional steps.
If you are running your own Ethereum node, see the next question.
As a non-staking node operator, what should I do?
To be compatible with the Dencun mainnet upgrade, update your node’s execution and consensus layer clients to the versions listed in the table above.
As a staker, what should I do?
To be compatible with the Dencun mainnet upgrade, update your node’s execution and consensus layer clients to the versions listed in the table above. Make sure your beacon node and validator client are up to date, as well as any external dependencies, such as external block creation software.
Additionally, stakers who wish to run the upgrade process multiple times before mainnet are encouraged to use ephemeral.devwhich now supports Dencun.
What if I am a staker or node operator and am not participating in the upgrade?
If you are using an Ethereum client that is not updated to the latest version (listed above), your client will sync to the pre-fork blockchain once the upgrade is complete.
You will be stuck on an incompatible chain under the old rules and will not be able to send Ether or operate on the post-Dencun Ethereum network.
As an application or tool developer, what should I do?
Check out the EIPs included in Dencun to determine if and how they affect your project — many exciting new features are introduced in the execution and consensus layers! The only EIPs with backwards compatibility implications are EIP-6780, EIP-7044 And EIP-7514.
Why “Dencun”?
Consensus layer upgrades use star names, and execution layer upgrades follow Devcon city names. “Dencun” is a combination of Deneb, a first-magnitude star in the constellation Cygnus, and Cancun, the location of Devcon 3.
Thanks to everyone who helped bring the blobs into being and get rid of them (or almost) SELF-DESTRUCTION and generally bring another major overhaul to the Ethereum network .oO!
Original cover image by Darren Lawrencewith modifications by Tomo Saito.
