summaryrefslogtreecommitdiff
path: root/78/922b2b9ba7b6c6fdc8782f36b6031884d05592
blob: 0331d490727a8304ba5f80be9e78d830511604ff (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
Return-Path: <casey@rodarmor.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 0FE72C0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 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 <bitcoin-dev@lists.linuxfoundation.org>;
 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 <bitcoin-dev@lists.linuxfoundation.org>;
 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 <bitcoin-dev@lists.linuxfoundation.org>;
 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 <bitcoin-dev@lists.linuxfoundation.org>;
 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 <casey@rodarmor.com>
Date: Fri, 20 Oct 2023 22:38:01 -0700
Message-ID: <CANLPe+OQBsPiTrLEfz=SMxU8TkM_1XNfJQeq8gt2V6vDu=+Zxw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Dear List,<br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif">The Ordinals BIP P=
R has been sitting open for nine months now[0]. I&#39;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&#39;ve also reached out to the BIP editors via=
 DM and email, but haven&#39;t received a response.</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">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.</div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif"><br>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=
.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif">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.</div><div class=3D"gmail_default=
" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif">Best regard=
s,</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif">Casey Rodarmor<br><br>[0] <a href=3D"https://github.com/bitcoin/=
bips/pull/1408">https://github.com/bitcoin/bips/pull/1408</a><br></div></di=
v>

--0000000000001a1e5506083365dc--