Pre-emptive commit/reveal for quantum-safe migration (poison-pill)

In a recent discussion within the Bitcoin Development Mailing List, Leo Wandersleb addressed concerns raised by Nagaev regarding potential quantum computing threats to Bitcoin's security architecture. Wandersleb elaborated on two proposed strategies aimed at enhancing the protection of exposed public keys against quantum-enabled attacks. The first strategy involves the implementation of a "poison pill" variant, which constitutes a hard fork in the blockchain. This approach would necessitate the creation of post-quantum address types, offering a proactive defense mechanism by embedding an additional hash layer to safeguard all exposed public keys from slower brute force attacks, as originally suggested in Tadge's proposal.

The conversation further explored the implications of quantum computing advancements, making quick and cheap attacks more feasible. In this context, Tadge's proposal for a soft fork was revisited, highlighting its potential to work with commitments that protect currently exposed public keys. This would require that commitments for these keys be established prior to the soft fork, thereby offering a temporary shield against quantum threats.

Moreover, the dialogue touched upon different priorities within the Bitcoin community, notably the trade-off between guarding against potential quantum computing confiscations and the broader risks associated with a quantum computing breakthrough. Those more concerned with the former might lean towards the hard fork poison pill option as it provides a direct method to secure exposed keys against such vulnerabilities.

This exchange reflects the ongoing efforts and debates within the Bitcoin development community to preemptively address and mitigate emerging security challenges posed by advancements in quantum computing. By considering both soft and hard fork solutions, developers aim to fortify the cryptocurrency against future technological threats while navigating the diverse concerns and preferences of its user base.