Ethereum researchers have proposed prioritizing two transaction changes for the 2027 Hegotá upgrade that could let privacy pools pay network fees without third-party intermediaries. Summary Frame Transactions would give wallets more control over transaction validation, execution, and fee payment. FOCIL would make it harder for block builders to exclude eligible privacy transactions. 66 proposals remain under consideration, while FOCIL is the only confirmed Hegotá feature. Ethereum developers are targeting 2027 for Hegotá after the Glamsterdam upgrade ships in 2026. Ethereum Foundation researcher Toni Wahrstätter said in an Aug. 17 X post that the Protocol Architecture team wants developers to prioritize Frame Transactions, listed as EIP-8141, and Fork-Choice Enforced Inclusion Lists, known as FOCIL or EIP-7805. Hegotá is taking shape, and we’ve published the Protocol Architecture team’s view on what should go into the fork:Check it out here:https://t.co/W1lfX3GZC3The short version: FOCIL is the right headliner, and we think Frame Transactions should join it as the headliner on the…— Toni Wahrstätter ⟠ (@nero_eth) August 17, 2026 Ethereum privacy pools could pay their own fees Frame Transactions would introduce a programmable transaction format that gives wallets more control over validation, execution, and gas payments. Wahrstätter described frames as a “much more expressive transaction format” and a key part of Ethereum’s planned transaction experience. Under the proposal, transaction logic would be divided into programmable frames instead of relying on Ethereum’s current fixed transaction structure. Wallets and applications could use the format for gas sponsorship, alternative signature systems, key rotation, and other forms of account abstraction. For privacy pools, the fee-payment feature could remove the need for a separate relayer to submit a transaction and pay its gas. Relayers can create another point where transaction details, wallet behavior, or network information may become visible to an outside service. “Together with Frames, these enable privacy pools where the pool itself can pay fees, removing the need for intermediaries,” Wahrstätter said. “Add FOCIL support, and privacy transactions also gain protocol-level inclusion guarantees.” Frame Transactions would work with Keyed Nonces and Recent Roots, listed as EIP-8272. Keyed Nonces would let an account maintain separate transaction sequences, while Recent Roots would allow a transaction to refer to a recent Ethereum state without relying on one fixed block reference. The proposed package also includes Transaction Assertions, or EIP-7906. According to Wahrstätter, assertions would let wallets define conditions that must remain true when a transaction is processed, giving users a way to limit what can happen after they sign and submit it. Earlier crypto.news coverage found that EIP-8141 remains under consideration rather than scheduled for Hegotá. Ethereum client teams are also comparing it with EIP-8130, another account-abstraction proposal, before deciding which design should move into implementation and testing. FOCIL would protect eligible transactions from censorship FOCIL is the only Ethereum Improvement Proposal currently scheduled for Hegotá. The design would allow a committee of validators to publish lists of transactions that block builders are expected to include. Attesters could reject a proposed block if its builder improperly left out eligible transactions from an inclusion list. Ethereum developers have presented the system as a way to protect transaction access as block production becomes more specialized and concentrated among large builders. Privacy transactions could benefit because users would not have to depend entirely on a block builder’s willingness to include them. FOCIL would not make transactions private on its own, but it would add a protocol process for resisting selective exclusion. Wahrstätter has argued that combining FOCIL with Frame Transactions, Keyed Nonces, and Recent Roots would give privacy pools both independent fee payment and stronger inclusion protection. His proposal represents a researcher’s preferred package, not a final decision by Ethereum’s core developers. Hegotá currently has 66 proposals under discussion, covering account abstraction, censorship resistance, transaction pricing, state growth, validator economics, and network scaling. The number does not mean all 66 features will ship, as most have not entered implementation, development networks, or public testnets. “A fork can’t be a wishlist by the community or core devs jamming on what Ethereum should eventually become,” Wahrstätter wrote in an earlier post. Developers instead need to decide which changes Ethereum should adopt next and which ones require more time, he added. US scrutiny has kept crypto privacy tools in focus For US users, the proposals concern how Ethereum processes private transactions rather than changing federal rules governing money transmission, sanctions, or illicit finance. American treatment of crypto privacy software has remained contested across Treasury actions and criminal cases involving mixing services. The US Treasury removed economic sanctions against Tornado Cash in March 2025 after reviewing the legal and policy questions raised by applying sanctions to technology-based financial activity. Treasury said at the time that it remained concerned about North Korean hackers and other illicit actors using digital assets. In a separate criminal case, a Manhattan jury convicted Tornado Cash co-founder Roman Storm in August 2025 of conspiring to operate an unlicensed money-transmitting business. Jurors did not reach verdicts on the money-laundering and sanctions charges, according to the reported split verdict. The US Justice Department said Tornado Cash had transmitted more than $1 billion in criminal proceeds, including funds connected to North Korea’s Lazarus Group. Storm’s defense maintained that the protocol operated through autonomous open-source software and that its developers did not control individual transactions. Ethereum’s proposed privacy pool design differs at the protocol level because Wahrstätter’s post deals with fee payment and transaction inclusion, not the legal structure or compliance systems of a specific application. Neither EIP-8141 nor EIP-7805 defines how privacy applications would handle US sanctions screening, money-transmission rules, or other compliance requirements. Hegotá follows Ethereum’s 2026 Glamsterdam upgrade Hegotá is scheduled to follow Glamsterdam, the Ethereum upgrade developers want to release before the end of 2026. A June upgrade report said Glamsterdam centers on Enshrined Proposer-Builder Separation and Block-Level Access Lists, alongside changes to the way Ethereum prices network resources. Enshrined Proposer-Builder Separation would bring the division between block proposers and builders into Ethereum’s protocol. Block-Level Access Lists would show which accounts and contract data a block needs, allowing clients to prepare data before execution and process some transactions in parallel. Hegotá candidates extend that work into privacy, censorship resistance, account abstraction, and state management. Scaling proposals under review include EIP-8368, which would adjust state-creation costs if Ethereum raises its gas limit beyond the level used for Glamsterdam. Developers are also studying separate access-list data, higher gas limits approaching 500 million to 600 million, and optional zero-knowledge Ethereum Virtual Machine proofs on the main network. Each proposal must compete for engineering resources, client support, testing time, and space within the 2027 release schedule. Privacy and quantum resistance also sit inside Ethereum’s multi-year technical plans. A July roadmap analysis reported that Vitalik Buterin’s Lean Ethereum plan calls for new cryptography, proof-based verification, redesigned storage, and native protocol privacy over the next three to four years. Execution client teams are due to submit their Hegotá preference lists by Sept. 10. Before then, developers plan to compare EIP-8141 with EIP-8130 during an Aug. 25 breakout meeting, with a decision on the competing account-abstraction designs targeted for the Aug. 27 All Core Developers Execution call.
