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
|
Return-Path: <karljohan-alm@garage.co.jp>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 00043C000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:20:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id DB5E040170
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:20:49 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 1.05
X-Spam-Level: *
X-Spam-Status: No, score=1.05 tagged_above=-999 required=5
tests=[BAYES_50=0.8, HEADER_FROM_DIFFERENT_DOMAINS=0.25,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=no 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 VeiTMNu8Xs0t
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:20:47 +0000 (UTC)
X-Greylist: delayed 00:05:50 by SQLgrey-1.8.0
Received: from mta61.mta.hdems.com (mta61.mta.hdems.com [3.112.23.28])
by smtp2.osuosl.org (Postfix) with ESMTPS id 6271D4015B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:20:47 +0000 (UTC)
Received: from mo.hdems.com (unknown [10.5.20.24])
by mta61.mta.hdems.com ('HDEMS') with ESMTPSA id 4H8VLP5WK7z2K1r93
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:14:53 +0000 (UTC)
X-HDEMS-MO-TENANT: garage.co.jp
Received: from mail-vs1-f72.google.com (mail-vs1-f72.google.com.
[209.85.217.72]) by gwsmtp.prod.mo.hdems.com with ESMTPS id
gwsmtpd-trans-0cdd34e7-8c28-4a81-9e52-b6f2fce52676
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Sep 2021 06:14:49 +0000
Received: by mail-vs1-f72.google.com with SMTP id
i2-20020a67e2c20000b02902bae9a0967fso382599vsm.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Sep 2021 23:14:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=R+xvnfsU0tD23An2bIS+vo8vNULyu0cwq7MwgtuArMk=;
b=j8wJ/UkNXYtHfR2EhY4cKnoGpxSNt3/jQHe5xrj6nIBqeuJSyT6iBNKVSyRe7glW/X
57s9UqF/IPTRFhr+8kXpDJvQzCgrWv0FsSuxDhw2TqZf4gZOq2XRX8CohRA2KmXeKelZ
0KRFnXrz7IGdncE1zrZ3keE3iMFzmYyBKgrpJqVZbX4OUnzctZZ1wWZbHPdez/vAlZEN
DrF0AIvYXPDPIU07XgaCy9U76yemDhGw+x/RKU3u+8vM4vKnKnLJcAMcxw+X248aM/Dm
x810jY18LsnY3h14vet9yzHLhY1fMeXDXi6CQb2z5wubZYASm81vJbIOQiWKzkdR+kd+
ssAw==
X-Gm-Message-State: AOAM532/jQEdCYQ5xW1fT36zW64xcgnVA/cXpdeu+9ee8PwkARfFlQCL
7Sm4b0AoeeMtdYiL+Ln7HvkbO9CDLwU3CSpyz9ixxyTWf10R0FQI3RkchBK7JhZfb4CCdbp2CR/
ZmPyoG6mFhCgNqZ2rAHRYtyb7eAp3shbHuZaFU+furBV5AgeaKol8t6Fuxl9HrkIoU5+VfeV5O8
CAx9MU4PVlwBCtyhSfvgB1qqX06+5CblXE5Gam6v6iZxodtKnoEQMSdTk4HLSNJ5ASHv7aIrZqX
cwUj7zJYJbdZZ6wo49KpdK3GkmNxR4K3dP6GgLduPrOX1qixcKH1fnkNniNNs4oJHfau2F/O+P4
8Jq2SZejxVmMW+OrvtyhUOimd9Ni
X-Received: by 2002:a05:6102:ac6:: with SMTP id
m6mr2178443vsh.55.1631686488127;
Tue, 14 Sep 2021 23:14:48 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJyf1X5jFzIDqeiPOUXQyKlljAltuX723MbYzJLIniXQg9wmLj9OFNi01qIszG6Mtb9lCaHgNPNVHNlCxkRsTJg=
X-Received: by 2002:a05:6102:ac6:: with SMTP id
m6mr2178431vsh.55.1631686487539;
Tue, 14 Sep 2021 23:14:47 -0700 (PDT)
MIME-Version: 1.0
From: Karl-Johan Alm <karl@dglab.com>
Date: Wed, 15 Sep 2021 15:14:31 +0900
Message-ID: <CALJw2w7f2JfskLQPwEBsKTqpJBo+qccP-y6oAX5EEzJ3vo0Grw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Subject: [bitcoin-dev] BIP extensions
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, 15 Sep 2021 06:20:50 -0000
BIPs are proposals.
They begin as ideas, are formulated and discussed on this list, and
assuming no glaring flaws are observed, turned into pull requests to
the bips repository, assigned a BIP number by the editors, and merged.
It is then organically incorporated into the various entities that
exist in the Bitcoin space. At this point, it is not merely a
proposal, but a standard. As entities place their weight behind a BIP,
it makes less and less sense to consider its author the "maintainer"
of the BIP, with rights to modify it at their whim. Someone may have
agreed to the proposal in its original form, but they may disagree
with it if it is altered from under their feet.
BIPs are modified for primarily three reasons:
1. Because of spelling errors, or to otherwise improve on their
description without changing what is actually proposed.
2. To improve the proposal in some way, e.g. after discussion or after
getting feedback on the proposed approach.
3. To add missing content, such as activation strategy.
I propose that changes of the second and third type, unless they are
absolutely free from contention, are done as BIP extensions.
BIP extensions are separate BIPs that extend on or an existing BIP.
BIP extensions do not require the approval of the extended-upon BIP's
author, and are considered independent proposals entirely. A BIP that
extends on BIP XXX is referred to as BIP-XXX-Y, e.g. BIP-123-1, and
their introductory section must include the wording "
This BIP extends on (link: BIP-XXX).
".
By making extensions to BIPs, rather than modifying them long after
review, we are giving the community
1. the assurance that a BIP will mostly remain in its form forever,
except if an obvious win is discovered,
2. the ability to judge modifications to BIPs, such as activation
parameters, on their merits alone, and
3. the path to propose modifications to BIPs even if their authors
have gone inactive and cease to provide feedback, as is the case for
many BIPs today, as BIP extensions do not require the approval of the
extended-upon BIP.
(Apologies if this has been proposed already. If so, feel free to
ignore this message, and sorry to have wasted your time.)
|
