The way I see Kaspa quantum security moving: Relevant today: hiding unspent public keys until spend time (the Bitcoin P2PKH model). Kaspa can already do this via P2SH / script-hash addresses with wallet and user coordination; the default address type currently exposes the key on receipt. Next practical step: improve the efficiency of post-quantum signature verification in the script engine. Pure-script hash-based vaults (SLH-DSA-128s and related variants) already work on testnet-10 as an interim. A dedicated non-ZK opcode (e.g. OpCheckSigPq / OpCheckSigFromStackPq) would make them cheaper and more usable at scale. MuHash replacement comes later. It is the harder problem (with real state-size and potential header-impact consequences). LtHash-style candidates are being tested as shadows, and recent parameter/security research is being discussed, but getting the security level, state size, and long-term maintainability right will take significant time. It is not an immediate emergency, but it is the piece that ultimately protects the integrity of everything.