Ethereum Research post proposes capacity limits that respond to load

What the post proposes

A post published on Ethereum Research on 11 November 2026 argues that Ethereum should treat elasticity, meaning the ability to shrink and grow its capacity, as a design principle. The author states that the text is an opinion piece setting out a possible direction rather than a finished design.

Ethereum's throughput is decided ahead of time, according to the post: a gas limit, a size limit, a fixed slot duration and one block per slot. Price moves demand toward that ceiling, and safety margins are held back to protect the network. The post says no rule at the protocol level adjusts those limits in response to measured resource pressure.

Robustness first, scaling second

The author frames elasticity as a robustness property before a scaling one. A system that measures what it can carry, and accepts less when it falls behind, is the kind that avoids congestion collapse, the post argues, and Ethereum's overload incidents resemble that failure mode.

Scaling follows from the same idea, according to the post: a network able to back off can run nearer to what its nodes and links can bear, while a fixed margin has to cover peak conditions at all times.

TCP as the reference point

The post points to TCP, the transport protocol that carries most internet traffic, whose congestion control was built to stop collapses. The author writes that the same mechanism, with small modifications, is part of why TCP runs on both modems and fibre links.

What is not settled

The post says it also looks at the mempool (the pool of transactions waiting to be included) and the unfinalized available chain. It offers no specification, and the excerpt available describes no implementation, timeline or governance route.

Whether client teams or other Ethereum researchers back the direction is not stated in the material available.