From: "Léo Haf" <leohaf@orangepill.ovh>
To: Casey Rodarmor <casey@rodarmor.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Ordinals BIP PR
Date: Mon, 23 Oct 2023 16:57:32 +0200 [thread overview]
Message-ID: <C61E710C-772F-4473-8FF2-38A47AC0D333@orangepill.ovh> (raw)
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
BIPs such as the increase in block size, drives-chains, colored coins, etc... were proposals for Bitcoin improvements. On the other hand, your BIP brings absolutely no improvement, on the contrary it is a regression, but you already know that.
I strongly invite you to retract or if the desire continues to push you to negatively affect the chain, to create OIPs or anything similar, as far as possible from the development of Bitcoin and real BIPs that improve Bitcoin.
Léo Haf.
> Le 23 oct. 2023 à 10:23, Casey Rodarmor via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> a écrit :
>
> Dear List,
>
> The Ordinals BIP PR has been sitting open for nine months now[0]. I've commented a few times asking the BIP editors to let me know what is needed for the BIP to either be merged or rejected. I've also reached out to the BIP editors via DM and email, but haven't received a response.
>
> There has been much misunderstanding of the nature of the BIP process. BIPS, in particular informational BIPs, are a form of technical documentation, and their acceptance does not indicate that they will be included in any implementation, including Bitcoin Core, nor that they they have consensus among the community.
>
> Preexisting BIPs include hard-fork block size increases, hard-fork proof-of-work changes, colored coin voting protocols, rejected soft fork proposals, encouragement of address reuse, and drivechain.
>
> I believe ordinals is in-scope for a BIP, and am hoping to get the PR unstuck. I would appreciate feedback from the BIP editors on whether it is in-scope for a BIP, if not, why not, and if so, what changes need to be made for it to be accepted.
>
> Best regards,
> Casey Rodarmor
>
> [0] https://github.com/bitcoin/bips/pull/1408
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 3349 bytes --]
next reply other threads:[~2023-10-23 15:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 14:57 Léo Haf [this message]
2023-10-23 17:26 ` [bitcoin-dev] Ordinals BIP PR Ryan Breen
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 23:10 vjudeu
2023-11-22 11:27 ` Kostas Karasavvas
2023-11-20 22:20 vjudeu
2023-11-21 12:13 ` Kostas Karasavvas
2023-10-21 5:38 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
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
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=C61E710C-772F-4473-8FF2-38A47AC0D333@orangepill.ovh \
--to=leohaf@orangepill.ovh \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=casey@rodarmor.com \
/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