* [bitcoindev] BIP 110: update status to closed
@ 2026-08-09 18:06 Jon Atack
2026-08-09 18:36 ` Greg Tonoski
0 siblings, 1 reply; 5+ messages in thread
From: Jon Atack @ 2026-08-09 18:06 UTC (permalink / raw)
To: Bitcoin Development Mailing List
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitcoindev] BIP 110: update status to closed
2026-08-09 18:06 [bitcoindev] BIP 110: update status to closed Jon Atack
@ 2026-08-09 18:36 ` Greg Tonoski
2026-08-09 18:54 ` Anthony Towns
2026-08-09 19:35 ` Murch
0 siblings, 2 replies; 5+ messages in thread
From: Greg Tonoski @ 2026-08-09 18:36 UTC (permalink / raw)
To: Bitcoin Development Mailing List, Jon Atack
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
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 <jonnyatack@gmail.com> 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 bitcoindev+unsubscribe@googlegroups.com.
> 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 bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMHHROy%3DNNoaRc828xp_Qr-GJqoDguTrowfBKsk0XuYsgaOhSg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2842 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitcoindev] BIP 110: update status to closed
2026-08-09 18:36 ` Greg Tonoski
@ 2026-08-09 18:54 ` Anthony Towns
2026-08-09 19:01 ` Greg Tonoski
2026-08-09 19:35 ` Murch
1 sibling, 1 reply; 5+ messages in thread
From: Anthony Towns @ 2026-08-09 18:54 UTC (permalink / raw)
To: Greg Tonoski; +Cc: Bitcoin Development Mailing List, Jon Atack
On Sun, Aug 09, 2026 at 08:36:28PM +0200, 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.
This objection seems straightforward to resolve: BIP 3 requires a 4 week
period before moving a BIP to "closed", and if there is fewer than one
block found per 4 week period, you can expect it will take about 150
years for the difficulty retarget point to be reached.
So I'd suggest don't mark the BIP closed until there's been 18-28 days
(100-150 years to the retarget) since the last BIP110 compliant block
was found.
Cheers,
aj
--
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/anjM4DQh-ZYafJXC%40erisian.com.au.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitcoindev] BIP 110: update status to closed
2026-08-09 18:54 ` Anthony Towns
@ 2026-08-09 19:01 ` Greg Tonoski
0 siblings, 0 replies; 5+ messages in thread
From: Greg Tonoski @ 2026-08-09 19:01 UTC (permalink / raw)
To: Anthony Towns, Bitcoin Development Mailing List
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
I disagree. What do you propose as a justification for the 4 weeks and not
another duration? Moreover, there are valid transactions, valid new UTXOs
and the valid blocks. Would you suggest that they are subject to
confiscation?
I look forward to a reply.
On Sun, 9 Aug 2026 at 20:54, Anthony Towns <aj@erisian.com.au> wrote:
> On Sun, Aug 09, 2026 at 08:36:28PM +0200, 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.
>
> This objection seems straightforward to resolve: BIP 3 requires a 4 week
> period before moving a BIP to "closed", and if there is fewer than one
> block found per 4 week period, you can expect it will take about 150
> years for the difficulty retarget point to be reached.
>
> So I'd suggest don't mark the BIP closed until there's been 18-28 days
> (100-150 years to the retarget) since the last BIP110 compliant block
> was found.
>
> Cheers,
> aj
>
--
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/CAMHHROx6F2L%3DURDs_TNFsfzUSZ4kZmsBCkp8_HoioLA8rOp1JQ%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2351 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [bitcoindev] BIP 110: update status to closed
2026-08-09 18:36 ` Greg Tonoski
2026-08-09 18:54 ` Anthony Towns
@ 2026-08-09 19:35 ` Murch
1 sibling, 0 replies; 5+ messages in thread
From: Murch @ 2026-08-09 19:35 UTC (permalink / raw)
To: bitcoindev
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 <jonnyatack@gmail.com
> <mailto:jonnyatack@gmail.com>> 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 bitcoindev+unsubscribe@googlegroups.com
> <mailto:bitcoindev+unsubscribe@googlegroups.com>.
> 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 bitcoindev+unsubscribe@googlegroups.com
> <mailto:bitcoindev+unsubscribe@googlegroups.com>.
> 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 bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/474c04c7-fa32-4f97-84ae-722f12f08f40%40murch.one.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-08-09 19:43 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-09 18:06 [bitcoindev] BIP 110: update status to closed Jon Atack
2026-08-09 18:36 ` Greg Tonoski
2026-08-09 18:54 ` Anthony Towns
2026-08-09 19:01 ` Greg Tonoski
2026-08-09 19:35 ` Murch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox