eip

EIP-8450 proposal update, intended to introduce a quantum-resistant public key registration mechanism for Ethereum validators, using a hash-based cryptographic scheme, including leanXMSS keys and VRF tree roots.The update clarifies that the registration and replacement of quantum-resistant keys are authorized by BLS signature keys, and sets a replacement delay of at least one Epoch and a replay protection mechanism; this proposal is currently still in the Draft stage and has not yet been deployed.

Due to the ChainSecurity report revealing compatibility and security issues with EIP-8037 and certain smart contracts, core developers decided last week to postpone the Hoodi testnet upgrade to Glamsterdam. The issues identified so far include: the remaining Gas during transaction execution may increase, leading to underflow in some Gas counting logic and triggering rollbacks, or causing code paths that should not be executed to be triggered, making the transaction appear successful. Additionally, some contracts may underestimate usage due to the inability to correctly calculate Gas consumption during calls.ChainSecurity previously stated that 13 real cases have been identified and they are responsibly disclosing this information to the affected projects. Toni Wahrstätter mentioned that this week they will further investigate the relevant contracts and assess subsequent solutions, which may require collaboration among application developers, core developers, auditors, and node operators. In the worst-case scenario, adjustments to the protocol specifications may be necessary. He reminded application developers and auditors to check the compatibility of contracts with EIP-8037 and EIP-8038 and to report issues in a timely manner.

Paranoid developer Ignotus Nemo proposed a recursive aggregation scheme for EIP-8288 on the Ethereum research forum, suggesting support for various approved proof sizes to allow smaller proofs for small-scale aggregation. He implemented heterogeneous recursion in the Paranoid system, which has been running both large and small state transition proofs on the public mainnet.The scheme uses a limited set of authenticated validator libraries, processing cross-class delayed validation through independent accumulator channels for each class to ensure the correctness of matrix claims in the recursive steps. When applying this mechanism to EIP-8288, discussions are needed on how to merge subclass libraries, handle dependencies, and address semantic compatibility issues between program identities and validator classes. EIP-8288 was proposed by Vitalik Buterin and Thomas Coratger in June 2026, primarily addressing the issues of large post-quantum signatures and STARK proof sizes, as well as high on-chain verification costs.

According to information from GitHub, a core protocol draft named "Decoupled Consensus" has appeared in the Ethereum EIP repository. It proposes to separate the beacon chain's head voting from the finality proof voting to enhance fork choice security, shorten finality time, and lay the groundwork for a subsequent transition to post-quantum cryptography (PQ).The proposal is co-authored by Francesco D'Amato, Roberto Saltini, Yann Vonlanthen, Mikhail Kalinin, and Ben Edgington, and is currently still in the early draft stage, with multiple details yet to be determined. The submitters primarily hope to obtain an EIP number at this stage. The proposal is pending further review and has not yet been merged.

Vitalik Buterin (@VitalikButerin) posted that the ideal path for supporting various cryptographic algorithms is through EIP-8288: users generate arbitrary signatures locally, then prove them through STARK, and aggregate them on-chain via STARK, without occupying calldata on-chain, thus Ethereum does not need to add new precompiles. He also mentioned that if lattice cryptography is proven to have security against AI attacks, it can still be used in scenarios such as accounts and wallets through precompiles in the future.Previously, Starknet co-founder Eli Ben-Sasson expressed disagreement with a16z's related views, stating that lattice cryptography has a rich mathematical structure that is vulnerable to AI attacks, and that a simplified version based on modular SIS only appeared in 2012 and lacks maturity. He suggested waiting another 3-5 years until AI has been thoroughly tested before using it for custody of large assets.

Ethereum contributor Francesco Risitano (@frisitano) submitted the draft proposal EIP-8440 (Proof of Execution Chain). This proposal proves the legitimacy of all execution payloads from the head beacon block to the origin beacon block through a recursive zero-knowledge proof mechanism, binding it to the beacon chain.Nodes can establish complete execution validity from a weak subjectivity checkpoint to the latest block header with a single proof, achieving constant time chain synchronization.

EIP-8363 co-sponsor Jérôme de Tychey announced the withdrawal of the application to include the proposal in the Hegotá hard fork, and the discussion on the related issuance policy will shift to an independent topic.

The Salvadoran government is collaborating with Modveon to develop a government-supported application called Sivar, allowing the public to send, receive, and hold dollar-pegged stablecoins through Coinbase's Base network, and supporting remittances. The application will verify user identities through government-issued identification.

According to Ethlabs, the Ethereum community is advancing the "Quick Slots" proposal (EIP-8198), which plans to remove the assumption of a fixed 12-second block time by restructuring once and first reducing the L1 block time from 12 seconds to 10 seconds, with further gradual reductions depending on network conditions.Ethlabs states that project teams such as DefiLlama, Doppler, Derive, Ondo, Railgun, Lido, Ethena, and infrastructure teams like Flashbots and Titan Builder generally believe that shorter slots will enhance DEX pricing efficiency, improve LP yields and user interaction experience, and strengthen transaction inclusion and censorship resistance when paired with FOCIL, while not significantly undermining geographic decentralization of nodes and the participation threshold for validators.

Arya.ag, an agricultural warehousing and loan company in India, is testing a system for tokenizing warehouse receipts for stored grains on the Avalanche dedicated Layer 1 blockchain. Arya.ag is collaborating with Finternet to connect grain storage, warehouse receipts, collateral commitments, and loan statuses through this network. Devika Mittal, head of Ava Labs India, stated that the testing is underway, with each tokenized warehouse receipt representing ownership of the stored goods.Sanmesh Kalyanpur, a director at Finternet Labs, mentioned that Arya.ag's samplers collect information on stored grains and input it into the company portal. Finternet will integrate farmers, commodities, warehouses, and insurance information into a "composite token" for banks to assess collateral risks. Arya.ag stores approximately $2 billion worth of agricultural products in its warehouse network and supports loans of about 120 billion Indian Rupees (approximately $1.26 billion) annually, with its loan department, Arya Dhan, disbursing around $230 million in loans each year.The concept of Finternet originated from a 2024 paper by the Bank for International Settlements (BIS), co-authored by Infosys co-founder Nandan Nilekani and then-BIS General Manager Agustín Carstens, proposing the establishment of an interconnected unified ledger for tokenized assets. In 2024, the Indian government launched a 10 billion Rupee credit guarantee scheme to encourage financing against electronic transferable warehouse receipts. The two companies have not disclosed the expected launch date or initial deployment scale.

The Ethereum Foundation (EF) stated that the Protocol Cluster has released two new articles that systematically assess the upcoming network upgrade Hegotá. Among them, the "Hegotá EIP Opinion Post and Tier List" evaluates and ranks the currently proposed 62 EIPs, marking the first time the team has published a unified EIP rating list for a major network upgrade.It was reported that approximately 60 researchers, engineers, and domain experts from 9 teams under the Protocol Cluster participated in the review, submitting a total of 397 rating opinions and engaging in live discussions on controversial proposals. The accompanying article outlines the current and future key directions of the Ethereum protocol layer, with one core goal being to promote Ethereum L1's quantum resistance by December 2029.The Ethereum Foundation indicated that the aforementioned upgrade plans, long-term commitments, and shared priorities at the cluster level provide the contextual basis for finalizing the scope of the Hegotá upgrade and the EIP ratings. Additionally, the Protocol Cluster will hold an AMA on September 16 at 14:00 UTC in the r/ethereum community on Reddit to discuss topics such as the Hegotá EIP ratings and key protocol developments.

Vitalik recently updated EIP-8141 "Frame Transaction" proposal, with core improvements including atomic batch execution of up to 64 operations, social recovery (similar to Google account recovery, without the need for a mnemonic phrase), P256 quantum-resistant signatures, and the ability for anyone to pay gas fees for users, significantly enhancing the usability of Ethereum wallets.It is reported that the improvement proposal was co-authored by Vitalik, lightclient, and 10 other experts, and is planned to be included in the 2027 Hegotá upgrade, marking a significant native implementation of Ethereum account abstraction.

Vitalik Buterin stated that recent discussions around transaction formats, including EIP-8141, the "future state" proposal, UTXO, PBT, key-controlled randomness, and recursive STARK memory pools, have helped the Ethereum community better understand the concepts of "actions" and "dependencies" in transactions. Dependencies can be processed in parallel, and some dependencies that do not require state access can be validated at the memory pool layer, potentially further compressing execution and data costs through STARK.Vitalik believes that Ethereum's future scalability needs to strike a balance between a dynamically flexible execution model and a more easily statically analyzable constrained model, providing lower gas costs for transactions and state access that can be statically analyzed. If EIP-8141 is designed properly, it will not only be a milestone achievement in a decade of account abstraction work but also prepare for decentralized-friendly large-scale scalability in the coming years.

Vitalik posted on the X platform, stating that recent research on transaction formats has led to a clearer understanding of "actions" and "dependencies" in Ethereum transactions, both of which can be optimized separately; signatures, UTXO's Merkle proofs, and ZK-SNARK or STARK belong to dependencies, while the call to send ETH belongs to actions.Dependencies can be processed in parallel, with state-related dependencies handled by the memory pool, while pure dependencies can be processed once at the memory pool layer and may be replaced by STARK proofs, thereby reducing execution and data processing. Vitalik pointed out that Ethereum's current scaling strategy needs to clearly distinguish between dynamic flexibility and static analyzability, with the latter achieving lower Gas costs; based on transaction volume, over 90% of Ethereum activities do not require dynamic flexibility. The EIP-8141 transaction type is developing towards a universal and minimalist call list, with new state types, recursive STARK memory pools, and key-controlled nonces also belonging to this direction.

According to CoinDesk, Ethereum researchers have proposed rebuilding the validator deposit contract to support a new cryptographic system and ultimately stop accepting deposits protected by the existing BLS signatures. This proposal targets the deposit contract, aiming to add a switch that prevents the network from accepting the currently relied-upon signature format.Currently, the contract only accepts BLS keys because their exact size is hardcoded, while the new draft allows for different key sizes, with each deposit tagged by the cryptographic system used, where BLS receives a tag of zero, reserving space for future schemes.If the proposal is approved, it will initially operate with BLS deposits, while other schemes can be registered simultaneously. Future decisions may permanently disable new BLS deposits, at which point validators who have staked using BLS keys will not disappear, but new validators will not be able to join using this method. Ethereum will ultimately need to change separately to inform validators how to check new signatures. This is part of the migration for validators, while another part is already in progress—EIP-8141 framework transaction proposals will allow regular Ethereum accounts to change the cryptographic method for approving transactions without changing their address.The urgency stems from research released in March by Google's Quantum AI research department, which outlined five quantum attack paths against Ethereum, putting over $100 billion in assets at potential risk. The Ethereum Foundation is advancing core protocol changes with a target around 2029. Currently, the amount of ETH staked in Ethereum is approximately 42.4 million, valued at about $10.4 billion.

The Ethereum community has released a deposit contract EIP proposal that supports post-quantum computing. The proposal aims to introduce a new contract that supports variable-length public keys and credential metadata, along with a clear scheme identifier, where scheme 0 is reserved for the current BLS deposits.The new contract no longer relies on the Merkle tree structure of the old deposit contract but instead passes deposit information to the consensus layer through execution requests derived from EIP-7685 logs. This contract features an irreversible mode controlled by protocol system calls: deposits are initially disabled, BLS deposits are enabled at a specified timestamp, and BLS deposits are permanently disabled at a later timestamp, with no option for re-enabling. During the migration period, the execution client must merge deposit requests from the new and old contracts.

Ethereum developer kevaundray submitted the EIP-12188 proposal, suggesting to shorten the consensus layer block retention window to reduce storage pressure on nodes. The proposal is currently in the public review stage and has received support from some Ethereum client developers.Developer DApplion expressed support for the proposal, while Lighthouse client contributor michaelsproul believes that this adjustment will not significantly impact Lighthouse's operation. The proposal points out that as the demand for Ethereum historical data changes, reducing the retention time for historical blocks in the consensus layer can optimize node resource usage.It was mentioned in the discussion that historical data pruning in the execution layer may affect some long-running nodes' ability to provide old block data, but developers believe this will not threaten network security or the normal operation of nodes. Currently, EIP-12188 has not yet been merged and still requires further review and community discussion.