Delivery-date: Fri, 28 Mar 2025 17:02:49 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of lf-lists@mattcorallo.com designates 2620:6e:a000:1::99 as permitted sender) client-ip=2620:6e:a000:1::99;
Message-ID: <1c7817fa-6451-4256-b8ce-ddca45abbf52@mattcorallo.com>
Date: Fri, 28 Mar 2025 16:00:40 -0400
MIME-Version: 1.0
Subject: Re: [bitcoindev] Against Allowing Quantum Recovery of Bitcoin
To: Sjors Provoost <sjors@sprovoost.nl>,
 Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: Jameson Lopp <jameson.lopp@gmail.com>
References: <CADL_X_cF=UKVa7CitXReMq8nA_4RadCF==kU4YG+0GYN97P6hQ@mail.gmail.com>
 <43afd5bb-244e-4698-ba3d-139efa2c2058@mattcorallo.com>
 <ED96C777-5BBD-4ACE-8821-A53FDE8FA128@sprovoost.nl>
 <912fd35e-02f5-49b5-b373-ca02806d952f@mattcorallo.com>
 <27A7048A-88D3-432A-AD7C-07C5EC60942D@sprovoost.nl>
Content-Language: en-US
From: Matt Corallo <lf-lists@mattcorallo.com>
In-Reply-To: <27A7048A-88D3-432A-AD7C-07C5EC60942D@sprovoost.nl>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


On 3/25/25 4:16 AM, Sjors Provoost wrote:
> Matt Corallo wrote:
>=20
>>> In that scenario you'd need to use a NUMS point for the key path. Or ma=
ybe that's unsafe, in which case we'd need a new Taproot version without ke=
y path support (or BIP360). That's also not a difficult soft fork, but now =
again you have something that only a small set of users will want to use.
>>>>
>>>>
>> A NUMS point does not suffice unless we explicitly soft-fork out spendin=
g from that NUMS point (which is, of course, doable).
>=20
> This could be a solution to the sequencing conundrum that I tried to expl=
ain.
>=20
> Along with the first PCQ scheme for tapscript (script path), we could hav=
e a soft that disables one or more NUMS points. The latter has zero effect =
under the current cryptographic assumptions, so it's not confiscatory.
>=20
> That way people can start using the scheme without having to worry about =
whether the community decides to freeze key path spending in time. They'll =
still worry about the market value of their coins, but not about whether th=
ey're going to be the first victim (or the umpteenth victim while everyone =
is in denial and blames them for poor key management).


Mmm, yea, fair enough, that seems perfectly reasonable to include.

Matt

--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/=
1c7817fa-6451-4256-b8ce-ddca45abbf52%40mattcorallo.com.