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
|
Return-Path: <aj@erisian.com.au>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 1BE25C0037
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Jan 2024 02:43:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id D844C613B6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Jan 2024 02:43:02 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org D844C613B6
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id Vj3cPgHlow-i
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Jan 2024 02:43:02 +0000 (UTC)
Received: from cerulean.erisian.com.au (azure.erisian.com.au [172.104.61.193])
by smtp3.osuosl.org (Postfix) with ESMTPS id C7CE761350
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 17 Jan 2024 02:43:01 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org C7CE761350
Received: from aj@azure.erisian.com.au
by cerulean.erisian.com.au with esmtpsa (TLS1.3) tls
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2)
(envelope-from <aj@erisian.com.au>) id 1rPvtI-0000tv-Vj
for bitcoin-dev@lists.linuxfoundation.org; Wed, 17 Jan 2024 12:42:59 +1000
Received: by email (sSMTP sendmail emulation); Wed, 17 Jan 2024 12:42:52 +1000
Date: Wed, 17 Jan 2024 12:42:52 +1000
From: Anthony Towns <aj@erisian.com.au>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <Zac+rMC/c+qTmSxY@erisian.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Spam_score: -0.0
X-Spam_bar: /
Subject: [bitcoin-dev] BIP process friction
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: Wed, 17 Jan 2024 02:43:03 -0000
Hi all,
Just under three years ago there was some discussion about the BIPs repo,
with the result that Kalle became a BIPs editor in addition to Luke, eg:
* https://gnusha.org/bitcoin-core-dev/2021-04-22.log
* https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-April/018859.html
It remains, however, quite hard to get BIPs merged into the repo, eg
the following PRs have been open for quite some time:
* #1408: Ordinal Numbers; opened 2023-01-21, editors comments:
Kalle:
https://github.com/bitcoin/bips/pull/1408#issuecomment-1421641390
https://github.com/bitcoin/bips/pull/1408#issuecomment-1435389476
Luke:
https://github.com/bitcoin/bips/pull/1408#issuecomment-1429146796
https://github.com/bitcoin/bips/pull/1408#issuecomment-1438831607
https://github.com/bitcoin/bips/pull/1408#issuecomment-1465016571
* #1489: Taproot Assets Protocol; opened 2023-09-07, editors comments:
Kalle: https://github.com/bitcoin/bips/pull/1489#issuecomment-1855079626
Luke: https://github.com/bitcoin/bips/pull/1489#issuecomment-1869721535j
* #1500: OP_TXHASH; opened 2023-09-30, editors comments:
Luke:
https://github.com/bitcoin/bips/pull/1500#pullrequestreview-1796550166
https://twitter.com/LukeDashjr/status/1735701932520382839
The range of acceptable BIPs seems to also be becoming more limited,
such that mempool/relay policy is out of scope:
* https://github.com/bitcoin/bips/pull/1524#issuecomment-1869734387
Despite having two editors, only Luke seems to be able to assign new
numbers to BIPs, eg:
* https://github.com/bitcoin/bips/pull/1458#issuecomment-1597917780
There's also been some not very productive delays due to the editors
wanting backwards compatibility sections even if authors don't think
that's necessary, eg:
* https://github.com/bitcoin/bips/pull/1372#issuecomment-1439132867
Even working out whether to go back to allowing markdown as a text format
is a multi-month slog due to process confusion:
* https://github.com/bitcoin/bips/pull/1504
Anyway, while it's not totally dysfunctional, it's very high friction.
There are a variety of recent proposals that have PRs open against
inquisition; up until now I've been suggesting people write a BIP, and
have been keying off the BIP number to signal activation. But that just
seems to be introducing friction, when all I need is a way of linking
an arbitrary number to a spec.
So I'm switching inquisition over to having a dedicated "IANA"-ish
thing that's independent of BIP process nonsense. It's at:
* https://github.com/bitcoin-inquisition/binana
If people want to use it for bitcoin-related proposals that don't have
anything to do with inquisition, that's fine; I'm intending to apply the
policies I think the BIPs repo should be using, so feel free to open a PR,
even if you already know I think your idea is BS on its merits. If someone
wants to write an automatic-merge-bot for me, that'd also be great.
If someone wants to reform the BIPs repo itself so it works better,
that'd be even better, but I'm not volunteering for that fight.
Cheers,
aj
(It's called "numbers and names" primarily because that way the acronym
amuses me, but also in case inquisition eventually needs an authoritative
dictionary for what "cat" or "txhash" or similar terms refer to)
|
