From: Hunter Beast <hunter@surmount•systems>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Introducing Hourglass
Date: Tue, 29 Apr 2025 15:38:26 -0700 (PDT) [thread overview]
Message-ID: <db3d0ec4-90b8-44a4-b912-b98ec9083b10n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]
This is a proposal to mitigate against potential mass liquidation of P2PK
funds. The specification is pretty simple, but the motivation and
justification for it is a bit longer.
https://github.com/cryptoquick/bips/blob/hourglass/bip-hourglass.mediawiki
Feedback welcome!
--
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/db3d0ec4-90b8-44a4-b912-b98ec9083b10n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1273 bytes --]
next reply other threads:[~2025-04-29 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 22:38 Hunter Beast [this message]
2025-04-30 3:01 ` [bitcoindev] " 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=db3d0ec4-90b8-44a4-b912-b98ec9083b10n@googlegroups.com \
--to=hunter@surmount$(echo .)systems \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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