Hello Greg,
BIP 110 failed to achieve adoption in both phases of its deployment
attempt. It got just shy of 2.5% of blocks signaling readiness in the
latest signaling period, and since RDTS nodes mandated signaling, RDTS
nodes relegated themselves to a chain that only found two blocks, while
the Bitcoin blockchain grew by 134 blocks. The sole block author on the
RDTS chaintip has since announced that they have ceased mining on the
stalled chaintip.
While it’s your choice to remain on the stalled chaintip or to throw-in
with the hard fork that is now being discussed, it’s clear that the
Bitcoin network rejected the soft fork. The minority hashrate chaintip
therefore constitutes a forkcoin. Altcoins are not on-topic for the BIPs
repository, and therefore, BIP110 should be advanced from Deployed to
Closed as it is obsolete.
Murch
On 2026-08-09 11:36, Greg Tonoski wrote:
Objection. The Bitcoin Improvement Proposal 110 (BIP-110 Reduced Data
Temporary Softfork) has been activated. There are two blocks with the
bit 4 signal (block height 961633) and the estimated 18 000 fully
validating nodes in the network. I keep running such a node and
accepting payments even if time interval between blocks is temporarily
longer until the next difficulty adjustment.
On Sun, 9 Aug 2026 at 20:07, Jon Atack <[email protected]
<mailto:[email protected]>> wrote:
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 [email protected]
<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/
bitcoindev/cf801753-e5b1-46bf-a0ae-9d88a0624829n%40googlegroups.com
<https://groups.google.com/d/msgid/bitcoindev/cf801753-e5b1-46bf-
a0ae-9d88a0624829n%40googlegroups.com?
utm_medium=email&utm_source=footer>.
--
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 [email protected]
<mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/
bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr-
GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com <https://groups.google.com/
d/msgid/bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr-
GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com?
utm_medium=email&utm_source=footer>.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bitcoindev/474c04c7-fa32-4f97-84ae-722f12f08f40%40murch.one.
