If your wallet needs a new signature scheme, should the whole network have to upgrade first? That’s what interests me about @Starknet programmable accounts. Account signatures authorize transactions. STARK proofs verify computation. Keeping those roles separate means developers can introduce a new signature verifier without a network-wide upgrade, while the hash-based proving system stays in place. Think of changing your apartment’s lock without rebuilding the building. The practical benefit: an account developer can introduce stronger signing without waiting for everyone else to switch at once. But having an upgrade path doesn’t automatically migrate existing wallets. Recovery, key management, audits and adoption still need work. Starknet is preparing for quantum threats. For me, the important design choice is making cryptography replaceable before replacing it becomes urgent. https://t.co/VIrUk0ToqH