New Starknet version offers ‘unprecedented increase in capacity,’ co-founder says

Version 12 is expected to solve the major problems of the current Alpha and meet surge in demand

article-image

Creativa Images/Shutterstock modified by Blockworks

share

Starknet, the zero-knowledge rollup solution from Starkware, is readying a major upgrade. According to the company, thanks to the update, throughput — or transactions-per-second (TPS) — is expected to surpass not only Ethereum mainnet, but also all other existing layer-2s.

The version 12 upgrade, currently on testnet, is set to resolve a bottleneck of the current alpha deployment of Starknet — its sequencer.

In Ethereum’s rollup-centric scaling roadmap, there are two main varieties: Optimistic and zk (or validity) rollups.

Sequencers are common to both, but in the case of zk-rollups they process transactions before sending them to a prover, which generates the validity proofs that are passed on to Ethereum mainnet and underpin the rollup’s security.

Starkware President Eli Ben-Sasson likens the upgrade to that of an air intake pipe for an engine that turned out to be too narrow, preventing Starknet’s prized prover from performing at full capacity.

“The core innovation, the core engine is working at very high capacity, it was clogged…and now we’re replacing it,” Ben-Sasson told Blockworks.

Starknet’s sequencer was previously written in the Python programming language, but the new version replacing it was written in Rust, a more modern language which Ben-Sasson said makes it much faster — with the upgrade overall like going from the Wright Flyer to the Airbus A380.

Among general purpose zk-rollups currently available to the public, the top two in terms of activity are zkSync and Starknet, according to L2Beat. But they use two different proving systems: SNARKs and STARKs

Ben-Sasson, who co-invented STARKs, the technology upon which Starkware the company was built, points to several advantages of this prover: It doesn’t require a trusted setup, has built-in quantum computing resistance and — most important for scaling Ethereum — STARK-based provers are faster “by several orders of magnitude for the same payload,” he said.

That speed boost is why the Starkware community has adopted a nickname for the upgrade: “More TPS daddy” for which a signaling vote on Snapshot concludes Wednesday, with 87% in favor at press time.

The vote is open to delegates or holders of the Starknet token, STRK, which is not yet transferable or tradable, but has governance as its first of three utility functions. As the project decentralizes, the token will also be used to pay for fees on Starknet and be required for staking to run a sequencer or prover, using the project’s open-source code.

“So far everything that we open source, we always open source under an Apache 2.0 license, which I think is considered fully open source for all,” Ben-Sasson said.
That includes the smart contracts, programs written in Cairo — Starkware’s home-grown smart contract language — and Cairo’s compiler toolchain, but not yet the prover which Ben-Sasson said will be released under the same Apache 2.0 permissive license during “the decentralization phase” within about a year.

Starknet, the zero-knowledge rollup solution from Starkware, is readying a major upgrade. According to the company, thanks to the update, throughput — or transactions-per-second (TPS) — is expected to surpass not only Ethereum mainnet, but also all other existing layer-2s.

The version 12 upgrade, currently on testnet, is set to resolve a bottleneck of the current alpha deployment of Starknet — its sequencer.

In Ethereum’s rollup-centric scaling roadmap, there are two main varieties: Optimistic and zk (or validity) rollups.

Sequencers are common to both, but in the case of zk-rollups they process transactions before sending them to a prover, which generates the validity proofs that are passed on to Ethereum mainnet and underpin the rollup’s security.

Starkware President Eli Ben-Sasson likens the upgrade to that of an air intake pipe for an engine that turned out to be too narrow, preventing Starknet’s prized prover from performing at full capacity.

“The core innovation, the core engine is working at very high capacity, it was clogged…and now we’re replacing it,” Ben-Sasson told Blockworks.

Starknet’s sequencer was previously written in the Python programming language, but the new version replacing it was written in Rust, a more modern language which Ben-Sasson said makes it much faster — with the upgrade overall like going from the Wright Flyer to the Airbus A380.

Among general purpose zk-rollups currently available to the public, the top two in terms of activity are zkSync and Starknet, according to L2Beat. But they use two different proving systems: SNARKs and STARKs

Ben-Sasson, who co-invented STARKs, the technology upon which Starkware the company was built, points to several advantages of this prover: It doesn’t require a trusted setup, has built-in quantum computing resistance and — most important for scaling Ethereum — STARK-based provers are faster “by several orders of magnitude for the same payload,” he said.

That speed boost is why the Starkware community has adopted a nickname for the upgrade: “More TPS daddy” for which a signaling vote on Snapshot concludes Wednesday, with 87% in favor at press time.

The vote is open to delegates or holders of the Starknet token, STRK, which is not yet transferable or tradable, but has governance as its first of three utility functions. As the project decentralizes, the token will also be used to pay for fees on Starknet and be required for staking to run a sequencer or prover, using the project’s open-source code.

“So far everything that we open source, we always open source under an Apache 2.0 license, which I think is considered fully open source for all,” Ben-Sasson said.

That includes the smart contracts, programs written in Cairo — Starkware’s home-grown smart contract language — and Cairo’s compiler toolchain, but not yet the prover which Ben-Sasson said will be released under the same Apache 2.0 permissive license during “the decentralization phase” within about a year.


Start your day with top crypto insights from David Canellis and Katherine Ross. Subscribe to the Empire newsletter.

Explore the growing intersection between crypto, macroeconomics, policy and finance with Ben Strack, Casey Wagner and Felix Jauvin. Subscribe to the Forward Guidance newsletter.

Get alpha directly in your inbox with the 0xResearch newsletter — market highlights, charts, degen trade ideas, governance updates, and more.

The Lightspeed newsletter is all things Solana, in your inbox, every day. Subscribe to daily Solana news from Jack Kubinec and Jeff Albus.

Tags

Upcoming Events

Javits Center North | 445 11th Ave

Tues - Thurs, March 18 - 20, 2025

Blockworks’ Digital Asset Summit (DAS) will feature conversations between the builders, allocators, and legislators who will shape the trajectory of the digital asset ecosystem in the US and abroad.

Brooklyn, NY

TUES - THURS, JUNE 24 - 26, 2025

Permissionless IV serves as the definitive gathering for crypto’s technical founders, developers, and builders to come together and create the future.If you’re ready to shape the future of crypto, Permissionless IV is where it happens.

recent research

Research Report Templates.png

Research

An overview of the Base Ecosystem, with a focus on market leaders.

article-image

Although bitcoin hitting $120k by year’s end is looking unlikely

article-image

About 270 million HYPE has been claimed, valued around $7.6 billion

article-image

Stanford professors David Mazières and Dan Boneh will lead the lab alongside a cohort of graduate student researchers

article-image

With more companies holding BTC, bitcoin yielding strategies could become “a new corporate finance norm,” CoinShares posed

article-image

The proposal comes after Polygon governance considered a controversial use of bridged liquidity for yield

article-image

Can the community balance its decentralized ethos with the need for inclusivity and constructive debate?