Ethlabs is arguing that Ethereum can move faster without tossing out decentralization, censorship resistance, or credible neutrality. And it wants EIP-8198 — Quick Slots — inside the Hegotá upgrade.
The pitch comes out of interviews with roughly 20 DeFi founders, app developers, and infrastructure researchers. After ten years of “Ethereum killer” talk and endless promises of a faster Ethereum, Ethereum mainnet and its L2s still account for the biggest DeFi arena around. As of Sept. 17, 2026, that stack held roughly $58 billion in total value locked, and spot DEX volume across layers had already gone past $750 billion this year.
Quick Slots starts with timing refactors, not an immediate hard cut
Right now, Ethereum produces a block every 12 seconds. Carl Beekhuizen wrote the EIP in March this year. Then on Aug. 6, Barnabé Monnot took it to All Core Devs in a push to get it into Hegotá, with Francesco D’Amato and a growing group of client and ecosystem teams helping drive it forward too.
The proposal comes in two parts. First, a bigger refactor strips out the hard-coded assumption in software that block time is always 12 seconds. Only once that exists would Ethereum actually start shortening slots, and only in line with what the network can safely handle. The first move being discussed is from 12 seconds to 10 seconds. Anything beyond that would need its own testing and its own consensus. Step by step.
That setup matters. Ethlabs is not calling for a single lunge to the shortest possible slot time. It is saying block time should become a parameter Ethereum can change safely. The article likens that to how capacity has been handled already: gas limits can climb when clients show more room, and blob capacity can be revisited as data handling gets better. Same idea here. In Ethlabs’ view, latency should be handled the same way.
Why supporters think shorter slots would improve Ethereum’s markets
Nobody in the piece is claiming Ethereum mainnet needs to turn into the fastest trading venue on earth. The point is narrower than that. As a secure, decentralized settlement layer for the global economy, it can be faster than it is now.
Ethlabs says the first effect is plain enough. Less waiting feels better. But the builders it interviewed linked shorter slots to market quality too. Ethereum mainnet is already a large market. Over the last 30 days, DEX volume on mainnet was about $41.25 billion. For a comparison point, the main exchange in Singapore logged about $33.9 billion in securities turnover in August 2026. So yes, the article argues that a somewhat faster protocol layer would make mainnet a more competitive global settlement venue.
Markets do not sit still between blocks. Prices move. Demand shifts. Quotes go stale while Ethereum waits for the next slot. Shorter slots mean on-chain liquidity updates more often, stale-quote windows get smaller, users have a better shot at execution, and market makers can quote in better conditions.
DefiLlama founder 0xngmi said faster slots would improve the experience for real-time routing aggregators such as LlamaSwap: “Quotes move less between blocks, so slippage can be set tighter.”
Austin Adams, founder of Doppler, which works on asset issuance and cold-start liquidity, looked at the same question from the LP side. He said: “Faster slots directly improve LP returns and also make capital markets more efficient. Shipping EIP-8198 quickly helps the network keep leading capital formation and trading.”
Josh Kim, head of engineering at options platform Derive, zeroed in on the risk arbitrageurs carry while waiting for an L1 transaction to land. That risk shapes how well they can rebalance markets and keep spreads tight. Derive V3 is set to deploy on Ethereum mainnet, and Kim said: “Large options orders often move the perpetuals and spot markets on our DEX. When arbitrageurs step in to rebalance, block speed directly determines the fees, slippage, and risk they have to take on. For example, if they go long spot and short perpetuals, they currently have to carry 12 seconds of spot settlement risk, which often means they only enter when prices have already moved a lot.”
Tokenized stocks and ETFs came up too. Ondo handles minting and redemptions through RFQ, with prices signed off-chain while the user transaction still has to settle on Ethereum. The underlying asset keeps trading during that gap. Shorter slots would lower the risk quote providers carry and leave room for tighter spreads. Armand Khatri, head of ecosystem at Ondo, said: “The market pricing tokenized stocks and ETFs never waits for Ethereum to produce a block. From the signed quote to transaction confirmation, every second means someone is carrying price risk, and that ends up showing in the spread. Shorter slots shrink that window and let on-chain pricing track off-chain reference prices more closely. That is a real improvement, and it does not consume the properties that make Ethereum worth settling on in the first place.”
Matthew, co-founder of Ethereum Institutional, said better market responsiveness would give institutions more reason to move activity on-chain. Haikane, founder of PropellerHeads, made much the same argument from the trading-business side, saying margins are already thin enough that even small latency gains matter and could make more firms willing to trade assets on L1.
ZoomerAnon, a contributor to Aerodrome, which is opening an instance on mainnet, also backed faster blocks. In that telling, quicker price updates mean less value leaking out to arbitrageurs and more trading staying inside on-chain pools. He said: “It is not in Ethereum’s interest for a big chunk of volume to run off to centralized market makers, and slow block production is part of the reason that happens. We can adapt to a new block time by changing parameters and swapping modules — no need to redeploy.”
Across all of those comments, the shared point is pretty simple: shorter blocks mean more frequent state updates, and that makes the mainnet market work better. Ethlabs says that if Ethereum can deliver fresher state without giving up decentralization, it should.
For users, the change shows up first as less waiting
Another set of users does not care what a slot is. They care whether an app feels slow. That’s it. TokenWorks’ FWA.fun recently became one of the biggest gas-consuming applications on mainnet, pulling in both new users and people who had not touched mainnet in a long time. Founder Adam said front ends can mask some of the wait, but users still hate waiting, and FWA’s use of Chainlink VRF adds another three block confirmations. If blocks get shorter, the entire wait gets shorter. Many users buy repeatedly and send transactions one after another, so every second shaved off matters.
Ethlabs also pointed to another piece of its broader fast-Ethereum workflow, FCR, which it said can cut confirmation time by about 30x and help on that same front.
Dan Lipert, a contributor to privacy protocol Railgun, said faster blocks could pull more liquidity onto L1 and expand privacy sets. He also said compliance tools would have more time to react in key windows, letting users use different applications privately without just sitting through passive delays.
The article draws a clean distinction between L2 and L1 jobs. L2s have already been tuned for faster interaction. L1 has a different assignment: be the safest, most credibly neutral, and most censorship-resistant settlement layer possible so those systems can rely on it. For builders trying to bring user-facing products closer to those properties, a faster mainnet would help right away.
Supporters also tie Quick Slots to censorship resistance
One reason people put transactions on decentralized chains is censorship resistance. If someone refuses to include your transaction, Ethereum should give you another route as fast as it can.
George Davies, head of engineering at Gattaca, which runs Titan Builder and currently produces about half of Ethereum blocks, called Quick Slots his top priority for the next consensus-layer EIP. He said: “This is the biggest user-experience unlock for DeFi users, and it also brings censorship-resistance and finality gains.��
For a censored user, block time is wait time. Simple as that. It decides how long it takes before another inclusion chance appears. Ethlabs says that matters even more when paired with FOCIL, the headline EIP in Hegotá. FOCIL gives a set of validators — called includers — extra transaction-inclusion duties. Quick Slots would make those opportunities show up more often. At 12 seconds per block, there are five chances per minute. At 10 seconds, there are six. In the article’s framing, FOCIL adds more doors for censored transactions, and Quick Slots makes those doors open more often.
Michael Mosier, head of research at Blockspace, stressed inclusion quality, saying shorter slots would make blockspace more predictable, stimulate user activity, and help the infrastructure serving the network. Patrick Apriori of Frachtis pushed the argument further, saying that with FOCIL alongside it, censorship would become more expensive, shorter-lived, and structurally harder to carry out.
The piece uses the phrase economic censorship resistance to describe how much it costs an adversary to keep a transaction off-chain over time. Shorter slots mean users wait less for the next inclusion chance. And if an adversary wants to maintain censorship over a fixed stretch of time, that adversary has to deal with more proposer opportunities. FOCIL adds includers into that process too.
Ethlabs’ broader argument is that performance and resilience often pull in opposite directions, but Quick Slots could push both the same way. A settlement layer for the world, in this view, should be hard to censor and quick to recover when someone tries.
The central condition: no tradeoff against decentralization
The article is blunt here. Faster blocks make sense only if decentralization is not the thing being sacrificed.
Flashbots has publicly looked at the issue and, according to the article, came out supportive of the direction. Its conclusion: shorter slots reduce confirmation latency and improve user experience, and slot time should become configurable so Ethereum can test shorter intervals one step at a time.
Its bigger worry is geographic decentralization. If slots get shorter, the time available in the block production pipeline gets tighter, and participants farther from network and infrastructure hubs could lose out. Still, the latency-calibrated simulations cited in the article suggest that the reduction currently under discussion is unlikely to create a material constraint. Even going from 12 seconds to 6 seconds would widen regional revenue gaps while leaving the overall geographic concentration result broadly unchanged. So in that reading, geography looks more like a cap on how far Ethereum can push slot times down later, not a blocker for the reduction now being discussed.
Ethlabs said it is also tracking node propagation times across the network, especially in light of post-quantum migration and the link between future consensus design, shorter slots, and larger quantum-resistant signatures.
Faster L1 timing would also help L2 coordination
L2s that rely on Ethereum inherit some of their timing from L1. The easiest example is deposits. Assets or messages moving from L1 into an L2 first need an L1 transaction included. If L1 blocks arrive sooner, that path finishes sooner too, whether or not the L2 uses Ethereum for sequencing.
For some interoperability designs, the upside is bigger. Armagan of Ethereum Economic Zone gave one example: EEZ is working on a design where a contract on one rollup can call a contract on another rollup and use the return value in the same transaction. That synchronous window opens at most once per L1 block, so a 12-second L1 clock becomes part of the cross-rollup user experience. He said: “L1 slot time sets the cadence for cross-chain composability; shorten the slot, and synchronous windows appear more often, while the worst-case wait until the next one gets shorter too. Quick Slots is a double win for EEZ: the first reduction already makes those windows noticeably denser, and once slot duration becomes adjustable, every further reduction supported by data will directly turn into faster cross-rollup composability for users.”
Ethlabs still describes L1 as a global settlement layer — secure enough and decentralized enough for assets, applications, and L2s to depend on it. Quick Slots is not supposed to make L2s unnecessary. The goal is to let mainnet get faster over time so both L1 and the broader L2 stack get stronger.
More voices from across the ecosystem
Greg Casegamas of Lido framed the issue around competitiveness. Faster slots are not essential to Lido’s core staking business, he said, but as a broader Ethereum and DeFi participant, the project supports anything that makes Ethereum stronger and more competitive, and would welcome an S-tier label for the proposal in Hegotá.
Ethena founder Guy Young was more direct: “DeFi works better with faster block production.” The article says Ethena has built on Ethereum since day one and clearly supports the proposal.
Noveleader, a researcher at Castle Labs, approached the issue through market microstructure. Compressing block times could reduce loss-versus-rebalancing for passive LPs, bring on-chain pricing closer to off-chain venues, improve capital efficiency, reduce toxic arbitrage leakage, and make liquidation windows in lending protocols timelier. But Castle Labs also wants testing to show that shorter slots do not make geographic dispersion and home validation harder by tightening propagation windows and quietly pushing stake toward better-connected data centers. It also wants to understand how shorter slots affect timing games and builder competition, since less time per slot makes latency and colocation advantages more valuable and could concentrate block production. On the ecosystem side, contracts and off-chain systems that use block height as a clock — including governance cycles, timelocks, and models that accrue interest based on annualized block counts — need a clear migration path before activation.
Omid Malekan, an adjunct professor at Columbia Business School, put his condition plainly: if decentralization is preserved, faster blocks are better for everything.
Nicolas of on-chain venture protocol Umia said faster slots would improve the mainnet experience and should be prioritized from a builder’s point of view.
Why backers want it in Hegotá
Every upgrade runs into limited engineering bandwidth. Ethlabs says the case for putting Quick Slots into Hegotá boils down to three lines: it helps the network, the engineering work can be reused, and the opening exists now.
Waiting has a price. The upgrade after Hegotá is currently referred to as I*, and it may include decoupled consensus, which separates block production from finality and already sits at the top of the Ethereum Foundation protocol roadmap. Barnabé’s point, as presented in the article, is that missing Hegotá does not mean Quick Slots just glides into the next fork. It could end up fighting for engineering resources against much larger consensus changes and then sit through several more upgrade cycles before a clean chance appears. That’s the risk.
Block time is also a network-wide constraint. Wallets can tweak loading animations. DEXs can tweak routing. But none of them can make the next mainnet block arrive earlier by themselves. If the protocol changes that constraint, every application and every user depending on L1 latency benefits at once, instead of each team building its own workaround. As user expectations climb, protocol-level latency improvements can stop more of that burden from being dumped onto applications.
Ethlabs also argues the engineering work compounds over time. A big part of the job is removing the assumption across specs and clients that Ethereum is stuck forever on a 12-second clock. Once that is finished, later reductions get easier as client performance and network conditions improve. Every cut would still need testing, coordination, and a network upgrade. But Ethereum would keep the reusable base. Capacity has already been pushed forward through a cycle of improve, measure, and improve again. Ethlabs says latency should follow the same pattern.
What has been done so far
Ethlabs places Quick Slots inside a broader fast-Ethereum workflow, but says it still needs the same kind of network-wide coordination as any other EIP. The Foundation’s protocol team has listed several areas where it wants more confidence: an agreed specification, implementations that match that specification, downstream impact assessments, and compatibility with decoupled consensus.
The article lists several pieces of current progress:
- The specification is being turned into working clients. With Francesco and Foundation contributors Justin Traglia and Jihoon Song, Barnabé has proposed a consensus spec covering timing changes and the upgrade transition. On Sept. 12, Terence reported that a Prysm prototype had been implemented against the working spec and tested locally with Kurtosis. Next up: align implementations across multiple clients and test the transition under more realistic network conditions.
- Teams are checking what is still hard-wired to 12 seconds today. Ethlabs and Sourcify are reviewing timing assumptions in deployed contracts and identifying migration paths where needed, including contracts that interact with historical beacon block roots. The article says the early assessment has already produced concrete code paths, not just a vague warning that things might break.
- The roadmap is also being aligned with later consensus work. Francesco and the Foundation’s finality team are reviewing the relationship between Quick Slots and decoupled consensus, since both directions assume faster block production in the future.
What still needs to happen
Ethereum upgrades touch hundreds of billions of dollars in value and have to ship without downtime. The stakeholder list is far too large to fit in one room. For an EIP to reach mainnet, it has to be proposed, specified, implemented, tested, checked for breakage, fixed, and tested again until the people responsible for shipping it are confident enough to include it in an upgrade.
Ethlabs says Quick Slots is on that road now. The next tasks are straightforward: merge the specification into main code, align implementations, test under network conditions, check downstream dependencies, and plan the next mechanism steps in the context of post-quantum migration. Its job, the group says, is to turn unknowns into implementation and migration plans so the proposal can legitimately enter Hegotá scope.
Ethlabs said it wants feedback from client maintainers, validators, infrastructure operators, and application teams that would benefit if mainnet gets faster. It also wants to hear about any constraints it may have missed.
The closing argument is simple. Decentralization and performance do not always need to be traded against each other. Sometimes Ethereum can ask for both. Ethlabs says this is one of those moments.