summaryrefslogtreecommitdiff
path: root/1e/d33411b0a2831118063ebee0377cc6a0217ed5
blob: b3bc9bcf29b28fa12dd63e12b2f824c2b1574956 (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
Return-Path: <asperous2@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 5C252B9D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 25 Aug 2015 23:20:48 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com
	[209.85.223.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 07F212DE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 25 Aug 2015 23:20:48 +0000 (UTC)
Received: by iodt126 with SMTP id t126so206876488iod.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 25 Aug 2015 16:20:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:from:date:message-id:subject:to:content-type;
	bh=8cbHtretWNFs39dS23Izp1xzMX6v7L+i8It5XNNDF94=;
	b=Ew0QRRXaHOvH5wR9CZoD/aHklhwv5e87VBu3J5bW8gSuW8nmdpbNvvX/FbnJth7+S7
	13qe7xrdzI/wNXdb9BZ7EWxn/KzbAVTHHmGS7l+50fRZWakBphsCjcEYxSE52HJFs4wH
	5qd8BrafmD+W62jg0PkK6f8Mi6mOWhJ4BD8ZrjvfFUv9akUrMWJX5vSnI11NC5JqJsES
	pmi21AF3kS9jP2Y0/Ei8SPqr2ENtKQfcDnxbW8noff2mlWxQZSKu8KNPD/7FBXA730KN
	auA6t1z2tuxbQRnIdndWTRw36yHE8lpiAMJMMsIq7XSj05pzj9ZjV6QSNH5TxqWaBEds
	4/pQ==
X-Received: by 10.107.135.79 with SMTP id j76mr25880251iod.29.1440544847428;
	Tue, 25 Aug 2015 16:20:47 -0700 (PDT)
MIME-Version: 1.0
Sender: asperous2@gmail.com
Received: by 10.50.3.33 with HTTP; Tue, 25 Aug 2015 16:20:28 -0700 (PDT)
From: Andy Chase <theandychase@gmail.com>
Date: Tue, 25 Aug 2015 16:20:28 -0700
X-Google-Sender-Auth: uJz1HtvyFxQMFtd_Yc3LwYwDouM
Message-ID: <CAAxp-m9R+cOJ6nn9PeKWkj7zops-8+xKzrmzZN6qUc6ZD9tQrw@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a113eb458ea022b051e2afb93
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
	HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: [bitcoin-dev] BIP/Motivation and deployment of consensus rule
	changes ([soft/hard]forks)
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Tue, 25 Aug 2015 23:20:48 -0000

--001a113eb458ea022b051e2afb93
Content-Type: text/plain; charset=UTF-8

As I understand Github is not to be used for the high-level discussion
of a draft BIP so I will post my thoughts here (is this specified
somewhere? Can we specify this in BIP-0001?).

-   I have some concerns about the structure and the wording of this
    proposal. I think both the structure and the internal wording can be
    slimmed down and simplified
    -   I also believe the "history lessons" should be trimmed out,
        mentioned at best
    -   There's separate BIP for at least one of the code forks
-   BIP-001 specifies that BIP proposals should not be given a BIP
    number until after they have been spelled checked and approved by an
    editor. Greg Maxwell: was this followed?
-   What kind of proposal is this? Informational, Process or Standards
    track?
    -   I believe it should be Standards Track. Include the proposed
        upgrade path as a patch into core as a module that hard forks
        can use in the future. This will also give us some space to work
        through some of the complexities of forks in a definite way.
    -   Alternatively maybe we can split up this BIP into a Standards
        track and a separate Informational BIP?

--001a113eb458ea022b051e2afb93
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>As I understand Github is not to be used for the=
 high-level discussion</div><div>of a draft BIP so I will post my thoughts =
here (is this specified</div><div>somewhere? Can we specify this in BIP-000=
1?).</div><div><br></div><div>- =C2=A0 I have some concerns about the struc=
ture and the wording of this</div><div>=C2=A0 =C2=A0 proposal. I think both=
 the structure and the internal wording can be</div><div>=C2=A0 =C2=A0 slim=
med down and simplified</div><div>=C2=A0 =C2=A0 - =C2=A0 I also believe the=
 &quot;history lessons&quot; should be trimmed out,</div><div>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 mentioned at best</div><div>=C2=A0 =C2=A0 - =C2=A0 There&#39=
;s separate BIP for at least one of the code forks</div><div>- =C2=A0 BIP-0=
01 specifies that BIP proposals should not be given a BIP</div><div>=C2=A0 =
=C2=A0 number until after they have been spelled checked and approved by an=
</div><div>=C2=A0 =C2=A0 editor. Greg Maxwell: was this followed?</div><div=
>- =C2=A0 What kind of proposal is this? Informational, Process or Standard=
s</div><div>=C2=A0 =C2=A0 track?</div><div>=C2=A0 =C2=A0 - =C2=A0 I believe=
 it should be Standards Track. Include the proposed</div><div>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 upgrade path as a patch into core as a module that hard fork=
s</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 can use in the future. This will al=
so give us some space to work</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 through=
 some of the complexities of forks in a definite way.</div><div>=C2=A0 =C2=
=A0 - =C2=A0 Alternatively maybe we can split up this BIP into a Standards<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 track and a separate Informational BI=
P?</div><div><br></div></div></div>

--001a113eb458ea022b051e2afb93--