MIME-Version: 1.0
From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Date: Sun, 2 Oct 2016 12:49:08 -0300
Message-ID: <CAKzdR-rsy1m-H4fYFuCim5+YJi_C2kgjxymM8A7_nEuqsZoO+g@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114e3e3e0240b2053de3c7a3
Subject: [bitcoin-dev] Drivechain proposal using OP_COUNT_ACKS
Precedence: list

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

Since ScalingBitcoin is close, I think this is a good moment to publish our
proposal on drivechains. This BIP proposed the drivechain we'd like to use
in RSK (a.k.a. Rootstock) two-way pegged blockchain and see it implemented
in Bitcoin. Until that happens, we're using a federated approach.
I'm sure that adding risk-less Bitcoin extensibility through
sidechains/drivechains is what we all want, but it's of maximum importance
to decide which technology will leads us there.
We hope this work can also be the base of all other new 2-way-pegged
blockchains that can take Bitcoin the currency to new niches and test new
use cases, but cannot yet be realized because of current
limitations/protections.

The full BIP plus a reference implementation can be found here:

BIP (draft):
https://github.com/rootstock/bips/blob/master/BIP-R10.md

Code & Test cases:
https://github.com/rootstock/bitcoin/tree/op-count-acks_devel
(Note: Code is still unaudited)

As a summary, OP_COUNT_ACKS is a new segwit-based and soft-forked opcode
that counts acks and nacks tags in coinbase fields, and push the resulting
totals in the script stack.

The system was designed with the following properties in mind:

1. Interoperability with scripting system
2. Zero risk of invalidating a block
3. No additional computation during blockchain management and
re-organization
4. No change in Bitcoin security model
5. Bounded computation of poll results
6. Strong protection from DoS attacks
7. Minimum block space consumption
8. Zero risk of cross-secondary chain invalidation

Please see the BIP draft for a more-detailed explanation on how we achieve
these goals.

I'll be in ScalingBitcoin in less than a week and I'll be available to
discuss the design rationale, improvements, changes and ideas any of you
may have.

Truly yours,
Sergio Demian Lerner
Bitcoiner and RSK co-founder

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

<div dir=3D"ltr"><div><div><div><div><div>Since ScalingBitcoin is close, I =
think this is a good moment to publish our proposal on drivechains. This BI=
P proposed the drivechain we&#39;d like to use in RSK (a.k.a. Rootstock) tw=
o-way pegged blockchain and see it implemented in Bitcoin. Until that happe=
ns, we&#39;re using a federated approach. <br>I&#39;m sure that adding risk=
-less Bitcoin extensibility through sidechains/drivechains is what we all w=
ant, but it&#39;s of maximum importance to decide which technology will lea=
ds us there.<br>We hope this work can also be the base of all other new 2-w=
ay-pegged blockchains that can take Bitcoin the currency to new niches and =
test new use cases, but cannot yet be realized because of current limitatio=
ns/protections.<br><br>The full BIP plus a reference implementation can be =
found here:<br></div><br>BIP (draft):<br><a href=3D"https://github.com/root=
stock/bips/blob/master/BIP-R10.md">https://github.com/rootstock/bips/blob/m=
aster/BIP-R10.md</a><br><br></div>Code &amp; Test cases:<br><a href=3D"http=
s://github.com/rootstock/bitcoin/tree/op-count-acks_devel">https://github.c=
om/rootstock/bitcoin/tree/op-count-acks_devel</a><br></div><div>(Note: Code=
 is still unaudited)<br><br></div><div>As a summary, OP_COUNT_ACKS is a new=
 segwit-based and soft-forked opcode that counts acks and nacks tags in coi=
nbase fields, and push the resulting totals in the script stack.<br><br>The=
 system was designed with the following properties in mind:<br><br>1. Inter=
operability with scripting system <br>2. Zero risk of invalidating a block<=
br>3. No additional computation during blockchain management and re-organiz=
ation<br>4. No change in Bitcoin security model<br>5. Bounded computation o=
f poll results<br>6. Strong protection from DoS attacks<br>7. Minimum block=
 space consumption<br>8. Zero risk of cross-secondary chain invalidation<br=
><br></div><div>Please see the BIP draft for a more-detailed explanation on=
 how we achieve these goals.<br></div><div></div><div><br></div>I&#39;ll be=
 in ScalingBitcoin in less than a week and I&#39;ll be available to discuss=
 the design rationale, improvements, changes and ideas any of you may have.=
<br><br></div><div>Truly yours, <br></div>Sergio Demian Lerner<br></div>Bit=
coiner and RSK co-founder<br><div><div><div><div><div> <div><div><br></div>=
</div></div></div></div></div></div></div>

--001a114e3e3e0240b2053de3c7a3--