-
Ethereum developers are working on 10 proposals for improvements.
-
Some aspects that they aim to optimize are the management of historical data and general efficiency.
The Pectra upgrade to the Ethereum (ETH) mainnet would be operational in early 2025. However, the improvements included in Pectra will be made in two stages. The second phase does not yet have a certain date.
Pectra will actually be the merger of two updates that were planned independently: Prague and Electra. According to the roadmap of Ethereum, Pectra will take place in 68 daysat the time of this writing.
The ten proposals included in the first stage aim to ensure that the Ethereum network of the future sees Optimized various aspects of the networkfrom improving the handling of historical data and cryptographic operations, to increasing efficiency, helping validators and improving the overall security of Ethereum.
Table of contents
The acronym “EIP” comes from the expression Ethereum Improvement Proposal and, followed by a number, represents the identification of that improvement proposal.
1. EIP-7702: an additional layer of security
This improvement was named “Set EOA account code” or “External Owned Account” or “Externally Controlled Account” and would allow externally controlled accounts (EOA) to have a code, something that until now was limited only to smart contracts.
EOAs are the standard traditional accounts that users control with private keys, but cannot execute code directly.
This EIP enter a additional layer of security and flexibilityallowing EOAs to execute sponsored contracts or engage in delegated transactions. This could facilitate the creation of more sophisticated wallet solutions.
2. EIP-2537: more security bits for Ethereum
EIP 2537 was titled “Precompile for BLS12-381 curve operations” or in Spanish “Precompiled functions for BLS12-381 curve operations”.
These precompiled functions are designed to perform complex or repetitive calculations that would be expensive to implement in standard smart contracts.
In addition, it allows complex operations to be carried out more efficiently, reducing the cost of associated gas to these operations.
EIP-2537 also provides more than 120 bits of securitycompared to the 80 bits of the curve used in ETH, BN254. Security bits are a measure of the difficulty of breaking a cryptographic scheme. More security bits mean greater resistance to attacks.
For its part, the BLS12-381 curve is a particular type of mathematical equation used in cryptography. Its name is derived from the BLS family of curves (Barreto-Lynn-Scott).
Introduces precompiled functions for operations with these curves, such as BLS (Boneh-Lynn-Shacham) signature verification and public key aggregation. These are key for advanced cryptography applications, improving privacy and scalability.
3. EIP-2935: Facilitate access to historical Ethereum data
It aims facilitate access to historical Ethereum datamaking access to old hashes faster and more efficient, which benefits several applications that rely on checking past events.
In the current state of Ethereum, obtaining hashes of old blocks (specifically, blocks that are further than 256 blocks away from the current block) is complicated and expensive.
The purpose of this proposal is to enable a mechanism that allows smart contracts directly access historical block hashes from the Ethereum state, storing them in the state data structure.
Under the title “Serve historical block hashes from state”, EIP-2935 provides a way to generate historical block headers from the Ethereum state, improving efficiency in light node synchronization.
4. EIP-7685: Improve Ethereum execution layer
EIP-7565, titled “General purpose execution layer requests” or “Requests to the Ethereum general purpose execution layer”, is a proposal designed to improve the interoperability and functionality of the Execution Layer (EL) on Ethereum.
The Execution Layer in Ethereum is the layer of this network responsible for processing transactions and executing smart contracts. However, until now, its interaction with other layers (for example, the Consensus Layer, CL) has been limited and with restrictions on what requests can be made between them.
So, EIP-7685 seeks increase the flexibility and capacity of requests within the Execution Layer, enabling more general and dynamic interactions between different layers, which will drive innovation in decentralized application development and improve overall system efficiency.
Ethereum also consists of 5 other layers: Consensus Layer, Application Layer, Data Availability Layer, Network Layer and Infrastructure Layer. .
This multi-layer architecture allows key network functions to be distributed across different strata, optimizing your performance general without compromising its integrity.
5. EIP-6110: Increase validator capital deposits
Proposal 6110“Supply validator deposits on-chain” or “Supply validator deposits on-chain”, would allow the validator deposits directly into the networksimplifying the process and making it more transparent.
This also increases security and reduces potential discrepancies between the consensus and execution layers, which is crucial to maintaining the integrity of the validation system on Ethereum.
Currently, validator deposits must be sent from off-chain, which adds operational complexity.
Validator deposits are a minimum amount of ether that a person or entity must lock in Ethereum in order to become a validator on this network.
These deposits serve as a way of ensure validators have a financial incentive to act honestly when validating transactions and securing the network.
6. EIP-7002: Allow partial withdrawals without taking the entire validator offline
Currently, withdrawals for validators require switching to full withdrawal mode.
He EIP-7002titled “Execution-layer triggerable withdrawals” would enable network validators to make partial withdrawals directly from the Execution Layer (EL), which adds flexibility to the process.
Validators could withdraw rewards without having to completely disconnect your validatorwhich improves the validator experience and reduces the risk of potential validation interruptions.
7. EIP-7251: Increase maximum staking limits on Ethereum
With this improvement called “Increase the max effective balance” or “Increase the maximum effective balance” the maximum effective balance for validators could be increased. In turn, this would lead to Ethereum validators being able to participate in the network with larger amounts of capital.
It refers to the maximum amount of ETH that a validator can take into consideration to participate in block validation and obtain rewards. In Ethereum 2.0, this limit is 32 ETH. This means that although a validator can deposit more than 32 ETH into their account, only the first 32 ETH will be effective for the validation and rewards process.
EIP-7251 intends to increase that limit for validators. Additionally, it could also optimize network performance, as there would be more value at stake and greater incentive to protect it against malicious attacks.
8. EIP-7549: Simplify block validation
Called “Move committee index outside Attestation”, EIP-7549 aims to do more efficient attestation process.
An attestation is a vote cast by a validator that confirms that a specific block is valid and should be added to the Blockchain. This process helps secure the network and maintain the integrity of the blockchain.
This proposal seeks to move the committee index out of the attestation process to simplify block validationwhich speeds up operations and reduces the computational load on validator nodes.
This optimizes validator tracking and improves the network’s ability to process transactions.
9. EIP-7742: Improve interoperability between Ethereum EL and CL layers
The proposal EIP-7742 It was titled as «Uncouple block count between CL and EL«, which in Spanish translates as “Decoupling the block count between the consensus layer and the execution layer”.
This improvement proposes to decouple these block counts to provide greater flexibility in transitions between both layers. This would allow specific updates or adaptations to be made to one layer without affecting the other, which can improve system efficiency and reduce latency.
Currently, the consensus (CL) and execution (EL) layers on Ethereum are synchronized in terms of block count.
While EIP-7742 is not included in the Ethereum roadmap, in a virtual meeting broadcast by YouTubethe developers of the Ethereum ecosystem agreed to incorporate it into Pectra.
10. EIP-TBD: Increase data availability capacity
Initially, this improvement has not yet been formally assigned an identifying number like the previous ones. Due to this, the acronym “TBD”, which is the abbreviation of the English expression “To be determined”.
This improvement It is also not included in the Ethereum roadmap, and its insertion into Pectra was proposed by Francis Li, developer of Base, an Ethereum L2.
Its purpose is increase data availability capacity (known as “blobs”) in Ethereum’s second layer (L2) solutions. Blobs are an important tool to improve the scalability and efficiency of Ethereum. By allowing data to be stored off-chain, blobs help reduce transaction fees and increase network processing power.
By increasing the limit and target number of these blobs, you improve the network’s ability to process data without significantly increasing costs.
This would be especially important to reduce transaction costs in L2 solutions, improving scalability.
Together, these proposals for the Pectra upgrade are designed to improve security, scalability, and operational efficiency on Ethereum, both at the execution and consensus layers.
Crypto Keynote USA
For the Latest Crypto News, Follow ©KeynoteUSA on Twitter Or Google News.
