Starknet holders back research into becoming an independent post-quantum Layer 1
STRK holders strongly supported studying a move from an Ethereum Layer 2 to a standalone Layer 1 with quantum-resistant security.
- published on Newsmetry
- original source published
the public page opens no earlier than 15 minutes after we detect the story. approved stories may reach the api sooner. connect the api →
what happened
Starknet (STRK) holders overwhelmingly backed a proposal to study moving the network from an Ethereum Layer 2 into an independent, post-quantum Layer 1, according to a seven-day Snapshot poll that closed on Thursday. More than 93.5% of voting power supported the idea, with over 2,800 wallets taking part, according to StarkWare. The company behind Starknet did not vote, leaving the decision to the community, The Block reported.
StarkWare and the Starknet Foundation will now research the transition. Any actual move would require a separate vote by STRK holders. StarkWare CEO Eli Ben-Sasson said a draft whitepaper is expected for public review in November, and he set a 2027 target for Starknet to become quantum-safe.
Starknet relies on hash-based cryptography, but it inherits its security from Ethereum, so its quantum resistance depends on the underlying chain. STRK will remain the native token, no new token will be created, and Ethereum bridges to Starknet will stay open.
why it matters
For markets this is still a research step with no agreed date for a transition. Investors may watch the draft publication and the second vote, which would decide whether the network's architecture changes.
market impact
STRK and the Starknet ecosystem: a possible architecture change and reduced reliance on Ethereum
tags
instruments
sources
- Starknet community overwhelmingly backs research into becoming an independent post-quantum Layer 1 — The Block, 22 October 2026 at 09:32 UTC
prepared by the newsmetry newsroom with ai assistance from the sources listed below. not investment advice.
the public page opens no earlier than 15 minutes after we detect the story. approved stories may reach the api sooner.
get stories in real time ↗