From: Ruben Somsen <rsomsen@gmail.com>
To: Murch <murch@murch.one>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Follow-up regarding Motion to Activate BIP 3
Date: Wed, 14 Jan 2026 01:06:48 +0100 [thread overview]
Message-ID: <CAPv7TjZjhG4UiG6U1-ktSAFYjwQ4zwyCAws5QqCzz1=tGujN1w@mail.gmail.com> (raw)
In-Reply-To: <a71add89-53ff-4486-9ed9-7cbd1db8ab58@murch.one>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
My opinion has not changed since my last review - it's a clear step up from
BIP2 and it's ready for adoption.
The BIP is significantly polished, and enough time has passed for
objections to be voiced. Activation has my full support.
Cheers,
Ruben
On Tue, Jan 13, 2026 at 2:21 AM Murch <murch@murch.one> wrote:
> Thanks Jonas, Chris, and Coperbyte Solutions for weighing in.
>
> I rebased the Activation PR today so that it applies the process changes
> also to the recently published BIP 433. The Activation PR is now again
> (from a technical point of view) ready for merge.
>
> Best,
> Murch
>
> On 2026-01-12 04:35, Jonas Nick wrote:
> > No objections have been raised since Nov 29, and all objections were
> > responded
> > to on the mailing list on Dec 2 and addressed in the BIP on Dec 16. The
> > latest
> > version of the activation PR [0] has received multiple ACKs.
> >
> > Therefore, I see rough consensus and BIP 3 should activate. The current
> > uncertainty is adding friction to the BIP process.
> >
> > [0] https://github.com/bitcoin/bips/pull/1820
>
> --
> 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/a71add89-53ff-4486-9ed9-7cbd1db8ab58%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/CAPv7TjZjhG4UiG6U1-ktSAFYjwQ4zwyCAws5QqCzz1%3DtGujN1w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2881 bytes --]
next prev parent reply other threads:[~2026-01-14 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 0:42 Murch
2026-01-08 20:40 ` Chris Stewart
2026-01-09 14:11 ` Coperbyte Solutions
2026-01-12 12:35 ` Jonas Nick
2026-01-13 1:16 ` Murch
2026-01-14 0:06 ` Ruben Somsen [this message]
2026-01-14 0:47 ` Bryan Bishop
2026-01-14 8:27 ` Tim Ruffing
2026-01-14 19:12 ` 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='CAPv7TjZjhG4UiG6U1-ktSAFYjwQ4zwyCAws5QqCzz1=tGujN1w@mail.gmail.com' \
--to=rsomsen@gmail.com \
--cc=bitcoindev@googlegroups.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