Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id A2DDFC0032 for ; Mon, 23 Oct 2023 15:05:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 7D69282540 for ; Mon, 23 Oct 2023 15:05:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 7D69282540 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=orangepill.ovh header.i=@orangepill.ovh header.a=rsa-sha256 header.s=sig1 header.b=M7V2hLaR X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.796 X-Spam-Level: X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QwrEyPFKNhtj for ; Mon, 23 Oct 2023 15:05:45 +0000 (UTC) X-Greylist: delayed 476 seconds by postgrey-1.37 at util1.osuosl.org; Mon, 23 Oct 2023 15:05:44 UTC DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org EC0A08133F Received: from qs51p00im-qukt01080502.me.com (qs51p00im-qukt01080502.me.com [17.57.155.23]) by smtp1.osuosl.org (Postfix) with ESMTPS id EC0A08133F for ; Mon, 23 Oct 2023 15:05:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orangepill.ovh; s=sig1; t=1698073065; bh=ZjxRyjm2QuU7C0zbh5YGJGNWpfxAogx+DuG2Ml4B7WU=; h=Content-Type:From:Mime-Version:Subject:Message-Id:Date:To; b=M7V2hLaR26NTrWwwuKU+UPkUfsGY++nWZK5JXcFnz/wY44UXqxLFa/7EfvDP4OQEK ep68EKm6mTakIgRYtGu13ZYmsac9bbCGrecrSj8Pb1AQ/jUp1HvHKf8OS6NMVNuGp6 V8qG85COfoCtitX6YqQknc0OVU4A8UfL6G5kteSohvoYPtUCltru6/ZPTFMOjc6Hx3 FSRCW1C1svs3NIqxOxLTKm2Cn9ZtrHjoQXhvZNKCA14LbgUwoYT4sd83xSyvy/GWY4 N8gPOTjH4rlzJ07nccC4edpxs1uaKKlw+zhxGt8rTQVFItXuZ/s6hEn66KEL4vxhNU 9wBjkBa9DLTIg== Received: from smtpclient.apple (qs51p00im-dlb-asmtp-mailmevip.me.com [17.57.155.28]) by qs51p00im-qukt01080502.me.com (Postfix) with ESMTPSA id E9BD24E40247; Mon, 23 Oct 2023 14:57:44 +0000 (UTC) Content-Type: multipart/alternative; boundary=Apple-Mail-A645869C-59A4-41B5-BD15-124082163A23 Content-Transfer-Encoding: 7bit From: =?utf-8?Q?L=C3=A9o_Haf?= Mime-Version: 1.0 (1.0) Message-Id: Date: Mon, 23 Oct 2023 16:57:32 +0200 To: Casey Rodarmor , Bitcoin Protocol Discussion X-Mailer: iPhone Mail (21A360) X-Proofpoint-ORIG-GUID: Lg8VVPNhn9WMSoURnJ2JWS-4kAePHrpU X-Proofpoint-GUID: Lg8VVPNhn9WMSoURnJ2JWS-4kAePHrpU X-Proofpoint-Virus-Version: =?UTF-8?Q?vendor=3Dfsecure_engine=3D1.1.170-22c6f66c430a71ce266a39bfe25bc?= =?UTF-8?Q?2903e8d5c8f:6.0.138,18.0.790,17.0.605.474.0000000_definitions?= =?UTF-8?Q?=3D2022-01-12=5F02:2020-02-14=5F02,2022-01-12=5F02,2020-01-23?= =?UTF-8?Q?=5F02_signatures=3D0?= X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 phishscore=0 spamscore=0 mlxscore=0 clxscore=1030 mlxlogscore=999 adultscore=0 suspectscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2310230130 X-Mailman-Approved-At: Mon, 23 Oct 2023 16:49:28 +0000 Subject: Re: [bitcoin-dev] Ordinals BIP PR X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2023 15:05:49 -0000 --Apple-Mail-A645869C-59A4-41B5-BD15-124082163A23 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =EF=BB=BF BIPs such as the increase in block size, drives-chains, colored co= ins, etc... were proposals for Bitcoin improvements. On the other hand, your= BIP brings absolutely no improvement, on the contrary it is a regression, b= ut you already know that. I strongly invite you to retract or if the desire continues to push you to n= egatively affect the chain, to create OIPs or anything similar, as far as po= ssible from the development of Bitcoin and real BIPs that improve Bitcoin. L=C3=A9o Haf.=20 > Le 23 oct. 2023 =C3=A0 10:23, Casey Rodarmor via bitcoin-dev a =C3=A9crit : > =EF=BB=BF > Dear List, >=20 > The Ordinals BIP PR has been sitting open for nine months now[0]. I've com= mented a few times asking the BIP editors to let me know what is needed for t= he BIP to either be merged or rejected. I've also reached out to the BIP edi= tors via DM and email, but haven't received a response. >=20 > There has been much misunderstanding of the nature of the BIP process. BIP= S, in particular informational BIPs, are a form of technical documentation, a= nd their acceptance does not indicate that they will be included in any impl= ementation, including Bitcoin Core, nor that they they have consensus among t= he community. >=20 > Preexisting BIPs include hard-fork block size increases, hard-fork proof-o= f-work changes, colored coin voting protocols, rejected soft fork proposals,= encouragement of address reuse, and drivechain. >=20 > I believe ordinals is in-scope for a BIP, and am hoping to get the PR unst= uck. I would appreciate feedback from the BIP editors on whether it is in-sc= ope for a BIP, if not, why not, and if so, what changes need to be made for i= t to be accepted. >=20 > Best regards, > Casey Rodarmor >=20 > [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 --Apple-Mail-A645869C-59A4-41B5-BD15-124082163A23 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
=EF=BB=BF BIPs such a= s the increase in block size, drives-chains, colored coins, etc... were prop= osals for Bitcoin improvements. On the other hand, your BIP brings absolutel= y no improvement, on the contrary it is a regression, but you already know t= hat.

I strongly invite you to ret= ract or if the desire continues to push you to negatively affect the chain, t= o create OIPs or anything similar, as far as possible from the development o= f Bitcoin and real BIPs that improve Bitcoin.

L=C3=A9o Haf. 

Le 23 oct. 2023 =C3=A0 10:23, Casey Ro= darmor via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> a =C3=A9= crit :

=EF=BB=BF
Dear List,

The Ordinal= s BIP PR has been sitting open for nine months now[0]. I've commented a few t= imes asking the BIP editors to let me know what is needed for the BIP to eit= her be merged or rejected. I've also reached out to the BIP editors via DM a= nd 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 accept= ance does not indicate that they will be included in any implementation, inc= luding Bitcoin Core, nor that they they have consensus among the community.<= /div>

Preexisting BIPs include hard-fork block size increases, hard-for= k proof-of-work changes, colored coin voting protocols, rejected soft fork p= roposals, encouragement of address reuse, and drivechain.

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"= >I believe ordinals is in-scope for a BIP, and am hoping to get the PR unstu= ck. I would appreciate feedback from the BIP editors on whether it is in-sco= pe for a BIP, if not, why not, and if so, what changes need to be made for i= t to be accepted.

Best regards,
Casey Rodarmor
=
[0] https://github= .com/bitcoin/bips/pull/1408
_______________________________________________
bitcoi= n-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<= /span>
= --Apple-Mail-A645869C-59A4-41B5-BD15-124082163A23--