From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Notice: Can BIP52 be moved to Closed?
Date: Thu, 21 May 2026 11:15:33 -0700 [thread overview]
Message-ID: <d641bfc5-ac10-4c98-ae52-5362edfb9794@murch.one> (raw)
In-Reply-To: <40c7064e-9ff5-4373-bf1e-eab96bde63f9@murch.one>
[-- Attachment #1.1.1: Type: text/plain, Size: 2072 bytes --]
Hey everyone,
After directly contacting the BIP52 authors failed, I’m forwarding the
following mesage to the list to provide a public notice instead. If you
happen to be in touch with the BIP52 authors, I would appreciate if you
made them aware.
Cheers,
Murch
----
Hello Mike and Bogdan,
I have been going through the list of Bitcoin Improvement Proposals in
Draft status, trying to determine which ones might be ready to be
advanced to Complete, Deployed, or Closed. It is my impression that your
hard fork proposal BIP52: “Durable, Low Energy Bitcoin PoW” has not made
progress toward Complete in several years. I have also not seen any
recent public discussion of it.
Per BIP3¹:
> BIP authors may decide on their own to change their BIP’s status from
Draft to Closed. If a Draft BIP stops making progress, sees accumulated
feedback unaddressed, or otherwise appears stalled for a year, anyone
may propose the BIP status be updated to Closed. The BIP is then updated
to Closed unless the authors assert that they intend to continue work
within four weeks of being contacted.
Per my impression of the momentum of BIP52, I’m proposing that we update
the status of BIP52 to Closed. Please respond here or on bips#2165²
within the next four weeks, if my impression is mistaken and you are
still pursuing adoption of your proposal. In that case, we could instead
pursue advancing it to Complete³ instead.
Thanks,
Murch (BIP Editor)
¹ https://github.com/bitcoin/bips/blob/master/bip-0003.md#draft--closed
² https://github.com/bitcoin/bips/pull/2165
³ https://github.com/bitcoin/bips/blob/master/bip-0003.md#complete6
--
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/d641bfc5-ac10-4c98-ae52-5362edfb9794%40murch.one.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 56265 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2026-05-21 18:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <40c7064e-9ff5-4373-bf1e-eab96bde63f9@murch.one>]
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=d641bfc5-ac10-4c98-ae52-5362edfb9794@murch.one \
--to=murch@murch.one \
--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