.jpg)
- Withdrawals are coming! The Shapella network upgrade will be implemented on the Sepolia network in the future 56832scheduled for 4:04:48 AM UTC on February 28, 2023
- Contractors and contract operators should read this publication in addition Frequently asked questions about withdrawals
- the Zhejiang Test Network It can be used to test Shapella functionality before upgrading Sepolia
After months of testing and launching an ephemeral devnet, the Shanghai/Capella (aka Shapella) network upgrade is now scheduled to be deployed in Sepolia.
Follow this upgrade Merger It enables validators to withdraw their stake from the Beacon Chain to the execution layer. It also introduces new functionality for both the implementation and consensus layer.
Upgrade specifications
The Shapella upgrade combines changes made to the Execution Layer (Shanghai), Consensus Layer (Capella) and Engine API.
Shanghai
Built-in implementation layer changes are available in Shanghai here. For reference, they are:
Note that EIP-6049 is just a deprecation warning. Customer teams expect Self-destruction The semantics will have to change in future network upgrades, but the opcode behavior remains unchanged in Shanghai.
In addition, changes can now be viewed in… Ethereum Execution Layer Specification (EELS)which is a new Python reference implementation of the implementation layer.
Capella
Changes made to the Capella upgrade consensus layer are specified in a file Capella Guide Subordinate Specifications v1.3.0-rc.3. At a high level, the upgrade offers:
- Full and partial withdrawals for auditors
- BLSToExecutionChange messages, which allow auditors to use BLS_WITHDRAWAL_PREFIX To update it to ETH1_ADDRESS_WITHDRAWAL_PREFIXa prerequisite for withdrawals
- An independent state and a bloc of historical accumulations, replacing the single original historical roots
Stakeholders are encouraged to read Frequently asked questions about withdrawals For more information on how to prepare for a cappella.
Customer versions
The following client releases support Shanghai & Capella on the Sepolia testnet. Note that these versions Just For Sepolia. Goerli and mainnet versions will be announced later.
When selecting which client to run, auditors should be particularly aware of the risks of running a majority client on both EL and CL. An explanation of these risks and their consequences can be found here here. An estimate of the current EL and CL client distribution and evidence of client-to-customer conversion can be found here.
Sepolia consensus layer versions
Sepolia implementation layer versions
Note: go-ethereum has released a new recommended version, v1.11.2, for upgrading. Version 1.11.1 is also compatible with the Shapella Sepolia upgrade.
Instructions
As an Ethereum user or Ethereum holder, is there anything I should do?
In short, no.
If you use an exchange, digital wallet or hardware wallet, you do not need to do anything unless you are notified to take additional steps by your exchange or wallet provider.
If you run your own Ethereum node, see the “As a non-stored node operator, what should I do?” section. Section below.
As a non-survey 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 stakeholder, 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 advise you to read Frequently asked questions about withdrawals. Plus, you can test things in the short term Zhejiang Test Network Before activating the upgrade on Sepolia.
What happens if I’m an administrator 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 (mentioned above), your client will sync with the pre-fork blockchain once the upgrade occurs.
You will be stuck on an incompatible chain according to the old rules and will not be able to transmit ether or work on the post-Chapella Cipolia network.
As an app or tool developer, what should I do?
Shapella does not introduce radical changes to smart contracts. Application and tool developers should review upgrade changes to ensure that any fixes have been made, or to understand how to use newly introduced functionality.
Why “Shabella”?
Promotions to the implementation layer follow Devcon city names, and promotions to the consensus layer follow star names. “Chapella” is a combination of Shanghai, the site of DEFCON 2, and Capella, the brightest star in the constellation Auriga North.
Cover image by Yiran Ding
