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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tomh@thinlink.com>) id 1WhjUT-0006RS-Ht
for bitcoin-development@lists.sourceforge.net;
Tue, 06 May 2014 17:49:17 +0000
X-ACL-Warn:
Received: from mail-pd0-f174.google.com ([209.85.192.174])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WhjUS-00006B-Kx
for bitcoin-development@lists.sourceforge.net;
Tue, 06 May 2014 17:49:17 +0000
Received: by mail-pd0-f174.google.com with SMTP id w10so8456151pde.19
for <bitcoin-development@lists.sourceforge.net>;
Tue, 06 May 2014 10:49:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=jdm7SATVO+/e4RTdopL3zI+RE3TcvMsW8ia/T6uXcug=;
b=T4PmV5fuLQEO9SIytxvL3VHSq7Yj5pyrwWEScf9Onyqn0KmMC77dk9b62NO9dj9tM6
PX3X7OsNfJL8XZhLfVUBOvwG7XU6nbtXVQ0JjzTJbN1+zZEC1sP5Ag/96E/60U6W6qYW
OxzCYt10IxDPsFFGB2v1M6Os0uhJH780kgY95MJQsZ5HdXluGgMkBiAs6aiNLQ5XtH36
1pgVRzzTBrByiBzpDK6hqcc3ue2yy9Vjlq/lk4F9gI3NBR+dcaANC9aulRP1pQMrOe/8
mXrUhZ9iJYSFYTRbKbMmUZd5zI40MI2AQK6f/WhDWgBYhwc17sbJg3BQawXWlFjF1v1t
y0AA==
X-Gm-Message-State: ALoCoQljBsW2znOtDt5SJNq+s94DyJVW0EZ23CpapVBbkjhbc9AQH5cyz4AyJOm8GUy50+DdtimA
X-Received: by 10.66.164.70 with SMTP id yo6mr8809808pab.85.1399398550545;
Tue, 06 May 2014 10:49:10 -0700 (PDT)
Received: from [10.100.105.45] ([204.58.254.99])
by mx.google.com with ESMTPSA id bc4sm1655782pbb.2.2014.05.06.10.49.09
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 06 May 2014 10:49:09 -0700 (PDT)
Message-ID: <53692091.5040003@thinlink.com>
Date: Tue, 06 May 2014 10:49:05 -0700
From: Tom Harding <tomh@thinlink.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Christophe Biocca <christophe.biocca@gmail.com>
References: <536589CC.8080005@thinlink.com>
<CANOOu=_tpqz8wdDGj9x_xT5QcT=CHRbr+5Cewj5xuZyJ+ZurNw@mail.gmail.com>
In-Reply-To: <CANOOu=_tpqz8wdDGj9x_xT5QcT=CHRbr+5Cewj5xuZyJ+ZurNw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.6 (/)
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 [209.85.192.174 listed in list.dnswl.org]
0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
[204.58.254.99 listed in dnsbl.sorbs.net]
X-Headers-End: 1WhjUS-00006B-Kx
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] A statistical consensus rule for reducing
0-conf double-spend risk
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: Tue, 06 May 2014 17:49:17 -0000
Christophe Biocca wrote:
> it becomes trivial with a few tries to split the network into two
> halves: (tx1 before tx2, tx2 before tx1).
"before" implies T=0. That is a much too optimistic choice for T; 50%
of nodes would misidentify the respend.
> Tom Harding <tomh@thinlink.com> wrote:
>> - Eventually, node adds a consensus rule:
>> Do not accept blocks containing a transaction tx2 where
>> - tx2 respends an output spent by another locally accepted
>> transaction tx1, and
>> - timestamp(tx2) - timestamp(tx1) > T
|
