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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1YPNoc-0007iD-JW
for bitcoin-development@lists.sourceforge.net;
Sun, 22 Feb 2015 04:06:46 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.214.177 as permitted sender)
client-ip=209.85.214.177; envelope-from=jgarzik@bitpay.com;
helo=mail-ob0-f177.google.com;
Received: from mail-ob0-f177.google.com ([209.85.214.177])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YPNoa-00023f-NA
for bitcoin-development@lists.sourceforge.net;
Sun, 22 Feb 2015 04:06:46 +0000
Received: by mail-ob0-f177.google.com with SMTP id wp18so29781687obc.8
for <bitcoin-development@lists.sourceforge.net>;
Sat, 21 Feb 2015 20:06:39 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type:content-transfer-encoding;
bh=VhV6ueXgv9Z2l7LPxQLhqFVsPuX5zl+s4GLzF9Ydjl4=;
b=S0ODdia3y6jPn1xdl/TWHrk5mUTGy2EhayTEE1ahcKnzXhTRY+pb8zcOk4GHlqxJsL
Cbp6T0/djU6xQZyVdoxpwUIbkTOUoI3N6puOTMTWSxF9093sddvorXM5eS5h7yeWUxit
vIg7XZr7MvqwUJj3GRci19+2qPpQCIVn7BEgToVX21POgRHaHZrhP6LpRqXZqlqlrAJl
S35vbnLIpsoOqSj5h+UuOI/IjmaXgT62wayArjAVPefRsrv25nNOfWr33wuTfCJXSnq8
Jiz9KAc41wdgoAdymReRAsL8I49X6isi3Bo8bp685BzDg7r3Vm00VGSJhBivtMvz1rKm
nOtQ==
X-Gm-Message-State: ALoCoQndSozW/I4ZgpsW/V1u+camERcTL49B1HdYMHVHJMpLR3G5kMSuSZe4IfGYRjclDhJ9BHd1
X-Received: by 10.202.90.3 with SMTP id o3mr3136495oib.99.1424577999100; Sat,
21 Feb 2015 20:06:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.219.10 with HTTP; Sat, 21 Feb 2015 20:06:18 -0800 (PST)
In-Reply-To: <CABm2gDpMagWHsBn1t_oLO2bESgD2NUpefYw-gePFaBCNmpXviQ@mail.gmail.com>
References: <20150212064719.GA6563@savin.petertodd.org>
<CANEZrP2uVT_UqJbzyQcEbiS78T68Jj2cH7OGXv5QtYiCwArDdA@mail.gmail.com>
<CAJHLa0PkzG44JpuQoHVLUU8SR55LaJf5AwG=a7AjK2u7TAveOQ@mail.gmail.com>
<20150215212512.GR14804@nl.grid.coop> <54E11248.6090401@gmail.com>
<20150219085604.GT14804@nl.grid.coop>
<CABm2gDorEFNzzHH2bxpo6miv1H0RUhL9uAYX6gg2aW0wB1QDbw@mail.gmail.com>
<CAOG=w-uJFobZtkd8OoPnOJC3uqCOwjsqyfNWJTg3j3sJQn+wXQ@mail.gmail.com>
<CAJHLa0M4Tc7kiQVNmBfMBvSqFyrmHXdaNh7mF+crAdME5FUWHg@mail.gmail.com>
<CABm2gDpMagWHsBn1t_oLO2bESgD2NUpefYw-gePFaBCNmpXviQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Sat, 21 Feb 2015 23:06:18 -0500
Message-ID: <CAJHLa0ObR32wg7TEJ2XHgZ=9=Z+yFsXjF3JCz+4d5mdp1=xu4Q@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.7 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.9 FUZZY_AMBIEN BODY: Attempt to obfuscate words in spam
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
-0.9 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YPNoa-00023f-NA
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] replace-by-fee v0.10.0rc4
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 22 Feb 2015 04:06:46 -0000
On Sat, Feb 21, 2015 at 10:25 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote=
:
> On Sat, Feb 21, 2015 at 11:47 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>> This isn't some theoretical exercise. Like it or not many use
>> insecure 0-conf transactions for rapid payments. Deploying something
>> that makes 0-conf transactions unusable would have a wide, negative
>> impact on present day bitcoin payments, thus "scorched earth"
> And maybe by maintaining first seen policies we're harming the system
> in the long term by encouraging people to widely deploy systems based
> on extremely weak assumptions.
Lacking a coded, reviewed alternative, that's only a platitude.
Widely used 0-conf payments are where we're at today. Simply ceasing
the "maintaining [of] first seen policies" alone is simply not a
realistic option. The negative impact to today's userbase would be
huge.
Instant payments need a security upgrade, yes.
--=20
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
