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
|
Return-Path: <dave@dtrt.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CD89FAF3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jun 2015 14:03:33 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.dtrt.org (mail.dtrt.org [207.192.75.234])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7CD6C181
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jun 2015 14:03:33 +0000 (UTC)
Received: from harding by mail.dtrt.org with local (Exim 4.72)
(envelope-from <dave@dtrt.org>)
id 1Z9w8J-0004wX-JX; Tue, 30 Jun 2015 10:03:31 -0400
Date: Tue, 30 Jun 2015 10:02:13 -0400
From: "David A. Harding" <dave@dtrt.org>
To: Adam Back <adam@cypherspace.org>
Message-ID: <20150630140213.GA22557@localhost.localdomain>
References: <20150629050726.GA502@savin.petertodd.org>
<5591E10F.9000008@thinlink.com>
<20150630013736.GA11508@savin.petertodd.org>
<CALqxMTH_5rtOs=aSNiVrfsG_sqQDCnTr-8qBH3Qji+8g_dAMcQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j"
Content-Disposition: inline
In-Reply-To: <CALqxMTH_5rtOs=aSNiVrfsG_sqQDCnTr-8qBH3Qji+8g_dAMcQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD
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: Tue, 30 Jun 2015 14:03:33 -0000
--nFreZHaLTZJo0R7j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 30, 2015 at 03:12:52PM +0200, Adam Back wrote:
> Any thoughts on the simplest way to support an opt-in version of full-RBF?
Bundle it in with BIP62 version-2 (or whatever) transactions.
- As you desire for RBF, the BIP62 transactions are already specified to
be opt-in. Nobody has to use them.
- Although BIP62 transactions only prevent third-party mutation, some
people might wrongly assume that they prevent all mutation---including
double spending.
We need to make it clear that even with BIP62 transactions, signers
can still mutate their own transactions---and what better way to do
that than make BIP62 transactions easier to double spend?
The downside I see is possible further delay of full BIP62. Although, I
guess it could go the other way too by having developers who want RBF
help push BIP62 into production.
-Dave
--=20
David A. Harding
--nFreZHaLTZJo0R7j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVkqFlAAoJEEspww/ynsS3gfwH/Aiy3Wrn4hsi/l6ceh2ajV3k
r0ub5HW3LZXUO5sBKJA9WpFXM5hQmIVGjkV2JHGWVqBaLjsjhL2StS5UKdWYPLVq
OwSXymr3XeuKq11vcm0WtLsn5+GulAnPZRusITOXwqZwbkGPJ3JTE2R5Wt4eQBrm
GJ1SHFl8oAXHSMITP6AWTg+bFzjSUrfg07+9oRRvlMDFGh1NYfBTWAstZbmH6uHJ
YH02rDEOsgCupS4DjdRBwyAK97X0jvvczok7aPgtAitYnT0X0tLtjejul55qaPT3
rLk82Ay8VfllTaFt1qmylVpoSK5ka6ha/4vof5RtBeDXCwAuRJ8OV36xNb02wKM=
=ypwQ
-----END PGP SIGNATURE-----
--nFreZHaLTZJo0R7j--
|
