Vitalik Buterin Proposes Recursive STARKs for Ethereums

Zusammenfassung:Ethereum co-founder Vitalik Buterin has proposed a new system that could change how the network processes transactions as it prepares for its planned

Ethereum co-founder Vitalik Buterin has proposed a new system that could change how the network processes transactions as it prepares for its planned I-Star upgrade.

Buterin outlined EIP-8288, which would use recursive STARK proofs to bundle transaction-related work and reduce computation handled directly by Ethereum‘s mainnet. He said the proposal could follow Hegota and build on Ethereum’s Frame Transactions.

A note on recursive STARK mempools (EIP-8288) https://t.co/KGUHKCcFqf

This is an EIP that I am hoping we can get included in I-star (the fork after Hegota) that you can think of as the next step after Frames, that would unlock extreme amounts of power. Particularly:

*…

— vitalik.eth (@VitalikButerin) September 9, 2026

Recursive STARKs Could Cut Costs

The system would let Ethereum nodes group transaction computations into recursive STARK proofs, shifting much of the processing away from the main execution path.

Related: Ethereum Price Prediction: Can ETH Clear $2,600 as Institutional Buying Continues?

Buterin said the approach could lower the cost of quantum-resistant signatures while supporting private transactions and account abstraction. Developers could also add new signature systems without modifying the Ethereum Virtual Machine.

This framework could allow systems such as Falcon and ML-DSA to operate alongside Ethereum as the network prepares for cryptographic changes.

Ethereum Could Adopt RISC-V

Under the proposal, nodes would group transaction data before producing recursive proofs. Each node could broadcast a STARK proof every 500 milliseconds. Buterin estimated proofs would range from 100 to 300 kilobytes, while each verified statement would add about 96 bytes to Ethereums blockchain.

The system could also support private account-ownership changes. However, Ethereum would need a common programming language for recursive STARKs.

Buterin identified RISC-V as the leading candidate, leaving developers to resolve a key architectural choice before adoption.

Haftungsausschluss

Die Ansichten in diesem Artikel stellen nur die persönlichen Ansichten des Autors dar und stellen keine Anlageberatung der Plattform dar. Diese Plattform übernimmt keine Garantie für die Richtigkeit, Vollständigkeit und Aktualität der Artikelinformationen und haftet auch nicht für Verluste, die durch die Nutzung oder das Vertrauen der Artikelinformationen verursacht werden.
Letzter Artikel

DoubleZero fügt Wahrscheinlichkeitsmarktdaten zu den US-Zwischenwahlen von Kalshi hinzu

Nächste

Trezor meldet weiteren Sicherheitsvorfall: Was Sie wissen sollten