<img src="https://storage.googleapis.com/ethereum-hackmd/upload_5f7b49ceccd26dd121224fe4688f175a.jpeg” />
- Mainnet blobs are coming .oO: Two years after ETHDenver's inception, dozens of test calls and devnets later, protodanksharding will finally be available on mainnet!
- Dencun will go live on ethereum mainnet around the time 269568, occurred on March 13, 2024 at 13:55 UTC. Node operators and participants must update their software to the versions listed in this announcement.
- To receive email alerts about future network update announcements, subscribe here.
The Dencun network update was successfully activated on all test networks. It is now set to be deployed on the ethereum mainnet and will go live on the network around the time. 269568occurred on March 13, 2024 at 13:55 UTC.
The update, which follows last year's Shapella Updateincludes several changes, notably the introduction of ephemeral data blobs with EIP-4844, also known as “protodanksharding”, which will help reduce L2 transaction fees.
If you want to follow the update as it happens, join the community live broadcast.
Upgrade Specification
The Dencun update combines changes to ethereum's consensus and execution layers. The full list of protocol changes can be found at ethereum.org/EIPS/eip-7569″>EIP-7569. For reference, they are:
deneb
The full Python specifications for changes affecting the ethereum consensus layer can be found at ethereum/consensus-specs/tree/dev/specs/deneb”>deneb file of the ethereum/consensus specifications repository.
Cancun
The EIPs linked above contain the complete specifications for changes affecting the ethereum execution layer.
Additionally, a Python specification for these is being implemented in the ethereum/execution-specs/pulls?q=is%3Apr+base%3Aforks%2Fcancun”>ethereum/execution specifications repository.
Finally, Deneb requires changes to the engine API, used for communication between consensus and execution layer nodes. These are specified in the ethereum/execution-apis/blob/main/src/engine/cancun.md”>cancun.md archive of the ethereum/execution-apis repository.
Customer releases
The following client versions support Dencun on the ethereum mainnet.
When choosing which client to run, validators should especially consider the risks of running a majority client at the execution layer (EL) or consensus layer (CL). An explanation of these risks and their consequences can be found. ethereum/2022/03/24/run-the-majority-client-at-your-own-peril.html”>here. You can find an estimate of the current distribution of EL and CL clients and guides for switching from one client to another. here.
Consensus Layer Mainnet Launches
Note– When a validator runs, both the consensus layer beacon node and the validator client must be updated.
Execution Layer Mainnet Launches
Grades:
- While Reth supports Dencun, the client is undergoing a full audit and is Not yet recommended for production use.. Watch the Reth README for more context.
- While Geth v1.13.13 is fully compatible with Dencun, ethereum/go-ethereum/releases/tag/v1.13.14″>v1.13.14 contains performance improvements to the transaction group's handling of blob transactions and is therefore recommended.
Frequently asked questions
<h3 class="chakra-heading css-145upk7" id="as-an-ethereum-user-or-ether-holder-is-there-anything-i-need-to-do”>As an ethereum user or Ether holder, is there anything I need to do?
In short, no. You can join us on the live broadcast To see everything live!
If you use an exchange, digital wallet, or hardware wallet, you don't need to do anything unless your exchange or wallet provider tells you that you need to take additional steps.
If you run your own ethereum node, see the next question.
As a non-stake node operator, what should I do?
To support the mainnet Dencun upgrade, upgrade your node's consensus and execution layer clients to the versions listed in the table above.
As a bettor, what should I do?
To support the mainnet Dencun upgrade, upgrade your node's consensus and execution layer clients to the versions listed in the table above. Make sure both your beacon node and validator client are up to date.
Additionally, participants who want to perform the upgrade process more times before the mainnet are encouraged to use it. ephemery.devwho now supports Dencun.
What happens if I am a participant 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 update occurs.
You will be trapped on an incompatible chain following 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?
Review the EIPs included in Dencun to determine if and how they affect your project. Many new and interesting features are being introduced in both the execution and consensus layers! The only EIPs with backward compatibility implications are ethereum.org/EIPS/eip-6780″>EIP-6780, ethereum.org/EIPS/eip-7044″>EIP-7044 and ethereum.org/EIPS/eip-7514″>EIP-7514.
Why “Dencun”?
Consensus layer updates use star names, and execution layer updates follow Devcon city names. “Dencun” is the combination of Deneb, a first magnitude star in the constellation Cygnus, and Cancun, the location of Devcon 3.
Thanks to everyone who helped make blobs exist, (almost) rid us of SELF DESTRUCTION and generally perform one more major overhaul of the ethereum network.oO!
Original cover image from Darren Lorenzowith modifications of tomo saito.
