- Withdrawals are coming! Shapella network upgrades are activated on the Sepolia network in epochs. 56832Scheduled for February 28, 2023 at 4:04:48 AM (UTC)
- Stakers and node operators should read this post along with this one. Withdrawal FAQ
- that much Zhejiang testnet It can be used to test Shapella functionality before upgrading Sepalia.
After months of testing and a temporary Devnet release, the Shanghai/Capella (aka Shapella) network upgrade is now scheduled to be deployed to Sepolia.
This upgrade includes: absorption Allows validators to withdraw their stake from the beacon chain back to the execution layer. It also introduces new features in both the execution and consensus layers.
Upgrade specifications
The Shapella upgrade combines changes to the execution layer (Shanghai), consensus layer (Capella), and engine API.
Shanghai
You can use the execution layer changes included in Shanghai. here. For reference:
EIP-6049 is deprecated. warning. Client teams look forward to self-destruct The semantics will change in future network upgrades, but the opcode’s behavior will not change in Shanghai.
Additionally, you can now see the changes in: EELS (Ethereum Execution Layer Specification)This is a new Python reference implementation of the execution layer.
Capella
Consensus layer changes for Capella upgrades: a cappella directory ~ Of v1.3.0-rc.3 Specification. At a high level, the upgrade introduces:
- Full and partial withdrawals for validators
- BLSToExecutionChange The message allows the verifier to use: BLS_WITHDRAWAL_PREFIX to update it ETH1_ADDRESS_WITHDRAWAL_PREFIXPrerequisites for withdrawal
- Independent state and block record accumulator replacing the original single historical root.
Stakers are encouraged to read the following: Withdrawal FAQ Learn more about how to prepare a cappella.
client release
The next client release will support Shanghai & Capella on the Sepalia testnet. This release Only For Sepolia. There will be follow-up announcements regarding Goerli and mainnet releases.
When choosing which clients to run, validators should keep in mind the risks of running the majority of clients, especially on both EL and CL. You will find a description of these risks and their consequences here. 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 Sepalia Released
Execution layer Seplia release
Note: go-ethereum has released a new recommended release, v1.11.2, for upgrading. v1.11.1 is also compatible with the Shapella Sepolia upgrade.
frequently asked questions
Is there anything I need to do as an Ethereum user or Ethereum holder?
Simply put, no.
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 run your own Ethereum node, see “What do I do as a non-staking node operator?” section below.
What do I need to do as a non-staking node operator?
To be compatible with the Shapella upgrade on the Sepalia testnet, update your nodes to the Ethereum client version listed in the table above.
What should I do as a staker?
To be compatible with the Shapella upgrade on the Sepalia testnet, update your nodes to the Ethereum client version listed in the table above.
Please read the following: Withdrawal FAQ. You can also test temporary items. Zhejiang testnet Before the upgrade was activated in Sepalia.
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.
According to the old rules, you will be stuck in an incompatible chain and will not be able to send Ether or operate on the network after Shapella Sepolia.
What should I do as an application or tool developer?
Shapella does not introduce any major changes to smart contracts. Application and tool developers should review upgrade changes to ensure that fixes have been completed or to understand how to use newly introduced features.
Why “Chappella”?
Upgrades to the execution layer follow Devcon city names, and upgrades to the consensus layer follow star names. Shapella is a combination of Shanghai, where Devcon 2 is located, and Capella, the brightest star in the northern constellation Auriga.
Cover image by: Ding Iran