BIP 110: update status to closed

[Jon Atack]

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

[Greg Tonoski]

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.

--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/cf801753-e5b1-46bf-a0ae-9d88a0624829n%40googlegroups.com.

[Anthony Towns]

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

[Greg Tonoski]

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.

[Murch]

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

> <mailto:bitcoindev+...@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+...@googlegroups.com

> <mailto:bitcoindev+...@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>.

[Greg Tonoski]

The BIP-110 was activated at the block height as you (Mark Erhardt) approved in the specification. There wasn't any other "adoption" criteria (especially "2.5%").

As the Bitcoin Whitepaper says: "As long as honest nodes control the most CPU power on the network, they can generate the longest chain and outpace any attackers. (...) Each node works on finding a difficult proof-of-work for its block". The chain is mined by many more nodes than the single one "Roughnecks" that you mentioned below. Roughnecks' decision does not represent the other nodes. Roughnecks node is free to leave at will as specified in the Bitcoin Whitepaper: "Nodes can leave and rejoin the network at will (...)". Again, there are estimated 18 000 fully validating nodes in the Bitcoin network and they don't reject the BIP-110 soft-fork (a.k.a. RDTS). I am running of the nodes and has just broadcast a transaction. It's not an altcoin transaction. The bitcoins should not be confiscated. Therefore, I think that my objection is justified.

I look forward to a reply.

To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/474c04c7-fa32-4f97-84ae-722f12f08f40%40murch.one.