public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Pieter Wuille <bitcoin-dev@wuille.net>
To: Hunter Beast <hunter@surmount.systems>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Proposal for Quantum-Resistant Address Migration Protocol (QRAMP) BIP
Date: Wed, 19 Feb 2025 17:56:07 +0000	[thread overview]
Message-ID: <pXZj0cBHqBVPjkNPKBjiNE1BjPHhvRp-MwPaBsQu-s6RTEL9oBJearqZE33A2yz31LNRNUpZstq_q8YMN1VsCY2vByc9w4QyTOmIRCE3BFM=@wuille.net> (raw)
In-Reply-To: <f9e233e0-9d87-4e71-9a9f-3310ea242194n@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2757 bytes --]

On Wednesday, February 19th, 2025 at 11:06 AM, Hunter Beast <hunter@surmount.systems> wrote:

> I don't see why old coins should be confiscated. The better option is to let those with quantum computers free up old coins. While this might have an inflationary impact on bitcoin's price, to use a turn of phrase, the inflation is transitory. Those with low time preference should support returning lost coins to circulation.

Of course they have to be confiscated. If and when (and that's a big if) the existence of a cryptography-breaking QC becomes a credible threat, the Bitcoin ecosystem has no other option than softforking(*) out the ability to spend from signature schemes (including ECDSA and BIP340) that are vulnerable to QCs. The alternative is that millions of BTC become vulnerable to theft; I cannot see how the currency can maintain any value at all in such a setting. And this affects everyone; even those which diligently moved their coins to PQC-protected schemes.

> Also, I don't see the urgency, considering the majority of coins are in either P2PKH, P2WPKH, P2SH, and P2WSH addresses. If PQC signatures aren't added, such as with BIP-360, there will be some concern around long exposure attacks on P2TR coins.

There were literally millions of BTC locked in outputs whose public keys are already known to the public, long before P2TR. Either because of they're in P2PK outputs, because they're in hashed addresses which have been reused and already using for spending, or because they're been spent in forked chains. There are likely substantially more BTC in outputs whose public keys are known to multiple parties (multisig, lightning channels, escrow services, ...) but not to the entire world.

I certainly agree there is no urgency right now, but if (and only if) cryptography-breaking QCs become a reality, the ecosystem has no choice but disabling(*) the spending of coins through schemes that become broken, and needs to have done so before such a machine exists.

(*) There may exist ways of retaining the ability to spend coins in vulnerable schemes, if they involve a PQC proof of knowledge of some additional secret, e.g. the xprv the key was derived with. It's a significant complication, not and applicable to everything, but might be an option.

--
Pieter

-- 
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/pXZj0cBHqBVPjkNPKBjiNE1BjPHhvRp-MwPaBsQu-s6RTEL9oBJearqZE33A2yz31LNRNUpZstq_q8YMN1VsCY2vByc9w4QyTOmIRCE3BFM%3D%40wuille.net.

[-- Attachment #2: Type: text/html, Size: 5549 bytes --]

      parent reply	other threads:[~2025-02-19 18:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 22:36 [bitcoindev] Proposal for Quantum-Resistant Address Migration Protocol (QRAMP) BIP Agustin Cruz
2025-02-12  0:15 ` Dustin Ray
2025-02-12  0:37   ` Agustin Cruz
2025-02-12  0:47     ` Dustin Ray
2025-02-12  0:54       ` Agustin Cruz
2025-02-19 16:06         ` Hunter Beast
2025-02-19 16:42           ` Agustin Cruz
2025-02-19 20:10             ` Dustin Ray
2025-02-19 21:07               ` Agustin Cruz
2025-02-19 21:35                 ` Dustin Ray
2025-02-19 21:49                   ` Agustin Cruz
2025-02-19 22:05                     ` Dustin Ray
2025-02-19 17:56           ` Pieter Wuille [this message]

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='pXZj0cBHqBVPjkNPKBjiNE1BjPHhvRp-MwPaBsQu-s6RTEL9oBJearqZE33A2yz31LNRNUpZstq_q8YMN1VsCY2vByc9w4QyTOmIRCE3BFM=@wuille.net' \
    --to=bitcoin-dev@wuille.net \
    --cc=bitcoindev@googlegroups.com \
    --cc=hunter@surmount.systems \
    /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