Necessary replace: for the reason that preliminary publication of this put up, Lodestar has revealed a brand new launch, v1.15.0, which Holesky customers should improve to previous to Dencun’s activation on February seventh. Moreover, Prysm and Nimbus have each revealed extremely really useful releases for Holesky. Prysm customers are inspired to make use of v4.2.1, and Nimbus customers v24.2.0.
- Goerli blobs are right here: Dencun went dwell on Goerli at 6:32 UTC on January 17, 2024. Now you can use blobs there!
- Sepolia and Holesky will improve over the following two weeks. Dencun will activate on Sepolia at epoch 132608 (January thirtieth, 22:51 UTC), and on Holesky at epoch 29696 (February seventh, 11:35 UTC).
- Shopper releases on this announcement are appropriate for each testnet upgrades.
- Assuming the Sepolia and Holesky upgrades go nicely, Dencun will probably be scheduled on the Ethereum mainnet subsequent.
- To obtain an e-mail alert for community improve bulletins, together with the Dencun mainnet one, subscribe right here.
The Dencun community improve has efficiently activated on the Goerli testnet on January 17, 2024. It’s now scheduled for the 2 remaining testnets, Sepolia and Holesky, on the following instances:
The improve contains a number of adjustments, most notably the introduction of ephemeral knowledge blobs with EIP-4844, also called “protodanksharding”, which is able to assist cut back L2 transaction charges.
Dencun follows final yr’s Shapella improve. It should first be deployed to Ethereum testnets. As soon as these all are easily working the improve, Dencun will probably be scheduled for deployment on the Ethereum mainnet.
Improve Specification
The Dencun improve combines adjustments to each Ethereum’s consensus and execution layers. The complete listing of protocol adjustments might be present in EIP-7569. For reference, they’re:
Deneb
Full python specs for adjustments affecting Ethereum’s consensus layer might be discovered within the deneb folder of the ethereum/consensus-specs repository.
Cancun
The EIPs linked above comprise the total 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.
Shopper Releases
The next consumer releases assist Dencun on each Sepolia and Holesky. Additional variations will activate assist on mainnet. As soon as these are launched, one other announcement will probably be made on this weblog.
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 might be discovered right here. An estimate of present EL and CL consumer distribution and guides for switching from one consumer to a different might be discovered right here.
Consensus Layer Sepolia & Holesky Releases
Notes:
- Holesky Lodestar v1.15.0-rc.0 customers should improve to v1.15.0.
- Holesky Nimbus v24.1.2 customers are extremely inspired to improve to v24.2.0.
- Holesky Prysm v4.2.1-rc.1 customers are extremely inspired to improve to v4.2.1.
- When working a validator, each the Consensus Layer Beacon Node and Validator Shopper should be up to date.
Execution Layer Sepolia & Holesky Releases
Observe: whereas Reth helps Dencun, the consumer remains to be pending a full audit and is not really useful for manufacturing use. See the Reth README for extra context.
FAQ
As an Ethereum consumer or Ether holder, is there something I have to do?
Briefly, no.
If you happen to use an alternate, digital pockets or {hardware} pockets you don’t want to do something until you’re knowledgeable to take further steps by your alternate or pockets supplier.
If you happen to run your individual Ethereum node, see the following query.
As a non-staking Sepolia or Holesky node operator, what do I have to do?
To be appropriate with the improve on both testnet, replace your node’s execution and consensus layer purchasers to the variations listed within the desk above.
As a Sepolia or Holesky staker, what do I have to do?
To be appropriate with the improve on both testnet, replace your node’s execution and consensus layer purchasers to the variations listed within the desk above. Be certain each your beacon node and validator consumer are up to date.
As a non-Sepolia or Holesky node operator or staker, what do I have to do?
Nothing for now. Additional bulletins will probably be made for Dencun’s activation on mainnet. You may signal as much as obtain an e-mail alert for them right here.
Stakers who wish to run by 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 Sepolia or Holesky 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 newest model (listed above), your consumer will sync to the pre-fork blockchain as soon as the improve happens.
You’ll be caught on an incompatible chain following the previous guidelines and will probably be unable to ship Ether or function on the post-Dencun Ethereum community.
As an utility or tooling developer, what ought to I do?
Overview the EIPs included in Dencun to find out if and the way they have an effect on your venture — there are various 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 mixture of Deneb, a first-magnitude star within the Cygnus constellation, and Cancun, the placement for Devcon 3.
Authentic cowl picture by Darren Lawrence, with modifications by Tomo Saito.
