StarknetPost-quantum migration
Review specimen

Selected evidence: OpenZeppelin Falcon-512 account

Starknet's structural starting pointPublic-source migration record

Hash-based proofs.Programmable accounts.

These two architectural properties reduce major migration burdens. They do not complete the wider transition; protocol cryptography, existing deployments and Ethereum dependencies remain separate.

Read the migration register
Structural position
Hash-based STARK proving + programmable accounts
Mainnet demonstration
Falcon-512 account · experimental and unaudited
Live protocol change
Two OS hashes · Starknet v0.14.3
Remaining boundary
Protocol migration · legacy deployments · Ethereum

Migration register

Five surfaces, held apart.

The migration crosses five parts of the system that move under different control. Open a record to see what happened, what it establishes and where the claim ends.

Accounts

Programmable validation lowers the burden of adopting a new signature path. Existing accounts, wallet support and ecosystem adoption remain separate.

Who controls the next move · Starknet account rules · implementers, account teams and wallets

Structural basis

Public evidence

Record integrity

A maintained public record.

Claims move only when public evidence, scope or review state changes. Every update keeps its limitation and source attached.

Last reviewed
22 Jul 2026
Evidence rule
Public sources only · limitations stay with claims
Publication gate
Public maintainer and correction route still required

Latest recorded change

Updated the Falcon record with the mainnet transaction and relabelled two roadmap items as published direction.