From: Anthony Towns <aj@erisian.com.au>
To: Murch <murch@murch.one>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] BIP 3 and issues on BIPs
Date: Fri, 5 Jun 2026 21:41:14 +1000 [thread overview]
Message-ID: <aiK12iWhAIVierZM@erisian.com.au> (raw)
In-Reply-To: <a00e00b8-b794-4462-a705-0e209120aad4@murch.one>
On Mon, Jun 01, 2026 at 02:24:04PM -0700, Murch wrote:
> I get the concern that in the case of the BIP Owners disagreeing with
> critics about a raised issue or whether it has been addressed
> satisfactorily, the issue may not be recorded in a manner that the critics
> would consider comprehensive.
>
> Maybe directly starting with the summaries would work better than gathering
> comments from random people, but given the low participation in the
> repository I’m still not convinced that there would be significant interest
> in contributing to these summaries. So, I’m still convinced that it would
> most likely become an additional burden for the BIP Editors to collect,
> curate, and referee these submissions, and would probably still be slanted
> to the opinions of a few active participants like in the prior system.
>
> I agree that needing to dig through so many different sources sucks and a
> better system would be better. I’m not sure that just having the BIP Editors
> curate submissions is enough.
>
> I’m gonna mull more on this and would be curious what others have to say.
(In case it wasn't obvious, that's not much different from where I sit:
I think this is an interesting approach worth thinking more about,
but I'm not sure if it's the best approach or even necessarily a good
one. I think it makes pretty good sense for BIP 39 since adding a
"shortcomings" section was previously suggested, and the the current
state of affairs is pretty confusing at best)
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/aiK12iWhAIVierZM%40erisian.com.au.
prev parent reply other threads:[~2026-06-05 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 1:51 [bitcoindev] BIP 3 and issues on BIPs Anthony Towns
2026-05-28 18:28 ` Murch
2026-05-31 7:12 ` Anthony Towns
2026-06-01 21:24 ` Murch
2026-06-01 22:54 ` Murch
2026-06-05 11:41 ` Anthony Towns [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=aiK12iWhAIVierZM@erisian.com.au \
--to=aj@erisian.com.au \
--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