Changing the locks without rebuilding the building Think of a building. The locks on the doors decide who can open them. The foundation and the structural beams decide whether the building is sound. On Starknet those two jobs are separate. Signatures are the locks. They authorise a transaction; they prove that the right person (or the right smart contract) approved it. STARK proofs are the foundation. They verify that the computation itself was done correctly. They don’t care which lock was used; they only care that the result is valid. Because accounts on @Starknet are programmable smart contracts (native account abstraction), the “lock” can be changed without touching the foundation. A new account implementation can use a different signature method, like a post-quantum signature scheme, without needing a network-wide upgrade or a hard fork. The proving system stays the same. It’s like being able to swap the locks on every door in a building for a new type of lock, without having to rebuild the walls or the foundation. That flexibility exists today.
