MIME-Version: 1.0
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"
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIP: OP_BRIBVERIFY - the op code needed for Blind
 Merge Mined drivechains
Precedence: list

--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&#39;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*&#39;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--