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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bip@mattwhitlock.name>) id 1WcocZ-0006TG-TP
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 04:17:19 +0000
X-ACL-Warn:
Received: from qmta03.westchester.pa.mail.comcast.net ([76.96.62.32])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WcocL-0007Pk-N2 for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 04:17:19 +0000
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71])
by qmta03.westchester.pa.mail.comcast.net with comcast
id tG1y1n0041YDfWL53G3JUW; Wed, 23 Apr 2014 04:03:18 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
by omta20.westchester.pa.mail.comcast.net with comcast
id tG3H1n00M4VnV2P3gG3JJ2; Wed, 23 Apr 2014 04:03:18 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: Tom Harding <tomh@thinlink.com>
Date: Wed, 23 Apr 2014 00:03:17 -0400
Message-ID: <1533579.cuHiT41BQ7@crushinator>
User-Agent: KMail/4.13 (Linux/3.12.13-gentoo; KDE/4.13.0; x86_64; ; )
In-Reply-To: <53574581.3040004@thinlink.com>
References: <20140422213128.GB2578@savin> <53574581.3040004@thinlink.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [76.96.62.32 listed in list.dnswl.org]
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
X-Headers-End: 1WcocL-0007Pk-N2
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Double-spending unconfirmed transactions
is a lot easier than most people realise
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: Wed, 23 Apr 2014 04:17:20 -0000
On Tuesday, 22 April 2014, at 8:45 pm, Tom Harding wrote:
> A network where transaction submitters consider their (final)
> transactions to be unchangeable the moment they are transmitted, and
> where the network's goal is to confirm only transactions all of whose
> UTXO's have not yet been seen in a final transaction's input, has a
> chance to be such a network.
Respectfully, this is not the goal of miners. The goal of miners is to maximize profits. Always will be. If they can do that by enabling replace-by-fee (and they can), then they will. Altruism does not factor into business.
|
