From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Murch <murch@murch•one>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Re: Finished planned work on BIP 3: Updated BIP Process
Date: Fri, 28 Mar 2025 17:21:58 +0000 [thread overview]
Message-ID: <d0-uma6EazZZ4vpFmYf8Xk3iKIHPSL9yriDE1HMvFG1ZC-MNMYo5shsw-MFUYesT2XE3Nt3nutjWGPpHnbWK0dFAKKSiAlijmb0nGogD_NE=@protonmail.com> (raw)
In-Reply-To: <458a5831-a1a2-4c21-ab61-dccd00ed5219@murch.one>
[-- Attachment #1: Type: text/plain, Size: 2872 bytes --]
Hi Murch,
Thanks for working on this. I just caught up with the latest version of BIP3 and i agree it seems ready for adoption. Can the other BIP editors please weigh in on this topic?
I have left some wording nits in a PR to the BIP repository. I have also played with the new format by porting my recent Consensus Cleanup BIP draft to BIP3. As the changes were minimal, i also ported the Miniscript BIP by pretending it was Final. If anyone's curious the diff is available here: https://github.com/darosior/bips/pull/1.
So.. tested ACK, i guess?
Best,
Antoine
On Tuesday, March 18th, 2025 at 10:38 PM, Murch murch@murch•one wrote:
> Dear colleagues,
>
> BIP3 got merged as Draft on the 20th of February and got one more minor
> update since then. I haven’t received any further input in over three
> weeks, so it seems to me that BIP3 is complete and may be ready for
> adoption. I recommend that it be advanced to Proposed here:
> https://github.com/bitcoin/bips/pull/1794
>
> Please let me know if you have any more review comments, suggestions, or
> concerns either here, on the linked pull request, or by email.
>
> Thanks,
> Murch
>
> On 2025-02-03 11:11, Murch wrote:
>
>> Hey everyone,
>>
>> I have been working on an update to the BIP Process. After drafting in
>> my own repository for some months, I opened a pull request to the BIPs
>> Repository in early December. The proposal has gone through two more
>> rounds of review since then and was assigned BIP 3 in early January. I
>> have concluded my planned work on the proposal.
>>
>> If you are interested in the BIP Process, I would appreciate your
>> review. Please share your suggestions and concerns, or raise issues that
>> you would like to see addressed before the proposal is merged or
>> activated. Please also feel free to state your support on the PR, if you
>> are so inclined after your review.
>>
>> You can find the proposal here: https://github.com/bitcoin/bips/pull/1712
>>
>> Thanks,
>> Murch
>
> --
> 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/458a5831-a1a2-4c21-ab61-dccd00ed5219%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/d0-uma6EazZZ4vpFmYf8Xk3iKIHPSL9yriDE1HMvFG1ZC-MNMYo5shsw-MFUYesT2XE3Nt3nutjWGPpHnbWK0dFAKKSiAlijmb0nGogD_NE%3D%40protonmail.com.
[-- Attachment #2: Type: text/html, Size: 4105 bytes --]
prev parent reply other threads:[~2025-03-28 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 19:11 [bitcoindev] " Murch
2025-03-19 2:38 ` [bitcoindev] " Murch
2025-03-28 17:21 ` 'Antoine Poinsot' via Bitcoin Development Mailing List [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='d0-uma6EazZZ4vpFmYf8Xk3iKIHPSL9yriDE1HMvFG1ZC-MNMYo5shsw-MFUYesT2XE3Nt3nutjWGPpHnbWK0dFAKKSiAlijmb0nGogD_NE=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=darosior@protonmail$(echo .)com \
--cc=murch@murch$(echo .)one \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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