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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id BAB7BBAC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 29 Jun 2015 05:53:26 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148154.authsmtp.co.uk (outmail148154.authsmtp.co.uk
[62.13.148.154])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 04B4B1C5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 29 Jun 2015 05:53:25 +0000 (UTC)
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5T5rK76083979;
Mon, 29 Jun 2015 06:53:20 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5T5rFOG005300
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Mon, 29 Jun 2015 06:53:18 +0100 (BST)
Date: Mon, 29 Jun 2015 01:53:15 -0400
From: Peter Todd <pete@petertodd.org>
To: Gregory Maxwell <gmaxwell@gmail.com>
Message-ID: <20150629055314.GB502@savin.petertodd.org>
References: <20150629050726.GA502@savin.petertodd.org>
<201506290540.26019.luke@dashjr.org>
<CAAS2fgRZh=__VGH8aJq4D9G62ostt20YUafJ66mm7BhdBRKe=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="s2ZSL+KKDSLx8OML"
Content-Disposition: inline
In-Reply-To: <CAAS2fgRZh=__VGH8aJq4D9G62ostt20YUafJ66mm7BhdBRKe=Q@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 2478a185-1e23-11e5-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAsUEkAaAgsB AmMbW1JeVV57WGs7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRll A1xoLW5ydwBFeH4+ ZEdiXngVXkB9fRd8
SktJFDgEZnphaTUa TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL
FQ4vNDcwO3BTJTpg CissFQBab1sPGnYG SggGFD4iWEcUAgs+
IlQqJ0YYG1cUP0Mu eUAqWV8ULhsfYgAA
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule
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: Mon, 29 Jun 2015 05:53:26 -0000
--s2ZSL+KKDSLx8OML
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jun 29, 2015 at 05:43:13AM +0000, Gregory Maxwell wrote:
> On Mon, Jun 29, 2015 at 5:40 AM, Luke Dashjr <luke@dashjr.org> wrote:
> > Policy is node/miner fiat and not the domain of BIPs.
>=20
> Even accepting the premise that policy is pure local fiat, the
> conclusion doesn't follow for me. BIPs about best practices or
> especially anything where interop or coordination are, I think,
> reasonable uses of the process.
>=20
> E.g. you might want to know what other kinds of policy are in use if
> you're to have any hope of authoring transactions that work at all!
For example, consider Luke-Jr's own BIP19, M-of-N Standard Transactions,
a non-consensus-critical suggested policy change!
https://github.com/bitcoin/bips/blob/master/bip-0019.mediawiki
Anyway, full-RBF has significant impacts for wallet authors and many
other stakeholders. At minimum it changes how you will want to author
and (re)author transactions, much like BIP19 does.
--=20
'peter'[:-1]@petertodd.org
00000000000000000ffad4a87861689c067f5dd3b98b84d8096572c163aa913a
--s2ZSL+KKDSLx8OML
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVkN1FXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwZmZhZDRhODc4NjE2ODljMDY3ZjVkZDNiOThiODRkODA5
NjU3MmMxNjNhYTkxM2EvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkft4BAf+PLQR40Li1C0wfAq6jMN1J8Es
TaYdjTEQSelvhEgmc5Qx9yBOtdkJppKSLbDFriBRjNy1KnqRwJg2xGppP2u/gBGH
XsKuNusym3cRDFJlG+/4t66e/8iu7MI91+xoBsdx1DLcTunsretWe18IqmsJf9VA
2uQCY5qXi+rvZBv4EcA2qbdvZlTFbqRrhI9O3jdPqF3yVoF88QCow9A0W1lhk8Af
3LAW13v1MxEezobk19qBEROvstgO4hzSRz9KnDOwcPWzucn/Xy3KPOVS+DJSqkuJ
PCDKh2FrT0jK7RPItGH+2+djMw10X+mEZ+FL1RGFl/uAQo450bH1djL4HUAAWA==
=Fmp2
-----END PGP SIGNATURE-----
--s2ZSL+KKDSLx8OML--
|
