From: Greg Tonoski <greg.tonoski@gmail.com>
To: Anthony Towns <aj@erisian.com.au>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP 110: update status to closed
Date: Sun, 9 Aug 2026 21:01:50 +0200 [thread overview]
Message-ID: <CAMHHROx6F2L=URDs_TNFsfzUSZ4kZmsBCkp8_HoioLA8rOp1JQ@mail.gmail.com> (raw)
In-Reply-To: <anjM4DQh-ZYafJXC@erisian.com.au>
[-- 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 --]
next prev parent reply other threads:[~2026-08-09 19:06 UTC|newest]
Thread overview: 5+ 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 [this message]
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='CAMHHROx6F2L=URDs_TNFsfzUSZ4kZmsBCkp8_HoioLA8rOp1JQ@mail.gmail.com' \
--to=greg.tonoski@gmail.com \
--cc=aj@erisian.com.au \
--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