Important Update: Since the first publication of this post, Lodestar has released a new release. v1.15.0Holesky users will need to upgrade before Dencun activation on February 7th. Additionally, both Prysm and Nimbus have released highly recommended releases of Holesky. Prysm users are advised to use it v4.2.1and Nimbus users V24.2.0.
- Goerli Blobs can be found here: Dencun lived in Goerli at 6:32 UTC on January 17, 2024. You can use Blobs here!
- Sepolia and Holesky will be upgraded over the next two weeks. Dencun activates with the epoch sepolia 132608 (January 30, 22:51 UTC) and at Holesky in Epoch) and Epoch. 29696 (February 7, 11:35 UTC).
- The client release of this announcement is suitable for both testnet upgrades.
- Assuming the Sepolia and Holesky upgrades work, Dencun will then be scheduled on Ethereum Mainnet.
- Subscribe to receive email alerts for network upgrade announcements including Dencun Mainnet One here.
The Dencun Network upgrade was successfully activated on January 17, 2024 on Goerli TestNet. Currently, the remaining two testnets are scheduled, Sepolia and Holesky.
The upgrade includes several changes. Most notably, the introduction of short-lived data blobs using EIP-4844, also known as “Protodanksharding,” helping to reduce L2 trading fees.
Dencun continues last year Shapella Upgrade. It will first be deployed on Ethereum testnets. All of this will perform a smooth upgrade and Dencun will be deployed on Ethereum MainNet.
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 Both Sepolia and Holesky. Further versions will activate support on MainNet. Once these are released, another announcement will be made on this blog.
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 Sepolia & Holesky Release
Note:
- Holesky Lodestar V1.15.0-RC.0 Users Must do Upgrade to v1.15.0.
- Holesky Nimbus V24.1.2 users are highly recommended to upgrade to V24.2.0.
- Holesky Prysm V4.2.1-RC.1 users are highly recommended to upgrade to v4.2.1.
- When running a validator, both the consensus layer beacon node and the validator client must be updated.
Run layer Sepolia & Holesky release
Notes:Les supports Dencon, but the client still pending full audits; Not recommended for production use. 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.
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-status Sepolia or Holesky Node operator, what do you need to do?
Update the node execution and consensus layer client to the versions listed in the table above to be compatible with either testnet upgrade.
As Sepolia or Holesky Staker, what should I do?
Update the node execution and consensus layer client to the versions listed in the table above to be compatible with either testnet upgrade. Make sure both the beacon node and the validator client are updated.
As a non-Sepolia or Holesky node operator or a staker, what should I do?
There's nothing for now. Further announcements will be made regarding Dencun activation on MainNet. You can sign up to receive email alerts here.
Before you recommend using the mainnet, you want to carry out the upgrade process further. ephemery.devnow supports Dencun.
What happens if I'm a Sepolia or Holesky 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.
Original cover image Darren LawrenceThere may be changes due to Tomowaite.
