From: Peter Todd <pete@petertodd.org>
To: Tim Ruffing <crypto@timruffing.de>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ordinals BIP PR
Date: Thu, 26 Oct 2023 22:05:30 +0000 [thread overview]
Message-ID: <ZTriqvhah23jBSFW@petertodd.org> (raw)
In-Reply-To: <5f1ba40e6b853851112652b0da8eb7d35369af82.camel@timruffing.de>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On Mon, Oct 23, 2023 at 06:32:47PM +0200, Tim Ruffing wrote:
> On Mon, 2023-10-23 at 15:35 +0000, Peter Todd via bitcoin-dev wrote:
> > Thus
> > we should limit BIP assignment to the minimum possible: _extremely_
> > widespread
> > standards used by the _entire_ Bitcoin community, for the core
> > mission of
> > Bitcoin.
>
> BIPs are Bitcoin Improvement *Proposals*. What you suggest would imply
BIPs being proposals is itself part of the problem. Note how RFCs have a Draft
RFC system to avoid giving numbers for absolutely every idea.
> that someone needs to evaluate them even before they become proposals.
> And this raises plenty of notoriously hard to answers questions:
> * Who is in charge?
> * How to predict if a proposal will be a widespread standard?
> * What is the core mission of Bitcoin?
> * How to measure if something is for the core mission?
> * Who and what is the _entire_ Bitcoin community?
...and we still face those problems with the current BIPs system. In particular
the "Who is in charge?" problem. BIPs are always going to be a centralized
system.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-26 22:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 5:38 [bitcoin-dev] Ordinals BIP PR Casey Rodarmor
2023-10-23 13:45 ` Andrew Poelstra
2023-10-23 15:35 ` Peter Todd
2023-10-23 16:32 ` Tim Ruffing
2023-10-26 22:05 ` Peter Todd [this message]
2023-10-23 17:43 ` Andrew Poelstra
2023-10-23 18:29 ` Luke Dashjr
2023-10-24 1:28 ` alicexbt
2023-10-24 22:56 ` Olaoluwa Osuntokun
2023-10-24 23:08 ` Christopher Allen
2023-10-25 0:15 ` Luke Dashjr
2023-10-26 22:11 ` Peter Todd
2023-10-27 9:39 ` Alexander F. Moser
2023-10-27 17:05 ` alicexbt
2023-11-09 2:15 ` Casey Rodarmor
2023-11-09 22:32 ` Claus Ehrenberg
2023-10-23 14:57 Léo Haf
2023-10-23 17:26 ` Ryan Breen
2023-11-20 22:20 vjudeu
2023-11-21 12:13 ` Kostas Karasavvas
2023-11-21 23:10 vjudeu
2023-11-22 11:27 ` Kostas Karasavvas
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=ZTriqvhah23jBSFW@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=crypto@timruffing.de \
/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