Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id D7E4BE22 for ; Tue, 9 Feb 2016 15:53:05 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 009EB182 for ; Tue, 9 Feb 2016 15:53:04 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id l127so13579515iof.3 for ; Tue, 09 Feb 2016 07:53:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DGkRzdDoJc971Zz1dGEned/1x+MAiaUijt5MCIPoME0=; b=GjaMF/2IMphtRP93/tUGb++v/LPe4x69b3MVN7SAsUso+j5iqWNbb7Uc0vprrVdDjt +wFsdL6ffEZQsPPvWUQNRDf8KUN2e/6mAajVgPr/5+IOxTo3fWFsEMmbLI/w7JKujnkh obKzrKl/9Fq6+EVOs4wIVLlTSOg1R8BInmZldwUo3fJZeHtd4k+FuhEc2T5shqqtxR2S eFSCIgn8O5mUM3PqoqzUZiU/h/oSIxHq0wHQXvqBzFDy/+25vJCFRrmfnKDCUJLQ4VF8 FiYVMZ46BxQctyb29SvLkTfuyGTHYf29UPfH0a/MvgvrDnASyUZSEDPuDr99uw3a/5/o GQ6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DGkRzdDoJc971Zz1dGEned/1x+MAiaUijt5MCIPoME0=; b=jeQVW2UEqiA0gfyY3WQutWL9QZJkW7caJ80u0Rdm35MM73J5ldrRrNWrYMW6LJ/TWC Wnm9RII3dHS99qc97j92LADuM/OlK+apdp7Byh2jt+0WGJ1a2axpCAKDUrRRdVu7NaQf hZjHPusrHq5JYGbGELpxPbyl9nwL8UrVqlLMKopdNOa4ywXcif3CqEEEzaRDCvYm/LP6 8DYKq4WUR8gTtOZ9SP8v9Q7PXt8wsFaERxmmdf1stm1nQWs36jVGToXmOEOX3Qruk1cf VoIorCng9aI/aS3vdhae767xd1RD3Jh1kKGo+ZOpFUOwQoQeqi1XC8t3j9Qf2Ar6wUbf o9Nw== X-Gm-Message-State: AG10YOS/GQRxRdWKld8xT5Ui7U6m6hjlNAust75xtk0dmi0tSH4b9OJHjxd76RZAfj+5zR7FPymwH62gyGy9dw== MIME-Version: 1.0 X-Received: by 10.107.136.194 with SMTP id s63mr36540715ioi.88.1455033184440; Tue, 09 Feb 2016 07:53:04 -0800 (PST) Received: by 10.36.203.65 with HTTP; Tue, 9 Feb 2016 07:53:04 -0800 (PST) In-Reply-To: <239b01d16344$717712d0$54653870$@xbt.hk> References: <239b01d16344$717712d0$54653870$@xbt.hk> Date: Tue, 9 Feb 2016 15:53:04 +0000 Message-ID: From: Ricardo Filipe To: jl2012@xbt.hk Content-Type: multipart/alternative; boundary=001a113eb3241858b3052b5850f5 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW 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: Tue, 09 Feb 2016 21:57:57 +0000 Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] A roadmap to a better header format and bigger block size X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 15:53:05 -0000 --001a113eb3241858b3052b5850f5 Content-Type: text/plain; charset=UTF-8 I believe i've seen Luke say this several times before, but there are several more things that the majority of the devs agree should be in bitcoin. I would suggest to compile that list for your stage 3, so that you can have an hardfork that fixes most of those things, and there should be some repository with those changes deployed. 2016-02-09 14:16 GMT+00:00 jl2012--- via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org>: > I would like to present a 2-3 year roadmap to a better header format and > bigger block size > > Objectives: > > 1. Multistage rule changes to make sure everyone will have enough time to > upgrade > 2. Make mining easier, without breaking existing mining hardware and the > Stratum protocol > 3. Make future hardfork less disruptive (with Luke-Jr's proposal) > > Stage 1 is Segregated Witness (BIP141), which will not break any existing > full or light nodes. This may happen in Q2-Q3 2016 > > Stage 2 is fixes that will break existing full nodes, but not light nodes: > a. Increase the MAX_BLOCK_SIZE (the exact value is not suggested in this > roadmap), potentially change the witness discount > b. Anti-DoS rules for the O(n^2) validation of non-segwit scripts > c. (optional) Move segwit's commitments to the header Merkle tree. This is > optional at this stage as it will be fixed in Stage 3 anyway > This may happen in Q1-Q2 2017 > > Stage 3 is fixes that will break all existing full nodes and light nodes: > a. Full nodes upgraded to Stage 2 will not need to upgrade again, as the > rules and activation logic should be included already > b. Change the header format to Luke-Jr's proposal, and move all commitments > (tx, witness, etc) to the new structure. All existing mining hardware with > Stratum protocol should work. > c. Reclaiming unused bits in header for mining. All existing mining chips > should still work. Newly designed chips should be ready for the new rule. > d. Fix the time warp attack > This may happen in 2018 to 2019 > > Pros: > a. Light nodes (usually less tech-savvy users) will have longer time to > upgrade > b. The stage 2 is opt-in for full nodes. > c. The stage 3 is opt-in for light nodes. > > Cons: > a. The stage 2 is not opt-in for light nodes. They will blindly follow the > longest chain which they might actually don't want to > b. Non-upgraded full nodes will follow the old chain at Stage 2, which is > likely to have lower value. > c. Non-upgraded light nodes will follow the old chain at Stage 3, which is > likely to have lower value. (However, this is not a concern as no one > should > be mining on the old chain at that time) > > ------------------------------- > An alternative roadmap would be: > > Stage 2 is fixes that will break existing full nodes and light nodes. > However, they will not follow the minority chain > a. Increase the MAX_BLOCK_SIZE, potentially change the witness discount > b. Anti-DoS rules for the O(n^2) validation of non-segwit scripts > c. Change the header format to Luke-Jr's proposal, and move all commitments > (tx, witness, etc) to the new structure. > This may happen in mid 2017 or later > > Stage 3 is fixes that will break all existing full nodes and light nodes. > a. Full nodes and light nodes upgraded to Stage 2 will not need to upgrade > again, as the rules and activation logic should be included already > b. Reclaiming unused bits in header for mining. All existing mining chips > should still work. > c. Fix the time warp attack > This may happen in 2018 to 2019 > > Pros: > a. The stage 2 and 3 are opt-in for everyone > b. Even failing to upgrade, full nodes and light nodes won't follow the > minority chain at stage 2 > > Cons: > a. Non-upgraded full/light nodes will follow the old chain at Stage 3, > which > is likely to have lower value. (However, this is not a concern as no one > should be mining on the old chain at that time) > b. It takes longer to implement stage 2 to give enough time for light node > users to upgrade > > ------------------------------- > > In terms of safety, the second proposal is better. In terms of disruption, > the first proposal is less disruptive > > I would also like to emphasize that it is miners' responsibility, not the > devs', to confirm that the supermajority of the community accept changes in > Stage 2 and 3. > > Reference: > Matt Corallo's proposal: > > http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012403. > html > Luke-Jr's proposal: > > http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012377. > html > > > > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --001a113eb3241858b3052b5850f5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I believe i've seen Luke say this several times before= , but there are several more things that the majority of the devs agree sho= uld be in bitcoin.
I would suggest to compile that list for your stage = 3, so that you can have an hardfork that fixes most of those things, and th= ere should be some repository with those changes deployed.

2016-02-09 14:16 GMT+0= 0:00 jl2012--- via bitcoin-dev <bitcoin-dev@lists.linu= xfoundation.org>:
I would = like to present a 2-3 year roadmap to a better header format and
bigger block size

Objectives:

1. Multistage rule changes to make sure everyone will have enough time to upgrade
2. Make mining easier, without breaking existing mining hardware and the Stratum protocol
3. Make future hardfork less disruptive (with Luke-Jr's proposal)

Stage 1 is Segregated Witness (BIP141), which will not break any existing full or light nodes. This may happen in Q2-Q3 2016

Stage 2 is fixes that will break existing full nodes, but not light nodes:<= br> a. Increase the MAX_BLOCK_SIZE (the exact value is not suggested in this roadmap), potentially change the witness discount
b. Anti-DoS rules for the O(n^2) validation of non-segwit scripts
c. (optional) Move segwit's commitments to the header Merkle tree. This= is
optional at this stage as it will be fixed in Stage 3 anyway
This may happen in Q1-Q2 2017

Stage 3 is fixes that will break all existing full nodes and light nodes: a. Full nodes upgraded to Stage 2 will not need to upgrade again, as the rules and activation logic should be included already
b. Change the header format to Luke-Jr's proposal, and move all commitm= ents
(tx, witness, etc) to the new structure. All existing mining hardware with<= br> Stratum protocol should work.
c. Reclaiming unused bits in header for mining. All existing mining chips should still work. Newly designed chips should be ready for the new rule. d. Fix the time warp attack
This may happen in 2018 to 2019

Pros:
a. Light nodes (usually less tech-savvy users) will have longer time to
upgrade
b. The stage 2 is opt-in for full nodes.
c. The stage 3 is opt-in for light nodes.

Cons:
a. The stage 2 is not opt-in for light nodes. They will blindly follow the<= br> longest chain which they might actually don't want to
b. Non-upgraded full nodes will follow the old chain at Stage 2, which is likely to have lower value.
c. Non-upgraded light nodes will follow the old chain at Stage 3, which is<= br> likely to have lower value. (However, this is not a concern as no one shoul= d
be mining on the old chain at that time)

-------------------------------
An alternative roadmap would be:

Stage 2 is fixes that will break existing full nodes and light nodes.
However, they will not follow the minority chain
a. Increase the MAX_BLOCK_SIZE, potentially change the witness discount
b. Anti-DoS rules for the O(n^2) validation of non-segwit scripts
c. Change the header format to Luke-Jr's proposal, and move all commitm= ents
(tx, witness, etc) to the new structure.
This may happen in mid 2017 or later

Stage 3 is fixes that will break all existing full nodes and light nodes. a. Full nodes and light nodes upgraded to Stage 2 will not need to upgrade<= br> again, as the rules and activation logic should be included already
b. Reclaiming unused bits in header for mining. All existing mining chips should still work.
c. Fix the time warp attack
This may happen in 2018 to 2019

Pros:
a. The stage 2 and 3 are opt-in for everyone
b. Even failing to upgrade, full nodes and light nodes won't follow the=
minority chain at stage 2

Cons:
a. Non-upgraded full/light nodes will follow the old chain at Stage 3, whic= h
is likely to have lower value. (However, this is not a concern as no one should be mining on the old chain at that time)
b. It takes longer to implement stage 2 to give enough time for light node<= br> users to upgrade

-------------------------------

In terms of safety, the second proposal is better. In terms of disruption,<= br> the first proposal is less disruptive

I would also like to emphasize that it is miners' responsibility, not t= he
devs', to confirm that the supermajority of the community accept change= s in
Stage 2 and 3.

Reference:
Matt Corallo's proposal:
http://lists.linuxfoundation.org= /pipermail/bitcoin-dev/2016-February/012403.
html
Luke-Jr's proposal:
http://lists.linuxfoundation.org= /pipermail/bitcoin-dev/2016-February/012377.
html





_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev

--001a113eb3241858b3052b5850f5--