From: Sjors Provoost <sjors@sprovoost.nl>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Cc: waxwing/ AdamISZ <ekaggata@gmail.com>
Subject: Re: [bitcoindev] Against Allowing Quantum Recovery of Bitcoin
Date: Wed, 28 May 2025 09:46:40 +0200 [thread overview]
Message-ID: <7E385C29-F84D-45E1-8314-D735929F9DC1@sprovoost.nl> (raw)
In-Reply-To: <c568cc33-abba-4010-ac65-42c84dae6eb8n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
> Op 28 mei 2025, om 03:07 heeft waxwing/ AdamISZ <ekaggata@gmail.com> het volgende geschreven:
>
> Hi all,
>
> I'd like to point out that the worst case scenarios here might be even worse than one naturally thinks.
Good morning! :-)
> Two more observations:
>
> (3) I do really like the "disabled NUMS" concept in regard to taproot external keys, for paving the way to PQC in tapleaf. This is one kind of censorship that cannot be controversial.
I brought this up [0], but it was later pointed out to me that it doesn't work.
The scriptPubKey that you see on chain is not the NUMS point itself. The internal key is a NUMS point, but it's tweaked. When this tweaked key is spent, the tweak itself is not revealed, so the blockchain can't tell if a NUMS was involved, and can't block the spend.
- Sjors
https://groups.google.com/g/bitcoindev/c/uUK6py0Yjq0/m/bQk2v0E5BQAJ
--
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/7E385C29-F84D-45E1-8314-D735929F9DC1%40sprovoost.nl.
[-- Attachment #2: Type: text/html, Size: 4112 bytes --]
next prev parent reply other threads:[~2025-05-28 9:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 19:02 [bitcoindev] Against Allowing Quantum Recovery of Bitcoin AstroTown
2025-03-24 11:19 ` Agustin Cruz
2025-05-25 19:03 ` 'conduition' via Bitcoin Development Mailing List
2025-05-25 23:03 ` Dustin Ray
2025-05-26 0:32 ` Agustin Cruz
2025-05-28 1:07 ` waxwing/ AdamISZ
2025-05-28 7:46 ` Sjors Provoost [this message]
2025-05-28 21:15 ` waxwing/ AdamISZ
-- strict thread matches above, loose matches on Subject: below --
2025-03-16 14:15 Jameson Lopp
2025-03-16 18:03 ` Chris Riley
2025-03-16 19:44 ` Nagaev Boris
2025-03-16 21:25 ` Jameson Lopp
2025-03-16 22:56 ` IdeA
2025-03-17 13:28 ` Jameson Lopp
2025-03-17 12:00 ` Matt Corallo
2025-03-18 12:48 ` Sjors Provoost
2025-03-25 1:06 ` Matt Corallo
2025-03-25 8:16 ` Sjors Provoost
2025-03-28 20:00 ` Matt Corallo
2025-03-30 22:23 ` Javier Mateos
2025-04-04 4:49 ` 'Ben Sigman' via Bitcoin Development Mailing List
2025-04-06 14:07 ` Nadav Ivgi
2025-04-30 15:40 ` Michael Tidwell
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=7E385C29-F84D-45E1-8314-D735929F9DC1@sprovoost.nl \
--to=sjors@sprovoost.nl \
--cc=bitcoindev@googlegroups.com \
--cc=ekaggata@gmail.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