Eniola4pnf🇪🇸

Why would Starknet want to control its own timeline? Most people treat security upgrades like a software update on their phone. You tap “update,” the phone restarts and you’re done. On a blockchain it’s different. When the cryptography that protects accounts, bridges and data needs to change, the whole network has to coordinate. If part of that system lives on another chain, you don’t fully control the calendar. That’s the practical reason @Starknet is researching an independent L1. Starknet is an Ethereum L2. It runs its own execution and proves it with STARKs, which are hash-based validity proofs. But two pieces still lean on Ethereum: 1. The bridge that moves assets between the two networks. 2. Data availability, which keeps Starknet’s state data publicly available. These pieces inherit Ethereum’s cryptography and Ethereum’s upgrade timeline. If Ethereum’s post-quantum migration moves slower than needed, Starknet’s remaining dependencies move at the same speed. An independent L1 would remove that external calendar. Starknet would decide when and how its own security upgrades happen instead of waiting on another chain’s schedule. On 22 October 2026 a non-binding community poll closed with roughly 93.5 % of voting power in favour of researching that path. A “yes” only starts research and further governance steps. It does not approve a migration, set a final design, or change anything today. Starknet is not claiming it is already fully quantum-safe. It is preparing the architecture so that, when the time comes, the upgrades can actually be executed under its own control. Two structural advantages already exist: 1. The proving layer was built on cryptographic hash functions rather than elliptic-curve assumptions. 2. Accounts are programmable smart contracts, so new signature methods can be added without a network-wide hard fork. Owning the full stack would help more, though it also means giving up some of what Ethereum provides today. That tradeoff is exactly what the research needs to answer. Progress is tracked at the StarkWare Quantum Hub: quantum.starkware.co/