February 27, 2024—Mainnet blobs are on their way. Two years after its inception at ETHDenver, and following numerous testing calls and development networks, protodanksharding is set to go live on the Ethereum mainnet!
The Dencun network upgrade will activate on the Ethereum mainnet at epoch 269568, which will take place on March 13, 2024, at 13:55 UTC. Node operators and stakers must update their software to the versions listed in this announcement.
Subscribe here to receive email notifications for future network upgrade announcements.
The Dencun upgrade has successfully been activated on all testnets and is now set for deployment on the Ethereum mainnet, where it will activate at epoch 269568, on March 13, 2024, at 13:55 UTC.
The upgrade follows last year’s Shapella upgrade and introduces significant changes, including the addition of ephemeral data blobs via EIP-4844, also known as “protodanksharding,” aimed at reducing L2 transaction fees.
Join the community livestream here to follow the upgrade in real time as it unfolds.
Upgrade Details
The Dencun upgrade combines changes to Ethereum’s consensus and execution layers. The full list of protocol modifications can be found in EIP-7569. For reference, these changes include:
- Deneb: Full Python specifications for changes to Ethereum’s consensus layer are located in the deneb folder of the ethereum/consensus-specs repository.
- Cancun: The EIPs mentioned above contain the complete specifications for changes to Ethereum’s execution layer. Additionally, a Python specification for these changes is being implemented in the ethereum/execution-specs repository.
- Engine API Changes: Deneb requires changes to the Engine API, which is used for communication between the consensus and execution layer nodes. These changes are detailed in the cancun.md file of the ethereum/execution-apis repository.
Client Releases
The following client releases support Dencun on the Ethereum mainnet. Validators should exercise caution when choosing a client and avoid running a majority client on either the execution layer (EL) or consensus layer (CL). You can find a summary of the risks and their potential consequences here. An estimate of current client distribution and guides for switching between clients are available here.
- Consensus Layer Mainnet Releases: When running a validator, ensure both the Consensus Layer Beacon Node and Validator Client are updated.
- Execution Layer Mainnet Releases: Note that while Reth supports Dencun, it is undergoing a full audit and is not yet recommended for production use. See the Reth README for more context. Geth v1.13.14 is recommended due to performance improvements in handling blob transactions.
Frequently Asked Questions
- What do I need to do as an Ethereum user or Ether holder?: Generally, no action is required. You can watch the upgrade unfold on the livestream! If you use an exchange or wallet, follow any specific instructions they provide.
- What should non-staking node operators do?: Update your execution and consensus layer clients to the specified versions to remain compatible with the Dencun upgrade.
- What about stakers?: Update your execution and consensus layer clients as specified, including your beacon node and validator client.
- What if I don’t upgrade as a staker or node operator?: You may end up on an incompatible chain and will be unable to send Ether or operate on the post-Dencun Ethereum network.
- What should application or tooling developers do?: Review the EIPs included in Dencun to understand how they impact your project. Key backward compatibility EIPs include EIP-6780, EIP-7044, and EIP-7514.
Why “Dencun”?
The names for upgrades follow a pattern: consensus layer upgrades use star names, and execution layer upgrades follow Devcon city names. “Dencun” combines Deneb, a bright star in the Cygnus constellation, and Cancun, the site of Devcon 3.
