From: Hunter Beast <hunter@surmount.systems>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Proposing a P2QRH BIP towards a quantum resistant soft fork
Date: Sat, 8 Jun 2024 14:04:01 -0700 (PDT) [thread overview]
Message-ID: <62fd28ab-e8b5-4cfc-b5ae-0d5a033af057n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1630 bytes --]
The motivation for this BIP is to provide a concrete proposal for adding
quantum resistance to Bitcoin. We will need to pick a signature algorithm,
implement it, and have it ready in event of quantum emergency. There will
be time to adopt it. Importantly, this first step is a more substantive
answer to those with concerns beyond, "quantum computers may pose a threat,
but we likely don't have to worry about that for a long time". Bitcoin
development and activation is slow, so it's important that those with low
time preference start discussing this as a serious possibility sooner
rather than later.
This is meant to be the first in a series of BIPs regarding a hypothetical
"QuBit" soft fork. The BIP is intended to propose concrete solutions, even
if they're early and incomplete, so that Bitcoin developers are aware of
the existence of these solutions and their potential.
This is just a rough draft and not the finished BIP. I'd like to validate
the approach and hear if I should continue working on it, whether serious
changes are needed, or if this truly isn't a worthwhile endeavor right now.
The BIP can be found here:
https://github.com/cryptoquick/bips/blob/p2qrh/bip-p2qrh.mediawiki
Thank you for your time.
--
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 on the web visit https://groups.google.com/d/msgid/bitcoindev/62fd28ab-e8b5-4cfc-b5ae-0d5a033af057n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1991 bytes --]
next reply other threads:[~2024-06-09 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 21:04 Hunter Beast [this message]
2024-06-14 13:51 ` [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork Pierre-Luc Dallaire-Demers
2024-06-14 14:28 ` Hunter Beast
2024-06-17 1:07 ` Antoine Riard
2024-06-17 20:27 ` hunter
2024-07-13 1:34 ` Antoine Riard
2024-08-06 17:37 ` Hunter Beast
2024-08-15 5:05 ` Hunter Beast
2024-08-22 6:20 ` Antoine Riard
2024-09-25 12:04 ` Hunter Beast
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=62fd28ab-e8b5-4cfc-b5ae-0d5a033af057n@googlegroups.com \
--to=hunter@surmount.systems \
--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