From: "Sjors Provoost" <sjors@sprovoost.nl>
To: "Greg Tonoski" <greg.tonoski@gmail.com>, Murch <murch@murch.one>,
"'Bitcoin Development Mailing List'"
<bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP 110: update status to closed
Date: Mon, 10 Aug 2026 13:03:58 +0200 [thread overview]
Message-ID: <5911e0ad-b8f1-4cdb-bd6e-47f032c72924@app.fastmail.com> (raw)
In-Reply-To: <CAMHHROzXou09Sv0=XGNFd36Ng4Ld-iM44dvcX8SYOb8=doMLRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7858 bytes --]
Hi Greg,
Closing a BIP does not confiscate coins. The only way to achieve that would a new BIP enforcing a confiscatory soft fork on top of the BIP 110 forked chain. Or a checkpoint on the winning chain. Nobody is advocating for either.
Closing a BIP also doesn't ban anyone from running a node or continuing to mine. But the odds of catching up are slim.
I'm not in a rush to close it, but what would be your own criteria for when it's reasonable to do so?
I could spin up a BIP 12 (OP_EVAL) node tomorrow, reject P2SH by forking off at its activation height, and probably mine a whole bunch of blocks trivially. Modern Bitcoin Core wouldn't reject those blocks, because checkpoints have been removed. But I would never catch up with the tip. Nobody would seriously considering reopening BIP12 in such a scenario, even if I ran a million nodes.
For BIP110, it was obvious to me years ago [1] that this was never going to work, not as a policy rule, and not as a consensus rule. For others it look longer realize this, and some people never will. Hard to put an exact number on when to close it, though now would be fine.
- Sjors
[0] https://github.com/bitcoin/bips/blob/master/bip-0012.mediawiki
[1] see e.g. https://bitcoinexplainedpodcast.com/@nado/episodes/episode-98-return-of-the-op-return and my comments on
On Sun, Aug 9, 2026, at 22:12, Greg Tonoski wrote:
> 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.
>
> On Sun, 9 Aug 2026 at 21:42, Murch <murch@murch.one> wrote:
>> 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%2Bunsubscribe@googlegroups.com>
>> > <mailto:bitcoindev+unsubscribe@googlegroups.com <mailto:bitcoindev%2Bunsubscribe@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%2Bunsubscribe@googlegroups.com>
>> > <mailto:bitcoindev+unsubscribe@googlegroups.com <mailto:bitcoindev%2Bunsubscribe@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 <mailto:bitcoindev%2Bunsubscribe@googlegroups.com>.
>> To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/474c04c7-fa32-4f97-84ae-722f12f08f40%40murch.one.
>
>
> --
> 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/CAMHHROzXou09Sv0%3DXGNFd36Ng4Ld-iM44dvcX8SYOb8%3DdoMLRw%40mail.gmail.com <https://groups.google.com/d/msgid/bitcoindev/CAMHHROzXou09Sv0%3DXGNFd36Ng4Ld-iM44dvcX8SYOb8%3DdoMLRw%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/5911e0ad-b8f1-4cdb-bd6e-47f032c72924%40app.fastmail.com.
[-- Attachment #2: Type: text/html, Size: 11389 bytes --]
next prev parent reply other threads:[~2026-08-10 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2026-08-09 20:12 ` Greg Tonoski
2026-08-10 11:03 ` Sjors Provoost [this message]
2026-08-10 11:54 ` Saint Wenhao
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=5911e0ad-b8f1-4cdb-bd6e-47f032c72924@app.fastmail.com \
--to=sjors@sprovoost.nl \
--cc=bitcoindev@googlegroups.com \
--cc=greg.tonoski@gmail.com \
--cc=murch@murch.one \
/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