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
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
|
Delivery-date: Mon, 13 May 2024 12:05:32 -0700
Received: from mail-oi1-f187.google.com ([209.85.167.187])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBAABB46IRGZAMGQEABFILAY@googlegroups.com>)
id 1s6azL-0002LU-T1
for bitcoindev@gnusha.org; Mon, 13 May 2024 12:05:32 -0700
Received: by mail-oi1-f187.google.com with SMTP id 5614622812f47-3c9abbb9f02sf1070913b6e.0
for <bitcoindev@gnusha.org>; Mon, 13 May 2024 12:05:31 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1715627125; cv=pass;
d=google.com; s=arc-20160816;
b=ujjhryHd2nywVGDHnyIRlcmznGg/ZiXXnyAjP2GnCmypi0aQ1S2pVpCcErWDPNKm2a
nvwqTOSTqeqPwJtRPLLJItDNJylMtuqDfRAGw4gHH3bnMBQ+gjEdC9xA8jYX/LYiCywX
DCqw7IOUsrD47LTGD3RDzu+m6JJtRUC6SW2KqELjo1DGQ8ygTmJXC8/y7vxymk2qwKn+
jVGTDCsD+Mg/U6+qZrgaGlBN5pSK+Le6qlXT5BnJ0vXbqn/+b4fRnkAxg8QUInJLzbCZ
oJWrWytBNInI6yoCwazWTXSzLFLLg/plXvh63dLlBeo96EEAPGz3qTSJEmgCWzd7nMdw
8Daw==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:content-transfer-encoding
:in-reply-to:content-language:references:to:subject:from:user-agent
:mime-version:date:message-id:sender:dkim-signature;
bh=kT/Mgh+VsWSxbEWRjqlZlA1cDAROLcLvYJix32JH6m0=;
fh=6vlFcPczPJojq3ay2c6eKfBAWINIlOg3f2gyQbZPGfc=;
b=bssT7n+hso+It7KK0Am4Bi7U20K3c/Yf6D5pjbVXDg23D+wwiGgiz+c4GCYpiqI+Qx
egxD7vMcNgjy5kVaPdwyLGT0JuRSx4uXbvg1Y1+jRTDbj1uepwdmQkN3wCn6g2CGoUiB
NsxIrwwuD6VdYvu7gyPUCe4cShdloouJIIHbm1gnemSMRikFD3w0lHDcqrQDc+Ke8Viq
i3KLVfXMBqeUySI8V7TgMFFMPtjDwRvXIfTnBXk5BnPb+RZGbRRxwGG1OqlRUP3xx0n5
02NuuG15bmwtitZnKCA6/YtCgmZhXj3k141elrTHaNfpb5jHKDapFiA68BwEQRX4IeQH
vs+g==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@murch.one header.s=uberspace header.b=vjJq+rDO;
spf=pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) smtp.mailfrom=murch@murch.one
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1715627125; x=1716231925; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding:in-reply-to
:content-language:references:to:subject:from:user-agent:mime-version
:date:message-id:sender:from:to:cc:subject:date:message-id:reply-to;
bh=kT/Mgh+VsWSxbEWRjqlZlA1cDAROLcLvYJix32JH6m0=;
b=hIO8Swa/zf8pE1n8vQua/uxcVrnu3gSHuWtZQWzmUNUPSNNkf/IC/9/KDtIMn/y6FB
PirFIs1wmTeMHoE8QOFt5anAeCXUZM8/RN5Mbt8x6HfolTfear5Etjp7ecytWwIYORBA
fto5kCq0sSUealwbGRhZ54qr09vSlav2nh/UPeYIkeVVrmSA76bbv4SvH/N8pCpjnqhV
c6wiIQ1mU4SIS8Yqttj010Ny9SocjtQxgIq6lhX5bRMc1l1GPvYn8MEk+O0zXEMUOeum
HyBoaJqlL7EfmlkbMZC8A2n4iIEvzODcDc7H2P7GxvzgLaNILagL9Psmn+ujtay4qKHc
XOOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1715627125; x=1716231925;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding:in-reply-to
:content-language:references:to:subject:from:user-agent:mime-version
:date:message-id:x-beenthere:x-gm-message-state:sender:from:to:cc
:subject:date:message-id:reply-to;
bh=kT/Mgh+VsWSxbEWRjqlZlA1cDAROLcLvYJix32JH6m0=;
b=eBr7ra/s8yEafqGm+ubwdPTTfCPgqggR/GSpzGEvInVg9PbXrH/m2DwJyPdrztXHbU
YVTIDQxTM46PNj25ZH/DLJ7AZpnlu71YwwrNix0/tb+Jnb/ZFI4LKco1IKrJNbBxXTxD
NNCs6gygNZDSsOE6H90tW0v5GD/iS6kajlzfaChQBlU0ul13REtjzTf4kGLCBfjkDPfX
X++XtpJ6Q6XBdb0iDDn/eyUcuA6Kolqgashk8SwEPPTpe2Qbu+hs3b7VCa5BPE6fOgOO
hX2V0XiRjHPK6EEkF/DbQ1rQDGJ/XUN9yK4AbbrRNYS+OUCfO8MCLaItNk6zxuxfUm/I
Fa0Q==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCVOmqCQWndWGuinAGxFROTh2aFkplnyhIEOAqZwKF+uTEEN1ZwIIpZ5c/vb8qYn1wbzcQpCPMjL5UdXitYlVEIRQOgQvpw=
X-Gm-Message-State: AOJu0Yw+tYhwjiCX6MVCIcMV4XG7zIYrBKlhnM0NwBTIlwPgGVmE3vJQ
AvW8Buf5pJUiSRWE+b11vpbKnRYKCTO2G1y++V5TWf6UEpp6TLcZ
X-Google-Smtp-Source: AGHT+IH55jvTjxbU1OzIxTnsskdxHOczAXGC8A9aESAKdK85Q6V17YHtR8p0aattprBXKIFj3XDlWQ==
X-Received: by 2002:a05:6808:170c:b0:3c9:a316:d522 with SMTP id 5614622812f47-3c9a316d986mr7607314b6e.25.1715627125375;
Mon, 13 May 2024 12:05:25 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:6214:252e:b0:698:ed81:bc0e with SMTP id
6a1803df08f44-6a15d445a8fls51293126d6.1.-pod-prod-06-us; Mon, 13 May 2024
12:05:23 -0700 (PDT)
X-Received: by 2002:a05:6214:27e9:b0:6a0:b4ff:4551 with SMTP id 6a1803df08f44-6a16815b441mr1637406d6.6.1715627123633;
Mon, 13 May 2024 12:05:23 -0700 (PDT)
Received: by 2002:a05:620a:190f:b0:790:ee24:5a3f with SMTP id af79cd13be357-792bcb6ec4ems85a;
Mon, 13 May 2024 11:34:00 -0700 (PDT)
X-Received: by 2002:a05:600c:4e88:b0:420:1551:96ab with SMTP id 5b1f17b1804b1-42015519952mr31843755e9.10.1715625239408;
Mon, 13 May 2024 11:33:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1715625239; cv=none;
d=google.com; s=arc-20160816;
b=G+S4l4Ckxj0CKUqr3F6QmEevlG6YSKEbXzq1AWmHv892JpEHqU2l9+fHBwdxT/0c+g
pOV4D+R4m3WdLUd++YkHK2sxVufERYxPtejK/hgKs6LtaSpmP4PQKAH6midaaUfoz1H4
0uhQ8LY+yK1/0t9TnvW0LHOX15TznJpE9gn7SNILQMjFH3b/R7Clazgcv9veSlKePSmB
oH0PxLDaUj0Oue2BI5DUB5MCurXmoNJ0CN2G06IyLVrnTkTejwNwZ9mO3Hhwl6RFBSfX
fxu+ymLUC0GcHYQ0EADZMcDdDExDQ1pJDQD6aYZnBbJPibo2iqtjgXFj5ssaFSp5B7Us
fkVw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=dkim-signature:content-transfer-encoding:in-reply-to
:content-language:references:to:subject:from:user-agent:mime-version
:date:message-id;
bh=wAspUbT/ewo9zrRhUI9pv865pbGx2oIP0dRljtq3nFU=;
fh=VcGcg+Zjs9gw1uDcHbxsAILhBAcecnbJzZRdxgKVDIc=;
b=y9HJrpsTkXoC7iIWciuH6ae5MJlVo4pk79P3LLDCqQrtsG6Lib8yni4h3/FxtNQvQz
gOUGLmaj4ZaMJefXKzXo/6JXIegZ66WG/pN5hC8scy+4liSdkGSulsUcnbFHTna9Cxh5
4z50gDpjMMt53NpA681fAL1589HAsS0/rqh7MuBaNE3sSs4PYdZMiIppEpfZEUN/YEA7
2MDcPg4yqFF1kILDkTivWnEeIzGYFzoO6so5J9MewRGQnbgxuKFZe39gkz9FnsCgLjrT
XAbcD54EzocsGD8v4zLPVOWJs62Y0euYkcaNrZByeo3agUn4o2tGTtVhk1K4lEl6R32z
XWYA==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@murch.one header.s=uberspace header.b=vjJq+rDO;
spf=pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) smtp.mailfrom=murch@murch.one
Received: from farbauti.uberspace.de (farbauti.uberspace.de. [185.26.156.235])
by gmr-mx.google.com with ESMTPS id 5b1f17b1804b1-41fdfe566easi6023535e9.1.2024.05.13.11.33.59
for <bitcoindev@googlegroups.com>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Mon, 13 May 2024 11:33:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) client-ip=185.26.156.235;
Received: (qmail 26365 invoked by uid 989); 13 May 2024 18:33:59 -0000
Received: from unknown (HELO unkown) (::1)
by farbauti.uberspace.de (Haraka/3.0.1) with ESMTPSA; Mon, 13 May 2024 20:33:58 +0200
Message-ID: <0bc47189-f9a6-400b-823c-442974c848d5@murch.one>
Date: Mon, 13 May 2024 14:33:57 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Murch <murch@murch.one>
Subject: Re: [bitcoindev] Time for an update to BIP2?
To: bitcoindev@googlegroups.com
References: <e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.com>
<9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
<42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
<d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com>
<52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
<f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcorallo.com>
<ZgWRu32FXzqqg69V@console>
<9ebd08b0-7680-4896-aad3-1c225b764bcb@mattcorallo.com>
<59fa94cea6f70e02b1ce0da07ae230670730171c.camel@timruffing.de>
<4pVUOTuyyAbTJB_rTGNWS_TuR39NS5OoJvaSCyqjezAg265kPnCjXvqohFmWQ5ITb7XFZCJie-uV1AG3pVCI5H54dDuFP4OyomC9yiWDot0=@wuille.net>
<Zg4z7P+MKzEfCkdM@erisian.com.au>
Content-Language: en-US
In-Reply-To: <Zg4z7P+MKzEfCkdM@erisian.com.au>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Rspamd-Bar: --
X-Rspamd-Report: BAYES_HAM(-3) XM_UA_NO_VERSION(0.01) SUBJECT_ENDS_QUESTION(1) MIME_GOOD(-0.1)
X-Rspamd-Score: -2.09
X-Original-Sender: murch@murch.one
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@murch.one header.s=uberspace header.b=vjJq+rDO; spf=pass
(google.com: domain of murch@murch.one designates 185.26.156.235 as permitted
sender) smtp.mailfrom=murch@murch.one
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)
Hey everyone,
I have spent some time going over comments about the BIP process in this=20
thread and a few open pull requests in the BIPs repository. Thank you=20
all for sharing your thoughts.
Below I summarized suggestions from those conversations. I started work=20
on drafting a proposal to succeed BIP-2 and will consider all these=20
suggestions with the intention of incorporating many of them.
If you are interested in collaborating on an updated Process BIP, I am=20
open to one or two co-authors. I will also consider any further comments=20
here on the mailing list, and look forward to the eventual review from=20
any interested parties. I will start a first draft in my own BIPs=20
repository after this email. Once the proposal is a bit more mature, I=20
will open a pull request against the main BIPs repository.
These are my take-aways and open questions so far:
1. Process
What should the role of the editors be?
- The process should minimize judgment calls from editors
- Editors should focus on formal criteria and editorial qualities
- The audience rather than editors should evaluate technical soundness
What criteria distinguish Standards Track and Informational type BIPs?
- If deviation breaks compatibility, it should be "Standards Track"
Open questions:
- What changes to BIPs are acceptable at what stage of the process?
- Which changes need sign-off from the Champion?
- How can we make the process more robust in face of an absent Champion?
2. BIP Statuses
- Excessive count of statuses
- Meaning of statuses should be more clearly defined
- Criteria for status transitions should be clarified
- There have been multiple recommendations to reduce the statuses to:
DRAFT, PROPOSED, WITHDRAWN, with some disagreement on whether ACTIVE or=20
FINAL would be useful in addition
- Get rid of the REJECTED status and drop the rule to move proposals to=20
REJECTED due to time passing
Open questions:
- Is it a problem if a BIP is stuck in "DRAFT" or "PROPOSED" indefinitely?
3. Other format issues
- Comments and Comment Summary are largely being ignored, they do not=20
seem to fulfill their intended purpose
- Backwards compatibility section is often forgotten
- Remove "Other Implementations" sections from documents
- Some suggested licenses may not be acceptable to license plain text
4. Scope of the Repository
- Only accept proposals that pass some bar of interest
- Require "a need for standardization", it must be relevant to multiple=20
implementations or a broader audience
- Clarify purpose of repository; it is often misunderstand in how far=20
BIPs "represent community consensus or recommendations"
- Focus on the proposals, explicitly stop guessing at acceptance and=20
tracking of adoption
Open questions:
- Both a tightening and a broadening of the scope have been suggested:
Do BIPs need to be "related to the Bitcoin ecosystem", "related to=20
technology that supports the bitcoin currency", or some other criterion?
- What does "keeping with the Bitcoin philosophy" mean?
- Where should adoption of BIPs be tracked? Should the BIPs repository=20
offer an overview of BIP implementations separate from the author documents=
?
If you have input on open questions, or alternative suggestions to the=20
summarized points, please let me know. As Tim before me, I would=20
appreciate that you read BIP-2=C2=B9 carefully before replying.
=C2=B9 https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki
Best,
Murch
--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/0bc47189-f9a6-400b-823c-442974c848d5%40murch.one.
|
