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
|
Return-Path: <tomh@thinlink.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id C7AA5932
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 26 Jan 2017 15:58:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pf0-f177.google.com (mail-pf0-f177.google.com
[209.85.192.177])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 34337192
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 26 Jan 2017 15:58:37 +0000 (UTC)
Received: by mail-pf0-f177.google.com with SMTP id f144so66234589pfa.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 26 Jan 2017 07:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=thinlink-com.20150623.gappssmtp.com; s=20150623;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-transfer-encoding;
bh=0cBYT0S3jVeUwrAWNRyKbiBXaBa0xn/WI0Xem9I9+r8=;
b=XboVKBlOPu0d7dP2Cd9I7SVS6fbmOTitEbfa5/dDIrS5CRsfAZlx6Bss3WTD6GL8G8
XmgY/i+3I65ad0VKOMRTU6ieU+GWCHg94qZlZAPhLDbTsNEGNXt7VDACFPcBmjxCdQab
EKBYciGh240jblda9dNCJm0uhEJL4r9eRZnSsLZ2Ogrx6xddcUCOtu9wgLs3AYc7nKdB
tDbGiCxv8v4qFurEI0zv5qbZZnsgtu22nvogD20bfA1PhocfLFLIazdndI6OGSfdfsd1
1XLyBRvyiiJOqfO0iw3z8zAtVk6jdlLqf/AqIqXg6UBNhRGcvw2up4X115BOrrdh+SMk
6lzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding;
bh=0cBYT0S3jVeUwrAWNRyKbiBXaBa0xn/WI0Xem9I9+r8=;
b=HvFkadFX3FLshg92uqQ2kZBUyae3s6NY5PAuTDlSAt8sOJCX2NkUow5i+Is8vVwLrH
PMqilLolrrYYkHwztwJqrax98y/Io0aR7SFj+BuBydJCAp1mZqpV5kEmDc1Bj3VYKjrf
sKSw2jL8KXFfDaSTktwcz6bF+31cxt2PZkjbd7SOQNhuU8WNck7USqPcJog36hwUYxoq
pQGqZZBedwzFMlBqp6e6WrVJZIWX6u5nk8/wj9n526GGWp0DL/dnPT30Y35NYzeEJWoF
b6g2tJq6mdnTnIRCQOAhL3fTrkAfUMHHtMFD8hWzu0Gad2Jullfj3dRT5tTvuYTPJHb0
m9iw==
X-Gm-Message-State: AIkVDXJeef6Gk4D7KP0KVHPzy8XFAhg05+fdoLSlhkDTip2k9dY7tHbKDpKNP1Hf+5oQrM1X
X-Received: by 10.99.8.194 with SMTP id 185mr4013731pgi.76.1485446316310;
Thu, 26 Jan 2017 07:58:36 -0800 (PST)
Received: from [10.199.6.91] ([12.219.129.12])
by smtp.gmail.com with ESMTPSA id
r78sm4491389pfe.55.2017.01.26.07.58.34
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 26 Jan 2017 07:58:34 -0800 (PST)
To: bitcoin-dev@lists.linuxfoundation.org
References: <A182F080-F154-4F05-B2F1-21B90E469267@xbt.hk>
<93ac7433-470c-d59e-e085-29f0f1613676@mattcorallo.com>
<CAAcC9ys4dH3hFzXJon7ho_TP3YwOd=SB2DB0oW5-NnNY5Q19Cw@mail.gmail.com>
<CEA70782-BE59-486E-BD79-0446A73DEDC3@xbt.hk>
<CAAcC9ytGJUe8_va+Ft2u=1SLm=0=vTpm1QPhJekNGh-WvktW8A@mail.gmail.com>
<7AF0AA6D-C144-4D0C-B5FC-0BC2C79C0D26@xbt.hk>
From: Tom Harding <tomh@thinlink.com>
Message-ID: <369b781f-065f-9a1d-a3d7-e98a6fe7f4f6@thinlink.com>
Date: Thu, 26 Jan 2017 07:58:23 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <7AF0AA6D-C144-4D0C-B5FC-0BC2C79C0D26@xbt.hk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 26 Jan 2017 16:00:30 +0000
Subject: Re: [bitcoin-dev] Anti-transaction replay in a hardfork
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Thu, 26 Jan 2017 15:58:37 -0000
Even more to the point, new post- fork coins are fork-specific. The
longer both forks persist, the more transactions become unavoidably
fork-specific through the mixing in of these coins. Any attempt to
maximize replay will become less effective with time.
The rationality of actors in this situation essentially defines the
limited solution that is possible. Upgraded software can create
transactions guaranteed not to execute to one fork or the other, or that
is not prevented from execution on either fork. I see no downside to
this, and the advantage is that markets can be much less chaotic. In
fact exchanges will be much better off if they require that post-fork
trading, deposits and withdrawals are exclusively chain-specific, which
will also result in well determined prices for the two currencies.
None of this precludes the possibility of further forks on either side,
and the difficulty consideration alone suggests a likely counter-fork by
(part of) the existing network.
On 1/26/2017 1:20 AM, Johnson Lau via bitcoin-dev wrote:
> Not to mention that mining is a random process, and the hashing power is going up and down.
|
