• 5 mins read
  • Published

EIP-8361 Could Streamline Ethereum Mempool Validation With Proofs

Guido Molinari Blockchain economics and tokenomics writer EgonCoin

Post by Guido Molinari

EIP-8361 Could Streamline Ethereum Mempool Validation With Proofs EgonCoin © egoncoin.com
EIP-8361 Could Streamline Ethereum Mempool Validation With Proofs © egoncoin.com

A new Ethereum proposal, EIP-8361, aims to reduce node workload by letting certain transactions carry cryptographic proofs for mempool admission, potentially enabling more complex account logic without slowing network propagation

Ethereum developers are considering a proposal that could change how transactions are admitted to the network's public mempool. EIP-8361, known as Transaction Validity Proofs, would allow certain programmable transactions to include a succinct cryptographic proof-specifically, a STARK-that demonstrates their validation logic has approved the transaction. This approach could reduce the computational burden on nodes, which currently must simulate complex validation logic for each incoming transaction before relaying it to peers.

Reducing Node Workload

Under the current system, Ethereum nodes do not automatically relay every transaction they receive. Instead, each node runs a series of checks to ensure a transaction is valid and not excessively expensive before adding it to the local mempool. For transactions using EIP-8141 frames, which enable more expressive programmable account logic, these checks can require significant computation. When such transactions are broadcast across the network, the same validation work is repeated by every node, increasing overall resource consumption.

EIP-8361 proposes that eligible transactions carry a STARK proof generated off-chain, attesting that the programmable validation logic has returned an "approve" result. Nodes could then verify the proof and its underlying assumptions, rather than re-executing the full validation logic themselves. This would not replace on-chain execution-transactions would still be executed normally if included in a block-but it could make mempool admission more efficient and predictable for complex transactions.

Implications for Transaction Propagation

If proof verification is less resource-intensive than repeated simulation, EIP-8361 could enable transactions with richer validation logic to propagate more easily across the network. The proposal also discusses removing the MAX_VERIFY_GAS constraint for proof-carrying transactions, potentially allowing more complex schemes to access the public mempool while maintaining protections against spam and abuse. However, proof verification still consumes resources, and the validity of assumptions can become outdated if network conditions change. Mempool admission remains separate from block inclusion-validators and builders will continue to prioritize transactions based on fees, demand, and extractable value.

Confusion has arisen because some sources have linked EIP-8361 to staking and issuance changes, but those belong to a separate proposal, EIP-8363. During its submission in August 2026, the Tapered Issuance Burn draft was temporarily labeled as EIP-8361 before Ethereum editors reassigned it. As a result, some older articles and platform summaries still reference staking ratios, validator reward burns, and the 60.25 million ETH threshold under the EIP-8361 keyword. For clarity, EIP-8361 addresses mempool admission via transaction validity proofs, while EIP-8363 covers changes to validator issuance economics.

Risks, Limitations, and Numbering Confusion

EIP-8361 remains a draft and has not been implemented on mainnet. Its effectiveness depends on secure proof verification, accurate handling of assumptions, and robust implementation. While the proposal aims to reduce duplicated computation, it does not eliminate all networking overhead. A valid admission proof does not guarantee block inclusion, and transaction ordering will still depend on network fees and builder strategies. Additionally, the history of EIP numbering has led to persistent confusion in search results and social media, with some users mistakenly associating staking and issuance mechanics with EIP-8361. Users should consult the current Ethereum Improvement Proposal records to verify which proposal covers which topic.

As Ethereum continues to evolve, protocol changes like EIP-8361 could have a measurable impact on network efficiency. According to data from Beaconcha.in, the Ethereum mainnet processed over 1.2 million transactions per day in June 2026, with average gas fees fluctuating between $1.50 and $3.00 depending on network congestion. Reducing duplicated validation work could help nodes handle higher transaction volumes without increasing hardware requirements, especially as programmable account logic becomes more common.

For readers interested in how protocol-level changes can affect network activity and transaction throughput, EgonCoin previously covered the rapid growth of agentic payments on the XRP Ledger, which surpassed 1 million transactions and could reach 100 million as on-chain automation expands. See the analysis at this report on XRP Ledger agentic payments for a comparison of how different networks are adapting to new transaction types.

Programmable validation logic is a key feature of Ethereum's account abstraction efforts, allowing users and developers to define custom rules for transaction approval, fee payment, and authorization. While this flexibility can enable new applications and user experiences, it also increases the complexity of transaction validation and network propagation. EIP-8361's proof-based approach is designed to address these challenges by shifting expensive computation off-chain and standardizing how nodes verify transaction eligibility for the mempool. As with any protocol change, the trade-offs between efficiency, security, and decentralization will be closely scrutinized by the Ethereum community before any mainnet deployment.

Related articles