Please describe the feature you’d like to see added.
The recent Google Research blog serves as a critical wake-up call for the Bitcoin community.
While the “Q-Day” might still be years away, the research highlights a more immediate danger: the extreme difficulty of implementing quantum-resistant schemes responsibly. The discovery of vulnerabilities in early PQC attempts (like the WOTS case mentioned) proves that we cannot afford a rushed, last-minute migration.
I propose that the community moves beyond abstract discussions and begins formalizing a concrete PQC Roadmap:
From Theory to Spec: We need to transition from “discussing algorithms” to drafting specific BIPs for PQC-compatible signature schemes (e.g., ML-DSA or SLH-DSA).
The “Harvest Now, Decrypt Later” Threat: This is already happening. Long-term storage security depends on actions we take today, not tomorrow.
Implementation Safety: We need to establish a dedicated working group to audit potential PQC implementations to avoid the pitfalls Google identified.
“Wait and see” is no longer a security strategy. We need to treat PQC migration as a high-priority engineering goal to ensure Bitcoin’s long-term value-store proposition remains intact.
Is your feature related to a problem, if so please describe it.
No response
Describe the solution you’d like
No response
Describe any alternatives you’ve considered
No response
Please leave any additional context
No response
