Quantum migration isn't just about new contracts. @Starknet also has to deal with the ones already deployed. Imagine a contract using Pedersen hashing to calculate the storage slot where a user's balance is stored. If the hashing rules change, that calculation could point to a completely different slot. The old balance doesn't simply move with it. Existing contracts still need a reliable way to access data written under the previous scheme. That's why one detail in the Quantum Hub's November 3 update caught my attention: tooling to migrate storage maps is still listed as research, with a public specification yet to come. The real test won't just be deploying a quantum-ready contract. It'll be migrating existing state without disrupting contracts people are actively using. That's the demo I'd like to see. Roadmap: https://t.co/77UU3yZT8R