From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D8ED471 for ; Sun, 2 Oct 2016 15:49:50 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1CBDE137 for ; Sun, 2 Oct 2016 15:49:50 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id t7so145718327qkh.2 for ; Sun, 02 Oct 2016 08:49:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=1gLO2rguKrxRbVF4ScvkbsISSPlkbtjt02ChHh0iagc=; b=y/eYnaaIIuwTouIavkKRaEQGf8jPXTeOVokKhpUkWTG+zXQHu6jYa7vvTd5ZASdaPy vUylXPDyctEpROR7EeY/iobc7WAaup2DXw10F5vJljs7EfUpUBalELJ7ZuUswwHN3gDX 625L4YEens/qNChI/MhlQ6kO3p0kruK9289dVdkph4ZBifX5ayRFjXhthQO0uQc6lnVX Qz0enoQqIp96mY6PbguMeDnDOcju5ASQlsSpncsqhdw+nwYPUrmBOkQIwqMOsJNp1LMU dzamy1Dhml0HiBPVw2a7jUqQecf73pR/mCyyFBbYwhUq+ta5IRwtJR94mqy0iyRx5L3t PGcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1gLO2rguKrxRbVF4ScvkbsISSPlkbtjt02ChHh0iagc=; b=EP5UJSFblu+Our9guBfWPKNXLe/6K6nFDnIa9b6xoOFbuF/HSVO+EU9xmRDRNjk0w6 emx3Wysa4dvQheUhijnyOjiSL63uKwrm8O/+BEgEawWzq12YosGNS7tpD++WnoSsyspa +m7tUsJNrr1LQRKRiNwuvcs6KNFLtyt8QvZtxg85/4KxQc0UxuP/VZSy/SKw6WhaHhmM jJkOrXPdPeWtd/eUsK8mkftcIbveSWb2WaOcN53Wx1n0dSX2qqWkByITH1hJxIXOY1H0 w/fze1k0dGMEsLXI0e5jTP23ePjOCqNPT+tqnxdyGSVVgp+NfFAIju+BeKewG7geOh8I shaA== X-Gm-Message-State: AA6/9RmNGmAV0r8dJZgph3YTLMzObLuOjvaxApBKxGXG9fHH6TAiay1vXW197M+weZECTTtBnzKaiZjhykOGzw== X-Received: by 10.55.92.71 with SMTP id q68mr17699136qkb.54.1475423389235; Sun, 02 Oct 2016 08:49:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.35.7 with HTTP; Sun, 2 Oct 2016 08:49:08 -0700 (PDT) From: Sergio Demian Lerner Date: Sun, 2 Oct 2016 12:49:08 -0300 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary=001a114e3e3e0240b2053de3c7a3 X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: [bitcoin-dev] Drivechain proposal using OP_COUNT_ACKS X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 15:49:51 -0000 --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
Since ScalingBitcoin is close, I = think this is a good moment to publish our proposal on drivechains. This BI= P proposed the drivechain we'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're using a federated approach.
I'm sure that adding risk= -less Bitcoin extensibility through sidechains/drivechains is what we all w= ant, but it's of maximum importance to decide which technology will lea= ds us there.
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.

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

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

Code & Test cases:
https://github.c= om/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 coi= nbase fields, and push the resulting totals in the script stack.

The= system was designed with the following properties in mind:

1. Inter= operability with scripting system
2. Zero risk of invalidating a block<= br>3. No additional computation during blockchain management and re-organiz= ation
4. No change in Bitcoin security model
5. Bounded computation o= f 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
Bit= coiner and RSK co-founder

=
--001a114e3e3e0240b2053de3c7a3--