Ethereum Validators Live on Issuance While Data Companies Collect $1.1 Billion Off Their Chain. Take It Back.

You run an Ethereum validator. Across every chain, the revenue from reading blockchain data leaves the network that produced it, when it belongs to the validators and ecosystems that did. That is the general case. On Ethereum the numbers make it personal: the network you secure had its best year of activity on record, and you got poorer for it.

Your Fees Collapsed. Your Data Revenue Left. You Live on Issuance.

Look at what a year has done to Ethereum validator economics. Native staking yield has compressed to roughly 2.8% APR and is still falling as more ETH stakes. Since Dencun, execution-layer rewards, the fees and MEV you earn for the actual transactions, are only about 7% of total validator rewards. The other 93% is issuance. You are running on newly minted ETH, not on the economic activity of the chain.

And the activity is there. Ethereum L1 set transaction records through the end of 2025, more daily transactions than the 2021 peak. But L1 fee revenue fell more than 80% year over year even as usage hit all-time highs, because the value moved up the stack to rollups and the fees moved with it. The busier Ethereum gets, the less its base layer pays the validators securing it.

Here is what all that record activity produces that you are not paid for: data. Every one of those record transactions, on L1 and on every rollup settling to it, becomes a read someone pays for. The more Ethereum is used, the more read-layer revenue it generates. Your problem is where it goes.

$1.1 Billion a Year Walks Out the Door

We estimate Ethereum and its EVM rollups produce on the order of $1.1 billion in read-layer revenue a year, RPC and indexing spend combined, every dollar paid to Alchemy, Infura, or an indexer to read Ethereum or rollup state. That money is not circulating inside the ecosystem. It leaves, collected by companies that stake nothing, secure nothing, and answer to no one in the network.

Put it next to your own numbers. Your yield is 2.8% and falling. Your fee income is 7% of rewards and shrinking. And the one revenue stream that grows with Ethereum's actual usage, the reads generated by the record activity you finalize, is a billion-dollar business you have no position in. The validators and sequencers producing the most-settled state in the industry are the only parties in its data economy earning nothing from it.

Ethereum's Read Layer Runs Through One Company's Front Door

Infura, owned by Consensys, is the default backend for MetaMask. A large share of Ethereum reads flow through a single commercial provider that ships inside the wallet most of your ecosystem uses. The dependency you carry is not spread across a competitive field. It sits with one company, and that company books the revenue for serving data your validators produced. When it reprices, deprecates an endpoint, or gates access, Ethereum absorbs it, and you had no vote.

Sit with the irony of that. Ethereum ran the largest decentralization effort in the industry's history at the consensus layer, over a million validators, precisely so no single party could stand between the network and the people using it. Then the read layer put one there anyway, and it happened without a vote because it happened outside the protocol entirely.

Every Unverified Read Is an Attack Surface

If the concentration sounds like an abstract risk, the Kelp exploit priced it: roughly $292 million, and not through a smart contract bug. It was an RPC poisoning attack. The attackers compromised the RPC nodes feeding the bridge's verifier, swapped the node software for versions that served forged chain state, and knocked the clean nodes offline so the poisoned ones would answer. The verifier believed what its RPC endpoints told it, because that is all a standard RPC response offers: an answer with no proof attached. A fabricated view of Ethereum's state passed as truth, 116,500 unbacked rsETH walked out, lending markets froze, and DeFi shed some $13 billion in deposits in the panic that followed.

Understand what actually failed. The state you finalized was correct the entire time. Consensus never broke. What broke was the layer between your state and the application reading it, a serving layer that transmits answers without proofs and asks everyone downstream to trust the endpoint. And Kelp was not an anomaly. It was one instance of the condition the entire ecosystem reads through every day: every bridge, every wallet, every protocol consuming Ethereum state through an unverified endpoint carries the same exposure, and most of them share the same handful of endpoints.

Ethereum's own answer to that problem is the Ethereum light client effort, and the consensus-layer work is real: a light client can verify headers and check state against roots. But light clients still fetch their data from the same handful of RPC providers, so the availability dependency and the serving revenue concentrate exactly as before, and the proof coverage runs out where applications actually live, indexed views, event queries, historical data, the cross-chain views Kelp's verifier was consuming. Ethereum built verification at the consensus layer and never built the verifiable serving layer underneath it. Kelp is what the gap costs, and the companies collecting the $1.1 billion have no reason to close it. Unverifiable serving is the product they sell.

Collect From the Outside Instead

Shinzo is how Ethereum collects from the outside. It lets validators serve their chain's data at the source and capture the revenue for it, raw reads and structured views in one layer, with no separate provider underneath. Every builder who reads Ethereum through Shinzo instead of a centralized provider turns a dollar that was leaving into revenue for the operators who run the infrastructure, at no cost to the delegators whose ETH backs it.

Follow what that does to every problem above. Operators earning dollar revenue for serving reads are operators less dependent on a 2.8% yield, without the foundation lifting a finger and without a single delegator's return shaved. The read layer stops being a dependency on one company's front door and becomes a revenue stream distributed across the validator set that already secures the network. And the data carries proof back to the state you finalized, at the raw read and the indexed view alike, which is the piece the light-client effort has been missing and the piece that would have given Kelp's verifier something to check instead of someone to believe.

There is one more number worth naming: the one nobody can size yet. A provider can serve a hundred ecosystems and still sell a hundred silos, because every chain speaks its own format, and moving data between them, Ethereum state consumable on Solana, Base data readable from Ethereum, requires transformation that no serving infrastructure performs. So the $1.1 billion only counts the demand that can reach Ethereum's data in Ethereum's own format. Shinzo builds the transformation into the serving layer itself, making Ethereum's data consumable from every ecosystem without breaking its proofs, and provenance decides where the revenue settles: an application on any chain reading Ethereum state is an Ethereum read, and it pays back to Ethereum. The demand locked behind the format walls has never had infrastructure able to serve it, which means it has never been priced. The $1.1 billion is the floor.

Builders pay for verifiable Ethereum data on infrastructure whose earnings flow back into Ethereum, instead of funding the next round at a company with no stake in the outcome. And the funding question answers itself from repatriated revenue rather than from stakers' pockets: keep a fraction of that $1.1 billion inside the network, a floor that cross-ecosystem demand only raises, and the capacity exceeds anything a redirect could raise, without touching anyone's yield.

Even the Validator Redirected Revenue Debate Proves the Point

Watch what the extraction has done to the ecosystem's own conversation. The funding programs that sustained client teams have wound down, core development faces a gap estimated at $30 million a year, and the live answer on the research forum, a proposal called Validator Redirected Revenue, is to let validators signal away up to 10% of staking rewards, mandatory for all if a majority signals above zero. The pool it would raise: 50,000 to 70,000 ETH a year, roughly $120 million.

Hold the two numbers side by side. Ethereum is debating whether to tax its own stakers $120 million a year, off the gross reward stream, so delegators pay while operators decide, to close a $30 million gap, while roughly ten times that sum leaves the ecosystem annually through the read layer. The instinct to fund shared infrastructure is right. The pocket is wrong. An ecosystem reduced to arguing over slices of a compressed yield, while a billion dollars of its own output walks out the door uncontested, is an ecosystem that has stopped noticing what it gives away.

The Record Year Should Have Been Yours

Ethereum's best year of activity ever made its validators poorer, its data resellers richer, and left its applications trusting endpoints that the Kelp exploit proved can lie. That is not a market cycle. It is a structure, and structures hold only until someone builds the alternative. It is built.

You finalize the most valuable state in the industry. The revenue from reading it runs to ten figures a year, and your share has always been zero. Take it back.

Shinzo is the trustless data read layer for blockchains, powered by the validators who produce the data in the first place.

See what your chain is owed: X · Telegram · Discord · GitHub · Docs