Been following the Ethereum roadmap pretty closely, and there's something brewing that doesn't get enough attention. The Hegota upgrade coming later this year is shaping up to be way more significant than most people realize, especially with what 7805 is actually trying to accomplish.



So here's what's interesting: right now, a handful of block builders basically control transaction ordering on Ethereum. They decide what gets included and what doesn't. It's efficient, sure, but it's also a single point of failure. If a builder wants to exclude your transaction—maybe because of regulatory pressure, maybe for competitive reasons—there's not much you can do about it. We saw this play out with Tornado Cash transactions getting filtered out.

FOCIL, the formal name being EIP-7805, is Ethereum's answer to this problem. Instead of trusting builders to do the right thing, the protocol itself is going to enforce inclusion. The way it works is pretty elegant: in each block slot, the network randomly selects multiple validators to create inclusion lists. If a builder tries to ignore these lists, the network's fork-choice rule essentially rejects their block. It's not a suggestion anymore—it's hardwired into the consensus layer.

What makes 7805 different from previous attempts is that it's fork-choice enforced. You can't game it. The redundancy is built in too—up to 17 validators contributing to each inclusion list, so even if some go offline or try to censor, one honest actor is enough to force transactions through.

Vitalik's mentioned that this works best when paired with other upgrades like 8141, which brings native account abstraction and better privacy protocol support. Together they're basically saying: your transaction gets in, period. Whether you're using a privacy tool, running a complex DeFi strategy, or relying on gas sponsorship—doesn't matter. The inclusion guarantee is the same.

But here's where it gets politically charged. Some validators and institutions are genuinely worried about the legal implications. If you're running a node in the US and the protocol forces you to include transactions tied to sanctioned addresses, what happens then? It's not theoretical—some developers like Ameen Soleimani have raised serious concerns that this could create a 'legal chilling effect' where institutions just stop running nodes altogether.

The pro-neutrality crowd, including Layer 2 developers like Tim Clancy, counter that Ethereum's entire value proposition is being permissionless. If the network can be censored at the protocol level, it's not really a global settlement layer anymore. They argue that 'valid' should only be defined by code—enough gas, valid signature, that's it. Your identity or where your money's going shouldn't matter.

For regular users, this is actually pretty meaningful. If you've ever had a transaction delayed or stuck because of builder filtering, that goes away. With 7805 enforced, you're looking at inclusion within one or two slots—roughly 12 to 24 seconds. No gatekeeping, no delays. Just predictable, reliable blockspace.

The bigger picture here is that Ethereum's basically completing what they call the 'Holy Trinity of Censorship Resistance.' You've got Glamsterdam handling Proposer-Builder Separation coming first, then Hegota with 7805 locking in the inclusion guarantees. It's a multi-year strategy to shift the network from relying on social norms to actual protocol guarantees.

Will it be controversial? Absolutely. The regulatory debate is going to be intense. But from a technical standpoint, 7805 is solving a real problem that's been lurking in Ethereum's architecture for years. Whether institutions embrace it or start looking elsewhere—that's the real question heading into 2026.
ETH-0.64%
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments
  • Pin