summaryrefslogtreecommitdiff
path: root/2c/00101854c853338b10686967193f3708a36d40
blob: 99a18eec2dec5a76f4c9430affdb358d9d39ad4e (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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <elombrozo@gmail.com>) id 1Z69z0-0005TN-9F
	for bitcoin-development@lists.sourceforge.net;
	Sat, 20 Jun 2015 04:02:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.192.169 as permitted sender)
	client-ip=209.85.192.169; envelope-from=elombrozo@gmail.com;
	helo=mail-pd0-f169.google.com; 
Received: from mail-pd0-f169.google.com ([209.85.192.169])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z69yz-0001g7-9R
	for bitcoin-development@lists.sourceforge.net;
	Sat, 20 Jun 2015 04:02:18 +0000
Received: by pdbci14 with SMTP id ci14so44188172pdb.2
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 19 Jun 2015 21:02:11 -0700 (PDT)
X-Received: by 10.68.200.100 with SMTP id jr4mr37464702pbc.168.1434772931588; 
	Fri, 19 Jun 2015 21:02:11 -0700 (PDT)
Received: from [192.168.1.102] (cpe-76-167-237-202.san.res.rr.com.
	[76.167.237.202]) by mx.google.com with ESMTPSA id
	oa14sm12691475pdb.47.2015.06.19.21.02.07
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 19 Jun 2015 21:02:10 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
	boundary="Apple-Mail=_08455CE8-2B7F-4F01-944E-05CFACE57279";
	protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <201506200348.06564.luke@dashjr.org>
Date: Fri, 19 Jun 2015 21:02:06 -0700
Message-Id: <B7B38239-8EF5-4D12-B3E7-40AE152CF5A3@gmail.com>
References: <20150619103959.GA32315@savin.petertodd.org>
	<CAOG=w-u6fmpnojpQmrFEMRK56WDsfhZgm406C3tVax5hsX2sOA@mail.gmail.com>
	<CACq0ZD5VDJRuKiq2NaPyoJdDVMPd+9YWtEr3pauS5ZNzxXXEig@mail.gmail.com>
	<201506200348.06564.luke@dashjr.org>
To: Luke Dashjr <luke@dashjr.org>
X-Mailer: Apple Mail (2.2098)
X-Spam-Score: -1.2 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(elombrozo[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-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.4 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z69yz-0001g7-9R
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
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: Sat, 20 Jun 2015 04:02:18 -0000


--Apple-Mail=_08455CE8-2B7F-4F01-944E-05CFACE57279
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jun 19, 2015, at 8:48 PM, Luke Dashjr <luke@dashjr.org> wrote:
>=20
> On Saturday, June 20, 2015 1:23:03 AM Aaron Voisine wrote:
>> They don't need to be made cryptographically safe, they just have to =
be
>> safer than, for instance, credit card payments that can be charged =
back. As
>> long as it's reasonably good in practice, that's fine.
>=20
> They never will be. You can get a decent rate of success merely by =
making one
> transaction propagate fast (eg, 1 input, 1 output) and the other slow =
(eg,
> 1000 inputs, 1000 outputs) and choosing your peers carefully. The only =
reason
> unconfirmed transactions aren't double spent today is because nobody =
is
> seriously *trying*.
>=20
> Luke
>=20


Newspapers are often sold in vending machines that make it possible for =
anyone to just pay the price of one and take them all=E2=80=A6and most =
of the time they are not that carefully monitored. Why? Because most =
people have better things to do than try to steal a few newspapers. They =
probably were much more closely monitored earlier in their history=E2=80=A6=
but once it became clear that despite the obvious attack vector very few =
people actually try to game it, vendors figured it wasn=E2=80=99t really =
that big a risk. Same thing applies to people trying to steal a piece of =
bubble gum at the cash register at a convenience store by =
double-spending.

- Eric Lombrozo

> =
--------------------------------------------------------------------------=
----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--Apple-Mail=_08455CE8-2B7F-4F01-944E-05CFACE57279
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVhOW+AAoJEJNAI64YFENUAUAQAILbh2n1YHjALZb2uXFwgr/o
CRzHsmdY2ImpfYhBlhbsBq1DpcUdnsX6lSeVAlTKX5rVZhyYFxRSf4IaVCkaHDzt
SgWDvd9F4S2N333KHzYrpF4lvj5un3ID8SfFn/1f7NvUMn+mTp9WI0g+S9jL2mHH
rnZJ8yPrZWPwfqEs96dz81j8/OJle3DBUt7Zp6rqv1FNnPn8RPRdMtvSC9jyegzL
WKJvE1hx4F+W/MjC7F2MAaXHgH5Kr2vxkd4+OvhJWY11E6O11BBCmhsG7KaQ1LaU
DF4p9WDUzlcHFBPld1+d+c5mY/9oVeEToe4f+/6iR8N7U8VZ0DKqb0RziFOOFanu
K7+7Dfcj+koH9U1M4Yxp4JxHLDgWnGnRGBkjwwGbGbKPRpv3IUKsKx7G6ancYcM+
xkAik/MSKXPGQTYnra/mubX74td419mzWl2P/PSRjFJtdfvkBqXT4ysyAZtEzVbH
vTOkbM1AoNazjSAwI1cdbpCMYKowNL0+b6B8Cd5HWJgEugUh9p/KVwxk/VrdlG7x
Y5E6uh5UgfzJQpabWsawjTTw4yXW7qa39j+5WFSG0Igm5ZlChVzc3L8xzv0RR6Z6
i+YUGFdd/6C82wgqdcG1r5C6W+iJ0DY05C04loYgEE3R1gojbRwAS1JMi/Vcl6gD
O5kLI34qe41Sfi7bT+2C
=9bYl
-----END PGP SIGNATURE-----

--Apple-Mail=_08455CE8-2B7F-4F01-944E-05CFACE57279--