Derek Chiang of Ethereum said, on the 7th September that EIP-8141 authors found a method to include several transaction features in Ethereum’s transaction envelope by using programmable contracts calls.
You can read more about it here:
- Ethereum developers claim that EIP-8141 allows for the expression of transactional features via contract calls, also known as “programmable frames”.
- The frames can support expiry and signature aggregation as well as privacy proofs or post-transaction statements without adding any new envelope fields.
- EIP-8141 is scheduled for Hegotá, though its specification remains draft and activation dates remain unset.
- The developers are working together to coordinate EIP-8141 and EIP-8130 in order to maintain structure, improve readability of transactions for infrastructure.
- Vitalik Buterin believes that by separating the transactional actions from their dependencies, parallel validation could be achieved and costs reduced.
Chiang is an EIP-8141 contributor and Ethlabs co-author. He described this development as “a “design breakthrough” It is a post The authors of the proposal are currently discussing their recent work. The proposal treats the following as “calls”: transaction expiry; aggregate signatures; privacy-pool Merkle root systems and post-transaction statements. “frames.”
Official draft specification Frame Transactions are defined as the sequence of contracts calls. Different frames are able to validate the transaction, confirm its gas payment and execute user-operations. The current proposal provides three modes, DEFAULT VERIFY AND SENDER.
A frame called VERIFY allows you to verify whether or not a certain condition is met. The SENDER frames executes the operation on the specified account. The frames can also be combined into atomic batching, where all the operations within a group are successful or all of them are reverted.
It still specifies a transaction envelope that includes fields such as chain identifiers (chain id), nonces, senders, fees, frame list, signatures etc. Chiang’s argument is more narrow: it may be possible for developers to add new features through frame targets or call patterns.
The stability of the envelope can help reduce coordination.
The change in the Ethereum transaction envelope has an effect on many other clients than those that execute transactions. The new format must be understood by wallets, Layer 2 network, block explorers and signing devices. Software libraries, infrastructure providers, and software libraries are also affected.
Chiang stated that Ethereum updates occur approximately every nine months. This makes repeated envelope changes difficult and time-consuming. The frame format can be a good interface, while the contracts and protocol components will provide new methods of validation.
It does not imply that any future functionalities would require no network upgrade. EIP-8141 changes Ethereum’s rules of consensus and needs client implementation. Hard forks could be required to implement new opcodes and gas rules, or precompiles. Developers would no longer need to redesign transaction containers every time.
It is important to note that the word “you” means “you”. EIP-8141 specification The company’s primary goal is native account abstraction. The system could be able to support key rotations, alternate signature systems, sponsor gas payments, and batching of transactions. It also wants to reduce the dependency of Ethereum accounts upon secp256k1, which is used for conventionally owned external accounts.
In its reportage on Crypto.news, Vitalik Buterin’s proposed Ethereum transaction redesignProgrammable validation may eventually allow Ethereum to adopt new authentication schemes without having to replace one signature system with another.
EIP-8130 makes it possible to easily inspect frames
Chiang acknowledged that there was a compromise. The complexity of highly abstract transactions makes it hard for sequencers, wallets and infrastructure to understand them before they are executed. For example, a Layer 2 Sequencer might only want to accept specific signature methods due to their predictable computational costs.
In order to explore how frames can work with EIP-8130Another draft proposal for account absorption. EIP-8130 is a keystore onchain where users can register their actors and authentication contracts. Transactions clearly identify their authenticity method.
The structure allows the node to choose which verification process is needed for a particular transaction before it runs arbitrary wallet codes. EIP-8130 proposes a Layer 2 profile that allows a chain to restrict the transaction flow of its transactions to canonical sets of fixed-cost validators, while still allowing other methods for authentication through normal EVM execution.
Chiang claimed that EIP-8130 would impose defined structure over EIP-8141 Frames. Collaboration could maintain the flexibility of frames, while giving wallets or high-throughput networks a more legible format for transactions. Both specifications are still open for revision, as the combined design is not finalized.
Early crypto.news articles examined the competition between EIP-8141 and EIP-8130 during the initial Hegotá scoping process. Recent comments indicate that developers now look for elements compatible rather than only treating proposals as mutually-exclusive alternatives.
Buterin frames are connected with parallel validation
Vitalik Buterin elaborated on the technical directions in a separate postDistinguishing between the transaction “actions” The following are some examples of how to get started: “dependencies.” A transfer of ETH, for example, changes the state of Ethereum. The condition of a dependency can be a Merkle or Zero-Knowledge Proof, signatures, etc.
Buterin claimed that dependent dependencies can be checked simultaneously. Conditions that are not able to access Ethereum’s state can be handled by the mempool once, rather than being processed multiple times during execution. A recursive proof could eventually represent multiple checks, but that is still a future research goal and not a feature.
It could help clients to distinguish predictable transactions from those that need Ethereum’s entire dynamic environment. Buterin claimed that activities which are more easily analyzed statically could have lower gas charges and be scaled further. A fee schedule of this kind has not been approved.
This frame model could be used to implement this method, as both the validation and execution of the contract appear in the code. Ethereum retains flexibility in contract execution, while also allowing simple transactions to provide more details about their needs.
EIP-8141 has a date, but it is still open.
Official Hegotá Meta EIP now lists Frame Transactions and FOCIL as scheduled for inclusion in Ethereum’s Hegotá upgrade. It is an improvement over the earlier status, although it doesn’t freeze EIP-8141’s current technical design.
EIP-8141 is still marked as an EIP Core Proposal. As implementation progresses, its authors may revise frame modes, handling of signatures, accounting for gas, and the relationship to EIP-8130. The Hegotá document also leaves the Sepolia, Hoodi and mainnet activation fields blank.
In order to measure progress, the next steps are updated specifications, implementation of execution-clients, network development, and testing for interoperability between wallets and Layer 2 system. Devs should also consider the mempool’s denial of service risks, as programmable verification can increase costs associated with rejecting invalid transaction.
Testing will help determine if the flexible frames combined with structured authenticators are able to meet the demands of Ethereum’s EVM chain and base layer. Until activation parameters are published, EIP-8141 remains a scheduled but unfinished part of Hegotá.
“This article is not financial advice.”
“Always do your own research before making any type of investment.”
“ItsDailyCrypto is not responsible for any activities you perform outside ItsDailyCrypto.”
Source: crypto.news
