From: Jon Atack <jonnyatack@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] BIP 110: update status to closed
Date: Sun, 9 Aug 2026 11:06:01 -0700 (PDT) [thread overview]
Message-ID: <cf801753-e5b1-46bf-a0ae-9d88a0624829n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1056 bytes --]
Hello list,
I'd like to propose marking BIP 110 Reduced Data Temporary Softfork as
closed, following the chain split yesterday during its mandatory signaling
period, when its chain began rejecting as invalid all blocks that did not
signal bit 4 and mining and block production stalled on the BIP 110 chain.
Per BIP 3, a BIP may evolve from Deployed to Closed when it is no longer in
active use. Any community member may initiate this status update by
announcing it to the mailing list, and proceed if no objections have been
raised for four weeks. BIPs are not deleted; they are retained for
historical/educational interest after being updated to Closed.
Regards,
Jon
--
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/cf801753-e5b1-46bf-a0ae-9d88a0624829n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1397 bytes --]
next reply other threads:[~2026-08-09 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 18:06 Jon Atack [this message]
2026-08-09 18:36 ` [bitcoindev] BIP 110: update status to closed Greg Tonoski
2026-08-09 18:54 ` Anthony Towns
2026-08-09 19:01 ` Greg Tonoski
2026-08-09 19:35 ` Murch
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=cf801753-e5b1-46bf-a0ae-9d88a0624829n@googlegroups.com \
--to=jonnyatack@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