From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0FE72C0032 for ; Sat, 21 Oct 2023 05:38:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id D6DC0401E1 for ; Sat, 21 Oct 2023 05:38:19 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D6DC0401E1 Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key) header.d=rodarmor.com header.i=@rodarmor.com header.a=rsa-sha256 header.s=google header.b=HOdOfN0/ X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58LY3BaOYZNY for ; Sat, 21 Oct 2023 05:38:15 +0000 (UTC) Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by smtp2.osuosl.org (Postfix) with ESMTPS id 57527400C8 for ; Sat, 21 Oct 2023 05:38:15 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 57527400C8 Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-53dd3f169d8so2147186a12.3 for ; Fri, 20 Oct 2023 22:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rodarmor.com; s=google; t=1697866693; x=1698471493; darn=lists.linuxfoundation.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=w/P2255819zKn7CsuhmvVQVywqMwcdlAsVpOpiepkJs=; b=HOdOfN0/0lPp4/L1+5ag2aRIjsyvf27U8GtQPqqslI25jUcJEFrUJEoHVJfOkFlnR7 19SXAEkwsOqI5ZwzObqUhA8I5nlQbaYVeV9YE1/+vMUGejr7KtQZ2eL5ajTrRzCO2pCs IcIE4BOH64PW18wfpj76ClLz9bLQxpZTwUmQm01EHB8NSXgqyFH8BemWehZlDNhb/wFT XAN/ByljdbgwcyiZFYCmBOiwl3ch3hX+PyReO3brbiPVBO1mKekFBgIdNRXDVGBOMJT5 +whud+8Ghe3+coCOLRaBMLd1IPRNgzyYchlZD08Dto7x0rGvGo0wVPEvwsBqaDjycj0P YXjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697866693; x=1698471493; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=w/P2255819zKn7CsuhmvVQVywqMwcdlAsVpOpiepkJs=; b=ePWtvIoyA+KX+avfCiRbV731Yt7vYJnHZl6xEpcdVs5dMIJMc8OzG4IJ+bztzSBKsL wuW4W1jJ52qSpcQUVvYdgsVR/sMstrQyacacdhK6Hkzgklk8Y9///H9zUa8Qmj+GJbbV Pede65nyEYNxXGWz+5WjYclTO8icE5K8JluJ+6yaDIlJNyk5DekepNu782ey4zkJpbcz 2ykNLxFCwTnHZfVt6Y79x8C7MJ4QW7SiLMtedWVh5ML6iyLj2aMQ+lWVRzy4o6F0/efv 6On8LT5h05zmHNmGJojBG/f+ECTUIVsiBTuwDwy0panDw2p22mAYurHYTPUCkVFqCyOR 77BQ== X-Gm-Message-State: AOJu0YySp1rldJZReuoosFXGMtvgsA+FIFlDBRXZahjz8iSKTD1yT468 gMdfC8j3edYNFx7DsAnE0y1k7cDPULChfjNGPIH8UGSxZHPi2nrs2uA= X-Google-Smtp-Source: AGHT+IFv51gzI3JOE+I6zh3+CJIgjPMjJuCQiIBjjHo7KrGod6/S3nz/V8dHdpnoBsq0fk/PMyN+WEl9D2G+OIccB1g= X-Received: by 2002:a05:6402:2694:b0:53e:a9bd:508 with SMTP id w20-20020a056402269400b0053ea9bd0508mr3235535edd.25.1697866692822; Fri, 20 Oct 2023 22:38:12 -0700 (PDT) MIME-Version: 1.0 From: Casey Rodarmor Date: Fri, 20 Oct 2023 22:38:01 -0700 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000001a1e5506083365dc" X-Mailman-Approved-At: Mon, 23 Oct 2023 08:23:24 +0000 Subject: [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: Sat, 21 Oct 2023 05:38:20 -0000 --0000000000001a1e5506083365dc Content-Type: text/plain; charset="UTF-8" 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 --0000000000001a1e5506083365dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear List,

The Ordinals BIP P= R has been sitting open for nine months now[0]. I've commented a few ti= mes 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 and email, but haven't received a response.

Th= ere has been much misunderstanding of the nature of the BIP process. BIPS, = in particular informational BIPs, are a form of technical documentation, an= d their acceptance does not indicate that they will be included in any impl= ementation, including Bitcoin Core, nor that they they have consensus among= the community.

Preexisting BIPs include hard-fork block size i= ncreases, hard-fork proof-of-work changes, colored coin voting protocols, r= ejected soft fork proposals, encouragement of address reuse, and drivechain= .

I believe ordinals is in-scope for a BIP, and am hop= ing 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 chan= ges need to be made for it to be accepted.

Best regard= s,
Casey Rodarmor

[0] https://github.com/bitcoin/bips/pull/1408
--0000000000001a1e5506083365dc--