Starknet Post-Quantum L1 Poll Opens With 99.9% Voting Yes
Starknet post-quantum L1 poll: holders vote until October 22 on researching an independent L1. Early Snapshot results show 99.9% yes, with 20 votes at 98.5%.

In this article+
Starknet holders have started voting on whether the network should leave Ethereum's shelter. The poll asks if the Starknet post-quantum L1 idea deserves research, and early results lean almost entirely one way.

The Snapshot poll page with results at the time of capture. Source: Starknet governance.
How the Starknet post-quantum L1 poll works
The Snapshot vote opened at 09:32 UTC on October 15 and closes at the same time on October 22. It is non-binding. Voters pick one of three answers: yes, no, or neutral.
A yes means "research the Starknet post-quantum L1 further" and nothing more. The poll text says it is not approval of any move to an L1, and any real switch would need its own governance process. A forum thread by user henrli explains the plan and runs alongside the vote.
The forum post lists what a result would trigger. A yes starts a research effort that leads to more detailed proposals and polls. A no keeps the post-quantum work on the current L2 path. A neutral result keeps the thread open until the missing answers arrive.
Why StarkWare wants a post-quantum L1
The idea did not start in the forum. On October 8, StarkWare co-founder Eli Ben-Sasson asked on X whether a Starknet L1 for post-quantum agility was a good or bad idea. He pointed to the quantum threat and AI as the two things to watch.
Two days later, StarkWare posted that Starknet becoming an independent L1 is its clearest path forward. The forum post gives the security case. Parts of Starknet under its own control can become quantum-resistant soon, but the bridge and data availability follow Ethereum's timeline.

The forum post explaining the reasons and what each result triggers. Source: Starknet Community Forum.
The post also lists what stays fixed. STRK remains the token and no new token is planned. Bridges from Ethereum to Starknet stay open whatever the outcome, according to the thread.
Who cast the early Starknet L1 votes
The Snapshot page showed about 162.7 million STRK of voting power on yes and about 155,000 on no, which is a 99.9% split. By 12:34 UTC on October 15, 209 votes had arrived. Four of them chose no.
Those numbers need context. Twenty of those voters hold 98.5% of the voting power cast so far, and the biggest single vote is about a tenth of the total. Snapshot shows these as addresses, and the poll does not say who sits behind them.
So the count of voters and the weight of the votes tell different stories. Roughly 200 votes have come in, but a small group decides the percentage. With six days left, those shares can still move.
What it means for STRK
STRK traded near $0.0798 on CoinGecko at 12:35 UTC on October 15, with a market value around $594 million. TOCE tracked the price reaction when the idea first surfaced, in STRK doubling in three sessions.
A research effort could take a long time, and the forum post says no timeline exists. This article reports a governance poll. It does not forecast the token price or the final decision on a Starknet post-quantum L1.
Written by
Daniel Kiprop covers exchanges, listings, stablecoins and institutional crypto moves for Times of Crypto Era. Stories start from company filings and official announcements, not secondary coverage.
View full profile →Related News

INJ Price Analysis: A 15% Slide Tests The $7.00 Swing Low
INJ price analysis: Injective fell 15% from $8.456 after two failed sweeps of $8.326. Four-hour support near $6.999, an order block and two scenarios.

ZK Price Analysis: An 18x Volume Spike Fades From $0.0188
ZK price analysis: the ZKsync token gained 44% in a week and hit $0.0188 on 18x volume before fading. Four-hour levels, blocks and two scenarios with triggers.

ZEC Price Analysis: A 13.8% Slide Reaches The $1,086 Block
ZEC price analysis: Zcash fell 14% in 32 hours and closed under $1,112.77. Four-hour levels, a daily order block at $1,086.20 and two scenarios with triggers.