Hegota bundles four key protocol-level proposals that together eliminate relay reliance, harden censorship resistance, and embed privacy at the base layer.
Fork-Choice Enforced Inclusion Lists, or FOCIL, is the consensus-layer headliner for Hegota . It mandates that all valid transactions included on an inclusion list must be placed into a block, preventing individual validators or builders from censoring specific transactions. Up to 17 randomly selected participants per slot can each submit an inclusion list; if a valid transaction appears on at least one list, the block builder must include it. Blocks that ignore valid inclusion lists are rejected by the fork-choice rule, making it practically impossible for any single actor to block a transaction
. This is a direct counter to scenarios where builder-validator separation has concentrated block construction in a handful of relays that could be pressured to filter transactions
.
EIP-8141 makes smart contract wallets—often called smart accounts—full first-class participants in the network, enabling them to send transactions directly without needing a relay intermediary . It builds on the account abstraction groundwork of EIP-7701 and extends those abilities so that smart wallet operations can be included in the public mempool
. When combined with FOCIL, a smart wallet transaction can reach a block by being picked up by one of the 17 randomly selected includers and then enforced through FOCIL's inclusion guarantees. The net effect is that “transactions from smart wallets will be able to enter the public mempool and be picked up by FOCIL on an equal basis with regular transactions,” according to Buterin
.
EIP-7701 is an account abstraction improvement specifically designed to let privacy protocols operate natively without depending on external relays or public broadcasters . It divides Ethereum transactions into distinct phases, allowing third parties to step in and pay fees at the appropriate phase without needing a dedicated relay service to accept and forward users' private transactions
. This removes a structural point where a relay could censor or even de-anonymize a transaction, and it simplifies the development and maintenance of privacy-preserving applications
. Buterin has called EIP-7701 an essential piece of a maximally simple L1 privacy roadmap
.
Drafted by Facet co-founder Tom Lehman in March 2026 and proposed for inclusion in Hegota, EIP-8182 embeds a shared shielded pool directly into Ethereum's base layer via a system contract deployed at a fixed address . The design uses a UTXO-based structure with no admin key, no proxy, no pause mechanism, and no governance token—changes can only happen through hard forks
. Transaction validity is verified using Groth16 BN254 zero-knowledge proofs
. The goal is to unify privacy under Ethereum's own trust model rather than force users into fragmented application-layer solutions with tiny anonymity sets
. Wallets and applications would share a single shielded pool, allowing private transfers to any Ethereum address or ENS name without requiring a separate privacy-specific address format
.
The relay dependency Buterin identified is not a theoretical edge case: it's the result of real tradeoffs where convenience and user experience were prioritized over trustlessness, and where the maturation of builder-validator separation concentrated block construction in a few centralized services . Hegota attacks this from multiple angles simultaneously. FOCIL guarantees that transactions can't be silently dropped by a hostile proposer. EIP-8141 and EIP-7701 ensure that smart wallets and privacy protocols can reach the public mempool and FOCIL's inclusion mechanism without routing through a trusted third party
. EIP-8182 goes a step further by making private transfers a built-in protocol feature rather than something that has to be bolted on externally through relay-dependent middleware
. The result, if delivered as planned in the Hegota hard fork, is a base layer where transactions from any kind of account are treated equally, censorship resistance is structurally enforced, and privacy is native rather than optional.
Comments
0 comments