From: neonrooks <neonrooks@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Hourglass V2 Update
Date: Fri, 20 Feb 2026 22:22:31 -0800 (PST) [thread overview]
Message-ID: <69633e8d-1491-4230-bfc8-f9300ecc97dcn@googlegroups.com> (raw)
In-Reply-To: <e9b8eac7-0f68-49fc-9301-2be2c3a419b0n@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 849 bytes --]
Disagree with this proposal. Applying a rate-limit to P2PK utxos directly
undermines the permissionless property of Bitcoin - ownership of private
keys is the right to spend as the owner wishes. Instead of allowing
laggards (we know there will be some!) to move coins just before a
real, quantifiable threat, Hourglass V2 all but guarantees a quantum
attacker has time to attack all remaining unspent P2PK utxos during the 32
years it would take to move all coins.
--
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/69633e8d-1491-4230-bfc8-f9300ecc97dcn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1108 bytes --]
prev parent reply other threads:[~2026-02-25 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 20:47 Mike Casey
2026-02-13 22:06 ` Light
2026-02-16 22:03 ` Jameson Lopp
2026-02-17 0:31 ` Light
2026-02-17 13:02 ` Garlo Nicon
2026-02-17 13:24 ` Isabel Foxen Duke
2026-02-23 18:47 ` Isabel Foxen Duke
2026-02-25 14:39 ` Bob Burnett
2026-02-25 16:46 ` Jameson Lopp
2026-02-18 14:33 ` Mike Casey
2026-02-19 3:26 ` Alex
2026-02-21 6:22 ` neonrooks [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=69633e8d-1491-4230-bfc8-f9300ecc97dcn@googlegroups.com \
--to=neonrooks@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