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
|
Return-Path: <cryptaxe@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2E26D890
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 30 Jun 2017 16:51:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com
[209.85.128.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 94FDF1E8
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 30 Jun 2017 16:51:36 +0000 (UTC)
Received: by mail-wr0-f179.google.com with SMTP id r103so207288808wrb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 30 Jun 2017 09:51:36 -0700 (PDT)
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=92wTYq3HH0RLZUmL9TX2s8Y9m3GTnMyCZwPjKf6rRBs=;
b=ocrdqKYRULUnetZJWmL1WYPeic9gkNOHGORup5VDPPi5HPvnUN2MZThGI2ErW+WPPb
rdbgOq10qstAU+mFDIHcjJQC+fZR+Rv9Mw4shMeNIDD35vVMNrLa+yhLMyMlK0gSakVT
NbOJe6Z27ejGiljWL4KDZy47lIGic7FRxoLwu3lHaf+U5BPKBvO2tW1HHcxtKq1hLKqH
km3VV+KhE0HVw3GUCzWfrGX9zIh07AM2ODyYH0N5NfdZSppnpji2qvcXwXLNuLj5nSrd
vcjL45aPW2pi4RhCgD2e2VdiMzkxIFXaCZDkqgKudkT1E6aS9S9RVbP0H4GhQxKEkGSF
dp1A==
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=92wTYq3HH0RLZUmL9TX2s8Y9m3GTnMyCZwPjKf6rRBs=;
b=qFgssaBLgCp5t4WWd0i1NdNb6PvUG3RSs7B0NoAsVwLkZTajpoXwXCiNGmR+sb4VzY
QCwyFfKBydGo8lCtwlDY1nehTQbH8Jl2DhVGdkrpcLyAiwwtpjVyJi8brS2QJqR2SPHH
Ig1UAdNsszBUsq1IyobbvClvBxWE+YeaKb+nsgILioCKF0rYgmw0y97GTamm4tRgtZC/
gRpnJulEtz2S2pcsjWJ5CvFPf7IqPtmsZiKLiCnKJVQuglzpYa0xpIWBTM9lzHq5gmGF
NpMBrReoVF9Nq4ga0kYJhzkEE1hV2OPMrAz16Tz6z4ORzr6xQ/I2nMlVUzUXFFjJAyFP
vQKA==
X-Gm-Message-State: AKS2vOwQUxUzhh3iUjeeh5S5OB+GuQDwM+soXoDkFYN0leic7GpM5oy1
FsotL1hdH0+Cw1HvFFacqUZ5SRucZw==
X-Received: by 10.223.139.87 with SMTP id v23mr25583568wra.145.1498841495240;
Fri, 30 Jun 2017 09:51:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.16.3 with HTTP; Fri, 30 Jun 2017 09:51:34 -0700 (PDT)
Received: by 10.28.16.3 with HTTP; Fri, 30 Jun 2017 09:51:34 -0700 (PDT)
In-Reply-To: <lYqi6yZAdUknHWs2DvSaM3h1tf3EVLngILZV9gbVBm5JVI96RvBGZaPBEFYNzt0QBkjdJ614BTsWjUkmuuqSd7RPFx-ihUL6SIXocqyW_ss=@protonmail.com>
References: <CAGL6+mHQ_vMc2JYVqwfP89WOZdUF2WDtWfh7ccL1PQve=nC+zQ@mail.gmail.com>
<OozQK1_gWeExd5578AYH_dHnSKSvx63FJc2rIBBcaJF4f07qzsR8rr-ka5epwMFCjqDuidAWZiZqqlvn4xvSuUpDY0KkV014VQs6_E3Rp_A=@protonmail.com>
<2f2e6b7c-2d47-518a-5a8f-0b5333607aac@gmail.com>
<lYqi6yZAdUknHWs2DvSaM3h1tf3EVLngILZV9gbVBm5JVI96RvBGZaPBEFYNzt0QBkjdJ614BTsWjUkmuuqSd7RPFx-ihUL6SIXocqyW_ss=@protonmail.com>
From: CryptAxe <cryptaxe@gmail.com>
Date: Fri, 30 Jun 2017 09:51:34 -0700
Message-ID: <CAF5CFkjwdx64F6Ss8Oz=2H1yiu5jWCHZNSoE5W6LD_Husr_Z3g@mail.gmail.com>
To: ZmnSCPxj <ZmnSCPxj@protonmail.com>
Content-Type: multipart/alternative; boundary="f403045e9c22e6099a0553303a7e"
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
X-Mailman-Approved-At: Fri, 30 Jun 2017 16:57:13 +0000
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: OP_BRIBVERIFY - the op code needed for Blind
Merge Mined drivechains
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: Fri, 30 Jun 2017 16:51:37 -0000
--f403045e9c22e6099a0553303a7e
Content-Type: text/plain; charset="UTF-8"
To ZmnSCPxj:
I don't understand this part. In my scheme, a sidechain cannot reorganize
unless the mainchain reorganizes, since the consensus loop only cares about
matching the current block; it ignores splits and does not consider them
valid.
But I suppose you are considering something like the Ethereum mutability
feature, which I do not think is something you would want in a sidechain.
The goal was to allow for sidechain reorgs without effecting the mainchain
at all. With the ratchet system (WIP) the sidechain miners can either move
the side chain forward or start a split at some previous sidechain block
height. This happens as the main chain moves forward normally.
From your other emails on this list, it seems the ratchet is for
withdrawals from sidechain to mainchain? ...
The ratchet system is actually what links the h* data from bribes to
sidechain blocks. h*'s (which are sidechain block hashes) are added to the
ratchet system if they move the sidechain forward or start a split like I
mentioned before. Then a sidechain can request of their local mainchain
node to verify the headers they have downloaded from sidechain peers and
form the side chain.
--f403045e9c22e6099a0553303a7e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div class=3D"gmail_extra" dir=3D"auto"><div class=3D"gma=
il_quote"><blockquote class=3D"m_5035772843904658503m_-4661972935824795979q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div></div></blockquote></div></div><div class=3D"gmail_extra" dir=3D"au=
to"><div class=3D"gmail_quote"><blockquote class=3D"m_5035772843904658503m_=
-4661972935824795979quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div></div></blockquote></div></div><div dir=3D"aut=
o">To ZmnSCPxj:</div><div dir=3D"auto"><br></div><div class=3D"gmail_extra"=
dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"m_50357728439=
04658503m_-4661972935824795979quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div>I don't understand this part.=C2=
=A0 In my scheme, a sidechain cannot reorganize unless the mainchain reorga=
nizes, since the consensus loop only cares about matching the current block=
; it ignores splits and does not consider them valid.<br></div><div><br></d=
iv><div>But I suppose you are considering something like the Ethereum mutab=
ility feature, which I do not think is something you would want in a sidech=
ain.<br></div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">The goal was to allow for sidechain reorgs without effecting the =
mainchain at all. With the ratchet system (WIP) the sidechain miners can ei=
ther move the side chain forward or start a split at some previous sidechai=
n block height. This happens as the main chain moves forward normally.=C2=
=A0</div><div dir=3D"auto"><br></div><div class=3D"gmail_extra" dir=3D"auto=
"><div class=3D"gmail_quote"><blockquote class=3D"m_5035772843904658503m_-4=
661972935824795979quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div></div></blockquote></div></div><div class=3D"gma=
il_extra" dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"m_50=
35772843904658503m_-4661972935824795979quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div>From your other emails on t=
his list, it seems the ratchet is for withdrawals from sidechain to maincha=
in? =C2=A0...<br></div></blockquote></div></div><div dir=3D"auto"><br></div=
><div dir=3D"auto">The ratchet system is actually what links the h* data fr=
om bribes to sidechain blocks. h*'s (which are sidechain block hashes) =
are added to the ratchet system if they move the sidechain forward or start=
a split like I mentioned before. Then a sidechain can request of their loc=
al mainchain node to verify the headers they have downloaded from sidechain=
peers and form the side chain.=C2=A0</div></div>
--f403045e9c22e6099a0553303a7e--
|
