Ethereum

PECTRA TESTNET presentation | Ether Leeum Foundation Blog

PECTRA TESTNET presentation | Ether Leeum Foundation Blog

The PECTRA Network upgrade will be activated in Ethereum Testnets!

PECTRA Overview

You will live in HOLESKY in EPOCH 115968 (February 24, 21:55 UTC) and EPOCH’s SEPOLIA 222464 (March 5, 7:29 UTC). PECTRA testnet client release is listed Below. If the two test nets are successfully upgraded, the main net activation will be selected.

PECTRA will follow last year Dencun upgrade. Introducing Ether Leeum account, improving validation experiences, and supporting L2 scaling!

This post details these three major improvements. See for more comprehensive outline Ethereum.org upgrade guide.

From EOA to smart account

EIP-7702 It shows a major step towards a wide range of account abstractions, allowing users to improve their external ownership accounts.EOA) Smart contract function.

This hybrid approach combines the simplicity of the EOA and the programming possibility of the contract -based account. Actually, it is possible:

  • Transaction placementWhen multiple operations are reactively in a single transaction. There is no more transaction for “approval” and “swap”!
  • Gas sponsorshipOthers can pay a transaction fee. This is especially useful if you want to trade on an account without an ETH.
  • Alternative certificationIt means a lot Hardware Security Module (HSMS) Today’s phone (HSMS) can be used to approve the account operation through the following technology: Pass key.
  • SpendingIt can limit the number of tokens that certain applications can spend or leak from wallets to improve security.
  • Recovery mechanismIt offers a variety of options that allows users to protect their assets without migrating with new accounts.

To use the EIP-7702, the EOA signs an approval that refers to a specific delegation address that wants to run the code. Once set, the account will obtain the function of the new code (eg, placement, sponsors, authentication logic, etc.). If you choose a delegation, it targets a lot of control, so the EIP-7702 will conduct several safety checks.

  • Chain delegationBy default, the delegation is valid only on a specific chain ID, preventing the same approval from being used in other networks.
  • Non -tax delegationThe approval is connected to the current Nonce of the account and can be automatically invalidated when the Nonce increases.
  • Possibility of mitigationThe owner of the EOA always creates another EIP-7702 privilege that cancel or replace the existing delegation code all the time to prevent permanent lock if something is wrong.

To deeply deeply how all this works @LightClient’s Devcon talks about the subject.

Improvement of the validation test machine UX

Three new EIPs within the PECTRA improve their validation experience. 7251,,, 7002 and 6110.

The first EIP-7251 increases the maximum balance that the validation tester can be rewarded from 32 ETH to 2048 ETH with the update of the withdrawal credential type.

For smaller stators, it enables automatic compensation complexes. Previously, rewards obtained beyond 32 ETH deposits, which are valid, are not included in their active shares. The supermarket, which wants to steak more than 32 ETHs, can only do so in fixed 32 ETH units, and rely on the pool for everything between them. The EIP-7251 can be configured to receive compensation for the entire equity of the existing and new validation tests, up to 2048 eth per validation.

This EIP allows large operators to merge with shared withdrawal credentials, allowing larger operators to integrate multiple valid inspections. This reduces the overall bandwidth requirements of the network. To understand the mechanism in detail, see this conversation. Teku’s Paul Harris.

The EIP-7002 also expands its ability to validate by introducing a withdrawal that can be executed layer triggers this time. Before this EIP, you can only trigger the exit of the active signature of the validity test. If the Ether Leeum address is set as a withdrawal certificate, he can also end. This is a reduction in trust assumptions in the delegation setting because it is a human who controls the owner of the funds (EOA or DAO management smart contracts.

Finally, the EIP-6110 eliminates the remaining traces of the free magician Etherrium: delayed to the validity test deposit and deposit queue. In advance, the beacon chain had to wait for 2048 blocks before processing the validated test machine deposit to explain the potential task proof of Reorgs. This is no longer necessary!

Using the EIP-6110, deposit processing delays will drop from about 9 hours to 13 minutes. TEKU engineers Lucas Saldanha and Stefan Bratanov have the details of EIP-7002 and EIP-6110 Joint Devcon Sea Talk.

Blove Scaling.OO

PECTRA’s final change is the EIP-7691 to increase Etherrium’s blove capacity by 50%!

BLOBS, Dencun upgradeL2 is a temporary data repository that can be used to submit compressed transaction data and evidence to Ethereum L1. After live broadcasting, L2’s L1 fees are reduced to 10-100X, so L2 user transactions are much cheaper.

Ethereum Mainnet currently supports an average of three masses per block and supports up to six to accommodate high demand periods. In the case of EIP-7691, this number increases to an average of 6 and 9.

unequal callingThe BLOB, which the node stores indefinitely, is pruned in the network after 4096 EPOCHS (~ 18th). This is bound to the amount of disk space they can use. The binding pharmaceuticals for the blove are instead of bandwidth. To offset the bandwidth in EIP-7691, PECTRA introduces EIP-7623 to prevent the worst block size.

In order to continue to expand the data throughout the data throughout the bandwidth requirements, all nodes must convert the network to sample the network to store only sub sets in the world where all nodes store all blobs and check the rest of the blobs data. do. Good news: Efforts to support this are already ongoing! The FranceSCO of the Ether Leeum Foundation’s research team Devcon keynote speech.

PECTRA specification

The list of changes introduced in PECTRA is EIP-7600. For reference, they are as follows:


In addition, the entire Python specifications for changing the execution and consensus layer specifications can be found in the following release.


Finally, PECTRA introduces changes in the engine API used for communication between the consensus and the execution layer nodes. These are Prague.md Storage file.

PECTRA activation

The PECTRA Network upgrade is activated in HOLESKY and SEPOLIA:


PECTRA has already been activated in EPEMERY, a stay King Test Net, which is already reset every 28 days. Learn more about it here.

Client release

The following client release is suitable for the PECTRA upgrade. Both HOLESKY and SEPOLIA. The additional version activates support in Mainnet. If these are released, another presentation will be made in this blog.

Sepolia & Holesky Release

When running an validation tester, you need to update both consensus layer Beacon Node and Validator clients.


memo: It was a magnificent customer Open source in April 2024. Since then, it has been included in all PECTRA test efforts with all customers.

Execution layer sepolia & holesky release


FAQ

How does the Ether Leeum network upgrade work?

The Ether Leeum Network Upgrade requires a clear opt in from the node operator of the network. Customer developers are agreed to contain EIPs in the upgrade, but they are not ultimate determinants of adoption.

In the case of Go LIVE, the validation tester and the non -staying node must support the change of protocols that are introduced by manually updating software.

If you use the latest version of Etherrium Client (listed above), the upgraded peer is broken in the fork block, making it a fork for the network. In this scenario, each sub -set of network nodes is connected to those who share upgraded (UN) upgraded state.

Most Etherum Upgrades are not consecutive and rarely lead to forks, but the options to adjust whether the node operator will support upgrade is the main feature of Etherum Governance.

The more thorough outline of Ether Lee’s governance process Tim Beiko’s story.

Is there anything I have to do as an Ether Lee Mainnet user or $ eth holder?

In short, no.

This announcement is associated with Ethereum Testnets: HOLESKY and SEPOLIA. There will be additional announcements on the activation of PECTRA in Ethereum Mainnet, but even Ethereum Mainnet users and $ eth holders do not need to take action.

If you want to upgrade, Live Live, ETHSTAKER at HOLESKY Online viewing party!

By non -steaking Sepolia or Holesky Node operator, what should I do?

To be compatible with the upgrade of the testnet, update the Node’s execution and consensus layer client to the version listed in the table above.

A Sepolia or Holesky Starker, what should I do?

To be compatible with the upgrade of the testnet, update the Node’s execution and consensus layer client to the version listed in the table above. Make sure that both beacon nodes and validation clients have been updated.

What should I do as a non -cell or Holzuki node operator or steak?

There is nothing now. There will be additional announcements on the activation of PECTRA in Mainnet.

What should I do as an application or tooling developer?

Review the EIP included in the PECTRA to see how it affects the project .– There are many new interesting features in both execution and consensus layers!

What should I do as a security researcher?

Please keep an eye on PECTRA BUG BOUNTY Competition. It will come soon 👀

Why “PECTRA”?

The upgrade to the execution layer follows the DEVCON City name and the consensus layer uses the name of the star. “PECTRA” is a combination of ELECTRA, a blue white star in the constellation of Prague and Bull.


Original cover image Julia Solonacorrection Tomosateo.

Related Articles

Back to top button