Starknet is evaluating a move from Ethereum Layer 2 to its own Layer 1 chain, with quantum resistance as the stated objective and a 2027 timeframe for the potential transition, according to a report by The Defiant.

The proposal marks a significant architectural pivot for one of the most prominent zk-rollup networks in the Ethereum ecosystem. Starknet currently operates as a validity rollup, batching transactions off-chain and posting proofs to Ethereum, where final settlement and data availability are handled. Moving to a standalone Layer 1 would sever that dependency and place consensus, settlement and data availability entirely under Starknet's own control.

Why quantum security drives the debate

The reported rationale is cryptographic. Rollups inherit Ethereum's security assumptions, and those assumptions rest in part on elliptic-curve cryptography — specifically ECDSA signatures — which sufficiently powerful quantum computers could break. A network operating its own Layer 1 could adopt post-quantum cryptographic schemes natively rather than waiting for the underlying settlement layer to upgrade.

The 2027 target aligns with a broader industry discussion about quantum risk timelines. Researchers and protocol teams across the sector have been assessing migration paths toward lattice-based and other post-quantum signature schemes, and several blockchain projects have announced intent to harden their stacks before the end of the decade. Starknet's consideration of the question at the Layer 1 level would place it among the more aggressive responses to date.

What a Layer 1 shift would change operationally

For Starknet, the change would be consequential on several fronts:

• Settlement autonomy. Starknet would no longer rely on Ethereum for finality, removing a dependency but also removing the security inheritance that has been central to its value proposition as a rollup.
• Validator and consensus design. A standalone chain requires its own consensus mechanism, validator set or proving infrastructure, all of which carry operational and decentralization trade-offs.
• Ecosystem and bridge infrastructure. Applications built on Starknet, as well as bridges connecting it to Ethereum and other chains, would need to adapt to the new architecture.
• STARK proof stack. Starknet's core technology — STARK proofs, developed by StarkWare — is already positioned as more quantum-resilient than SNARK alternatives because it relies on hash functions and collision assumptions rather than elliptic-curve arithmetic. A Layer 1 move could extend that posture across the full stack, including signature verification.

Open questions

The Defiant's report describes the shift as under consideration rather than finalized, and key parameters remain undefined in public discussion. These include the intended consensus model for a hypothetical Starknet Layer 1, the treatment of existing STRK token holders and stakers, migration mechanics for decentralized applications, and whether Ethereum would retain any role — for example, as a data availability layer or an anchored checkpointing destination.

The stakes extend beyond one network. Starknet is among the largest zk-rollup deployments by technical pedigree, and a public departure from the rollup model would test the argument that Layer 2 inheritance of Ethereum security remains the dominant end-state for scaling networks. Competing zk projects have largely framed their roadmaps around deeper Ethereum integration — shared sequencing, native rollup upgrades, and EIP-4844 blob data — rather than separation.

It would also sharpen the sector-wide conversation about quantum preparedness. To date, most post-quantum initiatives in crypto have taken the form of research papers, hybrid signature schemes or contingency plans. A production network committing to a full architectural migration on a dated timeline would convert that discussion into an engineering program with deliverables.

What comes next

Starknet governance processes would need to formalize any such proposal before execution, meaning the community vote and a technical specification are the concrete next milestones to watch. With 2027 as the stated horizon, decisions on consensus design and migration mechanics would likely need to land within the next development cycle for the timeline to remain credible.