From: Murch <murch@murch.one>
To: Tim Ruffing <me@real-or-random.org>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Follow-up regarding Motion to Activate BIP 3
Date: Wed, 14 Jan 2026 11:12:38 -0800 [thread overview]
Message-ID: <97db0b83-e271-47ee-acd3-1c1fb92ec05c@murch.one> (raw)
In-Reply-To: <f5124eeb53d80964161151ad6e75f1903b094e5b.camel@real-or-random.org>
Hi everyone,
After a number of people stated in the past few days here and in the
Activation pull request that they perceived BIP 3 to have achieved rough
consensus, BIP 3 was deployed this morning. This sunset BIP 2: future
submissions to the BIPs repository will be guided by BIP 3.
Thank you for your input and support!
Murch
On 2026-01-14 00:27, Tim Ruffing wrote:
> I perceive that there is rough consensus for activating BIP 3.
>
> On Tue, 2026-01-06 at 16:42 -0800, Murch wrote:
>> I therefore request that others, especially
>> participants in the BIPs process, comment on whether they perceive
>> there
>> to be rough consensus for activating BIP 3.
>>
--
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/97db0b83-e271-47ee-acd3-1c1fb92ec05c%40murch.one.
prev parent reply other threads:[~2026-01-14 19:45 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
2026-01-14 0:47 ` Bryan Bishop
2026-01-14 8:27 ` Tim Ruffing
2026-01-14 19:12 ` Murch [this message]
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=97db0b83-e271-47ee-acd3-1c1fb92ec05c@murch.one \
--to=murch@murch.one \
--cc=bitcoindev@googlegroups.com \
--cc=me@real-or-random.org \
/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