Starknet: Post-Quantum Migration Possible Without Hard Fork

iconKuCoinFlash
Share
AI summary iconSummary
On October 31 (UTC+8), Starknet announced that users can adopt post-quantum signature schemes without a hard fork, thanks to account abstraction. Addresses, balances, and transaction histories remain unchanged. As an Ethereum L2, Starknet continues to use Ethereum for settlement and data availability. Research into an independent L1 would enable Starknet to define its own cryptographic standards and migration plans. STRK remains the native token, with no new token issuance planned. Any transition to an L1 would require a binding governance vote, making this a key on-chain update for the community.

ME News reports that on October 31 (UTC+8), Starknet posted on X that account abstraction enables accounts to switch to post-quantum signature schemes without altering their address, balance, or transaction history, and without modifying the protocol. Starknet noted that, as an Ethereum L2, its settlement, data publication, and cross-chain bridges still rely on Ethereum and elliptic curve cryptography; researching a standalone L1 would allow it to define its own cryptographic schemes and migration timelines. A standalone L1 remains in the research phase; STRK remains the native token, with no plans to issue a new token, and any decision to migrate to an L1 would require a binding governance vote. (Source: ChainCatcher)

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.