From: Daniel Buchner <danjbuchner@gmail.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Proposal for minimum viable PQC protection without a fork
Date: Fri, 10 Apr 2026 19:52:23 -0500 [thread overview]
Message-ID: <CAHZ6zJH85YLcjtK1yz+eq7cnJi7JD5HLVeWp+j1faofwUdQ1Zw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Just wanted to throw out this proposal for enabling folks to optionally
incorporate PQC protection that doesn't require upfront implementation of
PQC logic/validation code:
https://github.com/csuwildcat/pqc-precommitment-migration. I think it could
be a reasonable middle ground between the (reasonable) hesitance to
integrate PQC code into Bitcoin today vs the desire of some to have a clear
mitigation plan in the unlikely event a Q-Day occurred in the near or
mid-term.
Let me know what you think!
- Daniel
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAHZ6zJH85YLcjtK1yz%2Beq7cnJi7JD5HLVeWp%2Bj1faofwUdQ1Zw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 1376 bytes --]
reply other threads:[~2026-04-11 1:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHZ6zJH85YLcjtK1yz+eq7cnJi7JD5HLVeWp+j1faofwUdQ1Zw@mail.gmail.com \
--to=danjbuchner@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox