- Withdrawals are coming! The Shapella network upgrade will be enabled on the Sepolia network at the time 56832scheduled for 04:04:48 UTC on February 28, 2023
- Stakers and node operators should also read this article as well as the FAQ on withdrawals
- THE Zhejiang Test Network can be used to test Shapella features before upgrading to Sepolia
After months of testing and a short-lived devnet launch, the Shanghai/Capella (aka Shapella) network upgrade is now scheduled to be deployed on Sepolia.
This upgrade follows The merger and allows validators to withdraw their stake from the Beacon Chain to the execution layer. It also introduces new features in both the execution layer and the consensus layer.
Upgrade Specifications
The Shapella upgrade combines changes to the execution layer (Shanghai), consensus layer (Capella), and engine API.
Shanghai
Runtime layer changes included in Shanghai are available hereFor reference, they are:
Note that EIP-6049 is only a deprecation warningCustomer teams expect SELF-DESTRUCTION The semantics will change in future network upgrades, but the opcode behavior remains unchanged in Shanghai.
Additionally, changes can now be viewed in the Ethereum Execution Layer Specification (EELS)which is a new Python reference implementation for the runtime layer.
Chapel
Changes to the consensus layer for the Capella upgrade are specified in the acapella directory of the Specifications for version v1.3.0-rc.3At a high level, the upgrade introduces:
- Full and partial withdrawals for validators
- BLSToExecutionChange messages, which allow validators using a PREFIX_WITHDRAWAL_BLS to update it to a WITHDRAWAL_PREFIX_ADDRESS_ETH1a prerequisite for withdrawals
- Independent state and bloc historical accumulators, replacing the original singular historical roots
Punters are encouraged to read the Withdrawal FAQ for more information on how they should prepare for Capella.
Client versions
The following client versions support Shanghai and Capella on the Sepolia testnet. Note that these versions are only for Sepolia. A later announcement will be made for the Goerli and mainnet versions.
When choosing which client to execute, validators should be particularly mindful of the risks associated with executing a majority client on both EL and CL. An explanation of these risks and their consequences can be found here. An estimate of the current distribution of EL and CL clients and guides for switching from one client to another are available. here.
Sepolia versions of Consensus Layer
Sepolia versions of the execution layer
Note: go-ethereum has released a new recommended version, v1.11.2, for the upgrade. v1.11.1 is also compatible with the Shapella Sepolia upgrade.
FAQ
As an Ethereum user or holder, is there anything I should do?
In short, no.
If you’re using an exchange, digital wallet, or hardware wallet, you don’t need to do anything unless your exchange or wallet provider asks you to take additional steps.
If you run your own Ethereum node, see the “As a non-staking node operator, what should I do?” section below.
As a non-staking node operator, what should I do?
To be compatible with the Shapella upgrade on the Sepolia testnet, update your node to the version of your Ethereum client listed in the table above.
As a staker, what should I do?
To be compatible with the Shapella upgrade on the Sepolia testnet, update your node to the version of your Ethereum client listed in the table above.
We recommend that you read the Withdrawal FAQ. Additionally, you can test things on the ephemeral Zhejiang Test Network before activating the upgrade on Sepolia.
What if I am a staker 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 upgrade is complete.
You will be stuck on an incompatible chain under the old rules and will not be able to send Ether or operate on the post-Shapella Sepolia network.
As an application or tool developer, what should I do?
Shapella does not introduce any radical changes to smart contracts. Application and tool developers should review the upgrade changes to ensure that fixes are applied or to understand how to use the newly introduced features.
Why “Shapella”?
The execution layer updates follow the names of Devcon cities, and the consensus layer updates follow the names of stars. “Shapella” is the combination of Shanghai, the location of Devcon 2, and Capella, the brightest star in the northern constellation Auriga.
Cover image by Yiran Ding
