summaryrefslogtreecommitdiff
path: root/fd/cfdf9308160a1a5fe3f104d8cefdb2e58512c6
blob: fd58eb6d0f13d9fa5a474b23959480cde636a3ab (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
Return-Path: <ctpacia@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C7089C1C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  4 Dec 2017 19:36:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f46.google.com (mail-it0-f46.google.com
	[209.85.214.46])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 837213FB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  4 Dec 2017 19:36:32 +0000 (UTC)
Received: by mail-it0-f46.google.com with SMTP id x28so15604795ita.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 04 Dec 2017 11:36:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc; bh=j2bO22xT0ebADqEFjOXnSTFYKEeet4D+6f3A8S6UCpY=;
	b=tI+frFlY41Rec+JnCfNlzMLAcgkp5uHwgEOtL0LgSJBkGnsZPPOjKjMNbECLEk2CDV
	OX/bjzvRnq+0+zdoMa43+J2j1xhmORcViN6JDK7coGE4/zwQYI2LBiU7oopnyxExAtU1
	d/e91pY3rniUCGBQD/eMGffS+aZVqvQLAi2kZY9CO7rhDJA7Q8R2smrk/clF8EYR7Jf3
	ZseIW/NkdS+JedXoBarej1YwHHoTszwukxcmQpIM9Xuvpos3AQb6TcwDN1LX+yIT0IB/
	pW9ziFhJ/9opKfTEczHt/JHDMOwqBC+6YWRb9y1pbAbghJMFCeCzq68htepVlNzGWgpY
	im+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc;
	bh=j2bO22xT0ebADqEFjOXnSTFYKEeet4D+6f3A8S6UCpY=;
	b=elKg77sj4hzvdQtot36zMGwCryeiXll+E+JYhIqBbrFqyq3jvzIPS2OqaPczfq8m6a
	/1bHaONoIy2QkOmBTBk49Bb9Xg4dPsGXJ25OtgYE9UsfYHhdrphRlKO1PqrmSiTyy1j7
	u6BNV23JnwSPGZR2wcWXYwdLK6KOfMZKNY+kqzCfD0IyW8H1QMOcHVf1oRKBCiYwbZNu
	KPhnyfC3ngHF9Ha53boQZ8XK3sT+tiJW2BVCrzmp018Kjbu6w8nwhtLGyg8cXXuzeZa4
	z7bCFvC8HiHVPMPL7YI6XjZL2ZkalJ733mLspo2M6K5u2UDfl01rYFFoXzFLwSYziSfG
	Wzuw==
X-Gm-Message-State: AJaThX5FrXd1YiCZrZCQwtsqKQFJpp1qKv4X6C5Lzwd8FpKRehAaq20e
	X3Nnzrif7U52OEEW56kqZDS87yvFykIeQ5rQe1k=
X-Google-Smtp-Source: AGs4zMZ4Hc5LGCuaJAaXQo50v6HCHT/FnyDq2q/CWjqkWBsFtL+ElQ4IGlQmRPkGKBFcnLy/mAyvdOwjpxZeOxE6nCQ=
X-Received: by 10.36.36.213 with SMTP id f204mr14549772ita.89.1512416191827;
	Mon, 04 Dec 2017 11:36:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.214.138 with HTTP; Mon, 4 Dec 2017 11:36:31 -0800 (PST)
Received: by 10.36.214.138 with HTTP; Mon, 4 Dec 2017 11:36:31 -0800 (PST)
In-Reply-To: <dd2781a6-3e10-9f0c-6ee0-a2c070b7cf67@gmail.com>
References: <d3497397-33c3-90c1-1be8-a733736eac0b@gmail.com>
	<1bb6cccd-3f6d-d62a-2825-4e6f46a4b525@mattcorallo.com>
	<dd2781a6-3e10-9f0c-6ee0-a2c070b7cf67@gmail.com>
From: Chris Pacia <ctpacia@gmail.com>
Date: Mon, 4 Dec 2017 14:36:31 -0500
Message-ID: <CAB+qUq4wNv=-ZSibUvVCwYSE7Qw8xe8EH91KG6znUp1d7X=mdA@mail.gmail.com>
To: Paul Sztorc <truthcoin@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="001a1147bce6ddd50f055f88d592"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	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
Subject: Re: [bitcoin-dev] Two Drivechain BIPs
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: Mon, 04 Dec 2017 19:36:32 -0000

--001a1147bce6ddd50f055f88d592
Content-Type: text/plain; charset="UTF-8"

I think you are missing a few things.

First of all, I think the security model for sidechains is the same as
that of every blockchain

People will say things, like "but with sidechains 51% hashrate can steal
your coins!", but as I have repeated many times, this is also true of
mainchain btc-tx.  is something else?


There are substantial opportunity costs as well as a collective action
problem when it comes to re-writing the mainchain.

Is there anything similar for drivechains? As far as I can tell there is no
opportunity cost to casting a malicious vote, no repercussions, and no
collective action barrier that needs to be overcome.

Unless I'm missing something I wouldn't liken the security of a drivechain
to that of the mainchain.

--001a1147bce6ddd50f055f88d592
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"quoted-text">I think you are m=
issing a few things.<br></div>
<br>
First of all, I think the security model for sidechains is the same as<br>
that of every blockchain<br>
<br>
People will say things, like &quot;but with sidechains 51% hashrate can ste=
al<br>
your coins!&quot;, but as I have repeated many times, this is also true of<=
br>
mainchain btc-tx. =C2=A0is something else?<br></blockquote></div></div></di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">There are substantial oppor=
tunity costs as well as a collective action problem when it comes to re-wri=
ting the mainchain.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">Is there anything similar for drivechains? As far as I can tell there is =
no opportunity cost to casting a malicious vote, no repercussions, and no c=
ollective action barrier that needs to be overcome.=C2=A0</div><div dir=3D"=
auto"><br></div><div dir=3D"auto">Unless I&#39;m missing something I wouldn=
&#39;t liken the security of a drivechain to that of the mainchain.</div><d=
iv dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><bloc=
kquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"></blockquote></div></div></div></div>

--001a1147bce6ddd50f055f88d592--