Mentioned in This Article
1. ETHGas Ethereum blockspace service targets Wall Street banks
ETHGas, a project built around trading Ethereum blockspace, is developing a service called Institutional Blockspace that would let banks and trading firms reserve room in upcoming blocks, choose which validators handle their transactions and screen counterparties for sanctions exposure. Founder Kevin Lepsoe confirmed that compensation for validators who miss their commitments is currently set to zero, and no bank has been identified as using the product in production.
The pitch is aimed at a specific frustration. Large financial institutions that settle sizeable amounts on a public blockchain want to know when a transaction will be confirmed, and ordinary Ethereum usage cannot promise that. ETHGas proposes to give that certainty without sending institutions to private chains, by selling advance commitments to include transactions in particular Ethereum blocks.
The proposal is notable as much for what it leaves unresolved as for what it offers. The mechanism that would make a reservation reliable, a financial consequence for a validator that fails to deliver, is not yet in force, and the pool of validators able to honor such commitments is small.
2. What is blockspace and why would a bank pay to reserve it?
Blockspace is the limited capacity inside each Ethereum block. Every block can only hold a certain amount of transaction data, so users compete for inclusion, usually by offering higher fees. A trader submitting an order during busy periods cannot be sure which block will carry it, or how quickly.
For a retail user, that uncertainty is an inconvenience. For an institutional trader moving large sums, timing can matter far more, because the value of a trade may depend on exactly when it settles. Reserving space in a specific upcoming block turns an open competition into something closer to a scheduled slot, which is how many traditional financial systems already handle large settlements.
The proposed arrangement also has a supply side. Validators, the participants who propose and attest to blocks, would gain another source of revenue by selling capacity ahead of time instead of waiting for fees to arrive transaction by transaction. That gives them a reason to join the service, which matters because the plan only works if enough of them take part.
Ethereum's design gives each block to one validator at a time, chosen from the active set. That proposer decides which pending transactions go in, and users generally have no say over who that will be. A reservation system effectively adds a pre-arranged contract between a transaction sender and a future proposer, something the base protocol does not provide on its own and which is the gap the service is trying to fill.
3. How would Institutional Blockspace work?
According to the project's description, Institutional Blockspace would let banks and trading firms do three things. They could select which validators process their transactions, screen counterparties against sanctions requirements, and reserve space in blocks that have not yet been produced. Throughout, transactions would continue to settle on Ethereum's public network rather than on a separate system.
That last point is central to the pitch. Lepsoe contrasts his approach with the alternative he says institutions often face, which is building separate permissioned layer-one or layer-two networks. A layer one is a base blockchain such as Ethereum itself, while a layer two is a network built on top of it. Permissioned versions restrict who can participate, and Lepsoe argues that creating many of them fragments liquidity across isolated systems. He said he would prefer to bring that capital onto Ethereum rather than see it build a walled garden elsewhere.
Lepsoe also stressed that the service is opt-in. It does not filter anyone else's activity, and every block still settles under Ethereum's normal consensus rules. In practice, that means a validator choosing to participate would honor reservations for institutional clients, while the rest of the network operates as it does today.
Sanctions screening is included because regulated institutions are bound by rules on who they may transact with. On a fully open network, a bank cannot easily control which counterparties interact with its transactions or which validators see them. Letting an institution restrict its dealings to screened counterparties and chosen validators addresses a compliance concern that has often kept banks from using public networks for larger flows.
4. What happens when a validator misses a commitment?
The central weakness identified in the arrangement is the absence of a penalty. Under the service as it stands, validators that fail to deliver on their commitments face no financial compensation requirement. Lepsoe said the compensation amount is currently set to zero and that there have been no major issues so far.
He argued that the mechanisms for pricing this risk already exist and that the market can set the right figure over time. That position treats the zero as a starting point rather than a permanent design choice, and it relies on the idea that participants will converge on a fair price once real usage begins.
For an institution, however, the practical meaning is straightforward. A reservation that carries no consequence for failure is a statement of intent rather than a guarantee. A bank that buys a slot to ensure a time-sensitive transaction lands in a given block would receive nothing if the chosen validator did not deliver. Whether banks accept that arrangement, or wait for a compensation schedule, is likely to determine how seriously the product is taken.
The same question applies to any service built on advance promises. Markets that sell guaranteed delivery usually attach a cost to failure, whether through deposits, collateral or refunds, because the price of the guarantee depends on what happens when it is broken. With compensation at zero, the service has not yet attached a price to that risk, and the market-setting process Lepsoe describes has little real usage to learn from.
5. How many validators can honor these reservations?
Availability is the second constraint. Lepsoe said qualified validators currently make up about 5% of Ethereum's network, and the goal is to raise that to between 20% and 30% or more by the end of the year. Because only qualified validators can fulfill reservations, the share directly limits how reliably a reserved slot can be served.
An October report by Delphi Digital examined the offering and modeled the effect. At 5% coverage, the expected wait for an eligible validator to propose a block is roughly four minutes, with a 23% chance that one will be available within a single minute. If coverage reached 30%, the average wait would fall to about 40 seconds.
Lepsoe acknowledged that these figures come from a model rather than live network data, but said the underlying logic holds: the smaller the qualified set, the longer the wait. For an institution that wants precise timing, a four-minute average wait is a substantial limitation, which explains why the project has set an ambitious target for validator participation.
The target of 20% to 30% or more by year-end implies a several-fold increase in a few months. Reaching it would require many more validators to meet the service's qualification standards and to opt in, and the report's modeled waits show why the number matters: the improvement from four minutes to about 40 seconds comes entirely from a larger pool of eligible proposers.
6. What do the commitment figures and the ether.fi deal show?
The Delphi Digital report also describes the commercial footprint of the service. It cites about $800 million in blockspace commitments, and a three-year agreement involving roughly $3 billion in ether from ether.fi that includes exclusive use of ETHGas's pre-confirmation platform. Pre-confirmation refers to a promise, made before a block is finalized, that a transaction will be included.
These numbers should be read with a clear caveat. Delphi's consulting arm produced the report under a paid agreement with ETHGas, so the analysis is not an independent assessment. The modeled wait times are likewise a projection, and the commitment totals are described in a report commissioned by the company itself rather than verified through separate disclosure.
That does not make the figures wrong, but it means the evidence for demand comes from the project and its commissioned research. The commitments cited are also not the same thing as banks using the product, a distinction that matters given what the report did not find.
7. Is any bank actually using it?
Neither Lepsoe nor the Delphi report identified a bank currently using Institutional Blockspace in production. The service is therefore best understood as an offering aimed at institutions rather than one they have adopted. The gap between the pitch and demonstrated use is the most important fact for anyone assessing the plan.
The idea itself reflects a broader tension in the market. Financial institutions want the settlement and liquidity benefits of public blockchains, but they also need predictable timing, compliance controls and clear accountability when something fails. Projects such as ETHGas are attempting to add those features as a layer on top of Ethereum, instead of asking institutions to give up the public network.
Whether that approach succeeds will depend on the two open points identified so far. Validators need a financial reason to stand behind their commitments, and enough of them need to qualify so that waits become short enough to be useful. Lepsoe has set a year-end target for validator coverage, which offers an early measure of progress. Until a bank is publicly confirmed as a customer and compensation moves above zero, the service remains a proposal with promising design goals and unproven institutional demand.