From: Erik Aronesty <earonesty@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Hashed keys are actually fully quantum secure
Date: Tue, 18 Mar 2025 09:48:25 -0700 (PDT) [thread overview]
Message-ID: <94689568-7ec5-4f19-b626-c9bdab57f5d8n@googlegroups.com> (raw)
In-Reply-To: <XHIL8Z4i4hji8LhbJ0AiKQ4eago2evXwjTGUOqqyAye_2nM3QicDpHo6KkcznBAHPUrIWSLj_GuiTQ_97KPjxcOrG8pE0rgcXucK2-4txKE=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]
If your threat model assumes an attacker can promptly recover the private
key from the public key then once the user broadcasts his transaction
spending both the old output and his own QR output the attacker could
simply create his own QR output and RBF the honest transaction.
correct. this doesn't provide protection. and any such rule about
"spent along with" would be a hard fork. which is fine if qr ever matters
(there's still not a lot of evidence that it will).
--
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/94689568-7ec5-4f19-b626-c9bdab57f5d8n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1369 bytes --]
next prev parent reply other threads:[~2025-03-18 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 18:25 [bitcoindev] Hashed keys are actually fully quantum secure Martin Habovštiak
2025-03-16 18:50 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-18 16:48 ` Erik Aronesty [this message]
2025-03-24 0:24 ` Lloyd Fournier
2025-03-30 20:16 ` Martin Habovštiak
2025-03-16 19:03 ` Agustin Cruz
2025-03-16 20:52 ` Martin Habovštiak
2025-03-17 10:44 ` Lloyd Fournier
2025-03-17 11:07 ` Martin Habovštiak
2025-03-30 15:41 ` David A. Harding
2025-03-30 20:11 ` Martin Habovštiak
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=94689568-7ec5-4f19-b626-c9bdab57f5d8n@googlegroups.com \
--to=earonesty@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