Testnet's sin advertisement | Ethereum Foundation Blog

The Network Pin Update is programmed to be activated in ethereum Testnets!

General description

He will live in Holesky in Epoch 115968 (February 24, 21:55 UTC) and then in sepolia at the time 222464 (March 5, 7:29 UTC). The versions of the client Pina Testnet are listed below. Once both tests have been updated successfully, a Netnet activation time will be chosen.

Pin continues last year Dencun update. Present features to increase ethereum accounts, improve the validator experience, support the L2 and more scale!

This publication explores these three main improvements in detail. To obtain a more complete description, see <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://ethereum.org/en/roadmap/pectra/”>ethereum.org guide for update.

From EOA to smart accounts

<a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-7702″>EIP-7702 It represents an important step towards the abstraction of generalized accounts, which allows users to improve their property accounts externally (<a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://ethereum.org/en/developers/docs/accounts/”>Eoas) with intelligent contract functionality.

This hybrid approach combines the simplicity of the EOA with the programbidness of contract accounts. In practice, enable:

• Transaction lotwhere multiple operations are executed atomically within a single transaction. No more separate transactions to “approve” and “exchange”!
• Gas sponsorshipwhich allows others to pay transaction rates. This is especially useful when you want to make transactions of an account that does not have eth.
• Alternative authenticationWhat many means hardware safety modules (HSMS) on phones today can be used to authorize account operations through technologies such as simple.
• Expenses controlswhich can limit how many chips can spend a specific application, or limit the daily outputs of a wallet, improving security.
• Recovery mechanismsthat provide different options for users to safeguard their assets, without migrating to a new account.

To use EIP-7702, an EOA signs an authorization that points to a specific delegation address whose code wishes to execute. Once established, the account gains the capacities of the new code (for example, lots, sponsorship, authentication logic, etc.). Because choosing a delegation objective delivers a large amount of control, EIP-7702 enforces several security controls:

• Specific delegations of the chain: By default, a delegation is only valid in a specific chain ID, preventing the same authorization from being used in different networks.
• Unrealized delegations: Authorizations can be linked to the current Nance of the account, automatically invalidating them once the Nance increases.
• Revocability: The EOA owner can always create another authorization EIP-7702 that revokes or replaces the existing delegation code, avoiding a permanent block if something goes wrong.

For a deeper immersion in how all this works, see @Devcon Talk about Lightclient's theme on the subject.

UX validator improvements

Three new EIP within pein improves the experience of validator: <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-7251″>7251, <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-7002″>7002 and <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-6110″>6110.

The first, EIP-7251, raises the maximum balance that a validator can receive rewards of 32 eth to 2048 eth, through an update of subscription update of the type of retirement credential.

For smaller stakers, this allows the composition of automatic rewards. Previously, any reward obtained beyond the 32 eth deposit of a validator would not count for its active participation. Stakers who wanted to bet more than 32 eth could only do it at 32 fixed eth increases, trusting rethinking pools for anything intermediate. With EIP-7251, both existing and new validates can be configured to obtain rewards in all of their participation, up to 2048 eth per validator.

This EIP also allows the largest operators to consolidate multiple validators, merging those with shared retirement credentials. This reduces the bandwidth requirement for the network as a whole. To understand the mechanics in detail, look at this talk from Paul Harris de Teku.

EIP-7002 also extends validated skills, this time when introducing triggers from the execution layer. Before this EIP, only the active signature key of a validator could activate an exit. Now, if an ethereum address is established as a retirement credential, that can also force an exit. This reduces the assumptions of confidence in the delegation environments, since the owner of the funds, whether human in control of an EOA or an intelligent contract managed by DAO, can always begin without confidence an exit.

Finally, EIP-6110 eliminates a persistent vestige of ethereum prior to shit: the delay between validator deposits and its addition to the tail of deposits. Before the merger, the beacon chain had to wait 2048 blocks before processing the validator deposits to take into account the possible reorganization of work test. This is no longer necessary!

With EIP-6110, delays in deposit processing now fall from about 9 hours to approximately 13 minutes. Teku Lucas Saldanha and Stefan Bratanov engineers covered the details of EIP-7002 and EIP-6110 in their Devcon conversation Sea.

BLOB SCALE .OO

The final change in Pin is EIP-7691, increasing Blob's capacity of ethereum by 50%!

Blobs, introduced into the <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-7569″>Dencun updateThey are storage of ephemeral data that L2S can use to send compressed transaction data and tests to ethereum L1. Since they went, they have reduced L1 rates for L2S by 10-100X, resulting in much cheaper L2 user transactions.

The ethereum Mainnet currently supports an average of 3 blobs per block, with a maximum of 6 to accommodate high demand periods. With EIP-7691, these numbers will increase to an average of 6 and maximum of 9.

Unlike CalitataThat the nodes store indefinitely, the blobs can be pruned from the network after 4096 times (~ 18 days). This limits the amount of disk space they can use. The binding restriction for Blobs is, instead, bandwidth, since stains must be gossip on the equal layer of ethereum. To compensate for the increase in bandwidth caused by EIP-7691, Pin also presents EIP-7623, which limits the worst size of a block.

To continue climbing the ethereum data performance without a corresponding increase in bandwidth requirements, we must change from a world where each node stores each BLOB to one where the nodes store only a subset and test the network to verify the data of BLOB remaining. Good news: I work to support this is already underway! Francesco of the ethereum Foundation Research Team described this roadmap of scale in its Key Devcon Note.

Special spectra

The list of changes introduced in pein can be found in <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://eips.ethereum.org/EIPS/eip-7600″>EIP-7600. As a reference, they are:

In addition, Python's complete specification for changes in execution and specifications of the consensus layer can be found in the following versions:

Finally, Pin also introduces changes in the Motor API used for communication between consensus and nodes of the execution layer. These are specified in the <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://github.com/ethereum/execution-apis/blob/main/src/engine/prague.md”>Prague.md repository archive.

Right activation

The tong network update will be activated in Holesky and sepolia as follows:

In addition, Pin has already been activated in Ephemery, a test test that is restored every 28 days. Read more about that here.

Customer releases

The following customer versions are suitable for the sicking update in both Holesky and sepolia. Other versions will activate support in Mainnet. Once they are published, another announcement will be made in this blog.

Sepolia and Holesky launches of consensus layer

When executing a validator, both the beacon node of the consensus layer and the validator client must be updated.

Note: Grandine's client was Open source in April 2024. Since then, it has been included in all the sicking efforts along with other clients.

Sepolia and Holesky launches of the execution layer

Frequent questions

<h3 class="chakra-heading css-145upk7" id="how-do-ethereum-network-upgrades-work”>How do the ethereum network updates work?

ethereum network updates require explicit option of node operators on the network. While customer developers reach a consensus on which EIP is included in an update, they are not the best decisors of their adoption.

For the update to be placed live, the validators and the unused nodes must manually update their software to admit the changes in the protocol that are introduced.

If they use an ethereum client that is not updated to the latest version (previously listed), in the fork block, it will disconnect from their updated peers, which leads to a bifurcation on the network. In this scenario, each subset of the network nodes will only remain connected to those who share their (ON) updated.

Although most ethereum updates are not contentious and cases that lead to forks have been rare, the option for nodes operators to coordinate whether to admit an update or is not a key feature of ethereum's governance.

For a more exhaustive overview of the ethereum government process, see This Tim Beiko talk.

<h3 class="chakra-heading css-145upk7" id="as-an-ethereum-mainnet-user-or-eth-holder-is-there-anything-i-need-to-do”>As a user of ethereum Mainnet or holder of $ eth, is there anything you need to do?

In short, no.

This announcement only refers to ethereum Testnets: Holesky and sepolia. Another announcement will be made for the activation of pein at the ethereum Mainnet, but still, ethereum Mainnet users and the $ eth holders have to act are not expected.

If you want to see the live update in Holesky, Ethstaker is organizing a Online visualization party!

Like a print Sepolia or Holesky Node operator, what do I need to do?

To be compatible with the update in any of the Testnet, update the clients of execution of their node and consensus layer to the versions listed in the previous table.

As Sepolia or Holesky Staker, what do I need to do?

To be compatible with the update in any of the Testnet, update the clients of execution of their node and consensus layer to the versions listed in the previous table. Make sure both your Beacon node and your validator client are updated.

As a node operator or node rally, what do you need to do?

Nothing for now. Additional ads will be made for the activation of pein in Mainnet.

As an application developer or tools, what should I do?

Check the EIP included in Pin to determine if they affect your project and how many new exciting features are introduced in the execution and consensus layers!

As a security researcher, what should I do?

Be attentive to a publication on the competition Pin Bug Bounty <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://x.com/cantinaxyz/status/1889660786936885365″>coming soon

Why “sin”?

The updates to the execution layer follow the names of the city of Devcon, and those to the consensus layer use the names of the stars. “Pectra” is the combination of Prague, the location of Devcon IV and Electra, a white blue giant star in the Taurus constellation.

Original cover image by Julia Soloninawith modifications of <a target="_blank" target="_blank" rel="noopener" class="chakra-link css-ug8vf0" href="https://twitter.com/tomosaito”>I take Saito.