Dencun Mainnet Announcement | Ethereum Foundation Blog

• Mainnet blob is released.oO: Two years after ETHDenver was launched, after dozens of test calls and development nets, protodanksharding has finally been released on mainnet!
• Dencun will be activated on the Ethereum mainnet in epoch. 269568, which will occur on March 13, 2024 at 13:55 UTC. Node operators and stakers must upgrade their software to the releases listed in this announcement.
• Subscribe to receive email notifications of future network upgrade announcements. here.

Dencun network upgrade has been successfully activated on all testnets. It is now set to be deployed on the Ethereum mainnet and will be active on the network in epoch. 269568Occurs on March 13, 2024 at 13:55 UTC.

Upgrade from last year Shapella Upgradeincludes several changes, most notably the introduction of temporary data blobs in EIP-4844, also known as “protodanksharding”, which helps reduce L2 transaction fees.

Please join the following steps to follow the upgrade as it progresses. Community live streaming.

Upgrade specifications

The Dencun upgrade combines changes to Ethereum’s consensus and execution layers. A full list of protocol changes can be found here: EIP-7569. For reference:

Deneb

The full Python specification for changes affecting Ethereum’s consensus layer can be found here: Deneb folder ~ Of Ethereum/Consensus Specification Storage.

cancun

The EIP linked above contains the full specification for changes affecting the Ethereum execution layer.

Additionally, the Python specification for this is being implemented in: Ethereum/Execution Specifications Storage.

Finally, Deneb requires changes to the engine API used for communication between consensus layer nodes and execution layer nodes. This is specified in the next item. cancun.md file ~ Of Ethereum/Execution API Storage.

client release

The next client release will support Dencun on the Ethereum mainnet.

When choosing which clients to run, validators should pay particular attention to the risks of running multiple clients in the execution layer (EL) or consensus layer (CL). You will find a description of these risks and their consequences. here. You’ll find estimates of the current EL and CL client distribution and guidance for transitioning from one client to another. here.

Consensus layer mainnet launch

memo: When running a validator, both the Consensus Layer Beacon Node and Validator Client must be updated.

Execution layer mainnet launch

note:

• While Reth supports Dencun, the client is undergoing a full audit and Not yet recommended for production use. reference Read Less For more context.
• Geth v1.13.13 fully supports Dencun, but v1.13.14 Recommended because it includes performance improvements to blob transaction processing in transaction pools.

frequently asked questions

Is there anything I need to do as an Ethereum user or Ethereum holder?

In short, no. you can join us live streaming Watch it all happen in real time!

If you use an exchange, digital wallet, or hardware wallet, you do not need to take any action unless you receive further instructions from the exchange or wallet provider.

If you’re running your own Ethereum node, see the following questions:

What do I need to do as a non-staking node operator?

To be compatible with the mainnet Dencun upgrade, update your node’s execution and consensus layer clients to the versions listed in the table above.

What should I do as a staker?

To be compatible with the mainnet Dencun upgrade, update your node’s execution and consensus layer clients to the versions listed in the table above. Make sure both your beacon nodes and validator clients are updated.

Additionally, stakers who wish to run the upgrade process further before mainnet are encouraged to use: ephemery.devNow supports Dencun.

What happens if I’m a staker or node operator and don’t participate in the upgrade?

If you are using an Ethereum client that has not been updated to the latest version (listed above), your client will be in sync with the prefork blockchain when the upgrade occurs.

Under the old rules, you will be stuck on an incompatible chain and will not be able to send Ether or operate on the Ethereum network after Dencun.

What should I do as an application or tool developer?

Review the EIP included with Dencun to determine if and how it will impact your project. A lot of new and exciting features are being introduced across both the execution and consensus layers! The only EIPs that affect backward compatibility are: EIP-6780, EIP-7044 and EIP-7514.

Why “Tenkun”?

Upgrades to the consensus layer take star names, and upgrades to the execution layer take Devcon city names. “Decun” is a combination of the first magnitude star Deneb in Cygnus and Cancun, the location of Devcon 3.

Thank you to everyone who helped me (almost) remove the stain. self-destruct And it provides one more major overhaul for the Ethereum network in general. .oO!

Original cover image by: darren lawrenceEdited by Tomo Saito.