From: Peter Todd <pete@petertodd•org>
To: alicexbt <alicexbt@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Anthony Towns <aj@erisian•com.au>
Subject: Re: [bitcoin-dev] BIP process friction
Date: Thu, 18 Jan 2024 17:42:03 +0000 [thread overview]
Message-ID: <Zali61MYQBz/cLbY@petertodd.org> (raw)
In-Reply-To: <jukOxw5FcU6syw4uF2sbFIMPK0RN1nUbUmu5G4zG4w5ZoU2gLOB2vGwHZ3_vEYyJQUQQDIc3w-C0t1anDDAz1tTry6-nCjG5a3nttuoARQc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
On Thu, Jan 18, 2024 at 04:47:33PM +0000, alicexbt via bitcoin-dev wrote:
> Hi AJ,
>
> I like the idea and agree with everything you shared in the email except one thing:
>
> > So I'm switching inquisition over to having a dedicated "IANA"-ish
> > thing that's independent of BIP process nonsense. It's at:
> >
> > * https://github.com/bitcoin-inquisition/binana
>
> I think "authority" is a strong word especially in bitcoin and this process could even work with BINN (Bitcoin Inquisition Numbers And Names). IANA (a function of ICANN) is different thing altogether which was founded by US government.
Bitcoin Inquisition is based on signet, which is a centralized blockchain for
testing run by a central authority whose consensus is based on signatures from
that authority. Using the term "authority" in this context is fine.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-18 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 2:42 Anthony Towns
2024-01-17 6:55 ` Christopher Allen
2024-01-17 16:45 ` Luke Dashjr
2024-01-17 17:29 ` Michael Folkson
2024-01-18 18:00 ` Peter Todd
2024-01-19 19:27 ` Michael Folkson
2024-01-18 15:41 ` David A. Harding
2024-01-19 0:46 ` Anthony Towns
2024-01-19 2:33 ` Karl-Johan Alm
2024-01-18 16:47 ` alicexbt
2024-01-18 17:42 ` Peter Todd [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=Zali61MYQBz/cLbY@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=aj@erisian$(echo .)com.au \
--cc=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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