kept wondering why @Starknet accounts feel different when changing how they sign. most chains lock the signature check in the Protocol... new method means the whole Network upgrades together. here the Account is a Contract so it can pick its own Verifier. i opened the Migration Register and it said a new Implementation can adopt a different one without any Protocol change... existing accounts don’t switch on their own. the Falcon 512 OpenZeppelin ran on Mainnet is still a Demo and unaudited... @Starknet lists that status in the Register. does a normal account keep the same Address if a new Verifier gets added later? the Validation logic sits inside the Account on @Starknet