The Dencun community improve has efficiently activated on all testnets. It’s now set for deployment on the Ethereum mainnet and can activate on the community at epoch 269568, occuring on March 13, 2024 at 13:55 UTC.
The improve, which follows final yr’s Shapella improve, contains a number of adjustments, most notably the introduction of ephemeral knowledge blobs with EIP-4844, also referred to as “protodanksharding”, which is able to assist cut back L2 transaction charges.
If you would like to observe the improve because it occurs, please be part of the group livestream.
Improve Specification
The Dencun improve combines adjustments to each Ethereum’s consensus and execution layers. The total checklist of protocol adjustments could be present in EIP-7569. For reference, they’re:
Deneb
Full python specs for adjustments affecting Ethereum’s consensus layer could be discovered within the deneb folder of the ethereum/consensus-specs repository.
Cancun
The EIPs linked above include the complete specs for adjustments affecting Ethereum’s execution layer.
Moreover, a python specification for these is being applied within the ethereum/execution-specs repository.
Lastly, Deneb requires adjustments to the Engine API, used for communication between the consensus and execution layer nodes. These are specified within the cancun.md file of the ethereum/execution-apis repository.
Consumer Releases
The next consumer releases assist Dencun on the Ethereum mainnet.
When selecting which consumer to run, validators needs to be particularly aware of the dangers of working a majority consumer on both the execution layer (EL) or consensus layer (CL). An explainer of those dangers and their penalties could be discovered right here. An estimate of present EL and CL consumer distribution and guides for switching from one consumer to a different could be discovered right here.
Consensus Layer Mainnet Releases
Word: when working a validator, each the Consensus Layer Beacon Node and Validator Consumer have to be up to date.
Execution Layer Mainnet Releases
Notes:
* Whereas Reth helps Dencun, the consumer is present process a full audit and isn’t but advisable for manufacturing use. See the Reth README for extra context.
* Whereas Geth v1.13.13 absolutely helps Dencun, v1.13.14 accommodates efficiency enhancements to the transaction pool’s dealing with of blob transactions and is thus advisable.
FAQ
As an Ethereum person or Ether holder, is there something I must do?
Briefly, no. You may be part of us on the livestream to look at all of it occur stay!
For those who use an change, digital pockets or {hardware} pockets you do not want to do something until you might be knowledgeable to take extra steps by your change or pockets supplier.
For those who run your individual Ethereum node, see the subsequent query.
As a non-staking node operator, what do I must do?
To be suitable with the mainnet Dencun improve, replace your node’s execution and consensus layer shoppers to the variations listed within the desk above.
As a staker, what do I must do?
To be suitable with the mainnet Dencun improve, replace your node’s execution and consensus layer shoppers to the variations listed within the desk above. Ensure that each your beacon node and validator consumer are up to date.
Moreover, stakers who need to run by means of the improve course of extra instances earlier than mainnet are inspired to make use of ephemery.dev, which now helps Dencun.
What occurs if I’m a staker or node operator and I don’t take part within the improve?
In case you are utilizing an Ethereum consumer that isn’t up to date to the most recent model (listed above), your consumer will sync to the pre-fork blockchain as soon as the improve happens.
You can be caught on an incompatible chain following the outdated guidelines and shall be unable to ship Ether or function on the post-Dencun Ethereum community.
As an software or tooling developer, what ought to I do?
Evaluation the EIPs included in Dencun to find out if and the way they have an effect on your challenge — there are numerous new thrilling options being launched throughout each the execution and consensus layers! The one EIPs with backwards compatibility implications are EIP-6780, EIP-7044 and EIP-7514.
Why “Dencun”?
Upgrades to the consensus layer use star names, and people to the execution layer observe Devcon metropolis names. “Dencun” is the mix of Deneb, a first-magnitude star within the Cygnus constellation, and Cancun, the placement for Devcon 3.
Thanks to everybody who helped carry the blobs into existence, (practically) rid us of SELFDESTRUCT and customarily ship another main overhaul to the Ethereum community .oO!
Authentic cowl picture by Darren Lawrence, with modifications by Tomo Saito.
