Algorithm Agility for Bitcoin to maintain security in the face of quantum and classic breaks in the signature algorithms

The discourse delves into the intricacies of signature verification within the Bitcoin network, specifically addressing concerns regarding fault injection attacks and the reliability of signing devices like Trezor, Ledger, or mobile phones. It is elucidated that the primary concern for these devices should be their ability to maintain non-corrupted RAM during the execution of signing algorithms rather than the resilience of the SLH-DSA (Standardized Post-Quantum Cryptography NIST algorithm) itself. The argument posits that if a device's RAM cannot be trusted to remain intact, the solution lies in either emulating or directly utilizing error-corrected RAM, pointing out that the focus on SLH-DSA's vulnerability is misplaced.

Furthermore, the conversation shifts towards the broader concept of "algorithmic agility" in the context of Bitcoin's technical architecture. This idea advocates for the network's capacity to support multiple algorithms, including both SLH-DSA and ML-DSA, to ensure adaptability in the face of potential vulnerabilities discovered in the future. The proposed method to achieve this flexibility involves integrating these algorithms as OP-codes within spending scripts that are part of an extensive Merkle tree structure. This structure allows for selective invocation of specific algorithms as necessary, thereby enhancing the robustness and security of the Bitcoin network against evolving threats and challenges.