BTC 
BNB 
XRP 
SOL 
TRX Vitalik Buterin argues most cryptography support should not go in precompiles or EVM
Vitalik Buterin argued that precompiles and the EVM are the wrong place for most cryptography support on Ethereum, because both operate on data that must be included in a block as calldata. He said that space is limited, citing a practical cap of about 8 MB/s even with PeerDAS and blocks-in-blobs. He proposed computing self-contained heavy computation client-side, STARKing it, and pushing the STARK through the EIP-8288 recursive aggregation mechanism.
Why “Confirmed”
- Published by a primary source: Vitalik Buterin
1 independent source group across 1 post · evidence score 90/100. How labels work
Market around the story
-
ETH
Still being measured. The price reaction is recorded six hours after the first report, around .
What the sources claim
-
Buterin says precompiles and the EVM are the wrong place for most cryptography support on Ethereum. ETH
“precompiles and EVM are both the wrong place to put most cryptography support into Ethereum”
Vitalik Buterin -
Buterin says precompiles and the EVM operate on data that must be included in a block as calldata. ETH
“precompiles and EVM both operate on data that has to be included into the ethereum chain somehow”
Vitalik Buterin -
Buterin says calldata space has a practical cap of about 8 MB/s even with PeerDAS and blocks-in-blobs. ETH
“there's a practical cap of ~8 MB/s before it starts getting uncomfortable”
Vitalik Buterin -
Buterin proposes computing self-contained heavy computation client-side, STARKing it, and pushing the STARK through EIP-8288 recursive aggregation. ETH
“compute it and STARK it client-side”
Vitalik Buterin
Sources
More on ETH
Summary and claims extracted by AI with prompt analyze-story@5 on 2026-10-19 04:10 UTC. Labels are computed from the sources, not by the model.