MIME-Version: 1.0
Sender: earonesty@gmail.com
In-Reply-To: <201705232023.40588.luke@dashjr.org>
References: <201705232023.40588.luke@dashjr.org>
From: Erik Aronesty <erik@q32.com>
Date: Tue, 23 May 2017 19:07:41 -0400
Message-ID: <CAJowKgJK9zBkVAM1NyOsjU04gvwV3zGnk+1ebfpt6rnbiKy6Og@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary="94eb2c084666018a1e0550390e09"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hypothetical 2 MB hardfork to follow BIP148
Precedence: list

--94eb2c084666018a1e0550390e09
Content-Type: text/plain; charset="UTF-8"

Personally, I would prefer if a 2MB lock-in that uses BIP103 for the
timing.

I think up to 20% per year can be absorbed by averages in bandwidth/CPU/RAM
growth, of which bandwidth seems the most constraining.

- Erik


On Tue, May 23, 2017 at 4:23 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> In light of some recent discussions, I wrote up this BIP for a real 2 MB
> block
> size hardfork following Segwit BIP148 activation. This is not part of any
> agreement I am party to, nor anything of that sort. Just something to throw
> out there as a possible (and realistic) option.
>
> Note that I cannot recommend this to be adopted, since frankly 1 MB blocks
> really are still too large, and this blunt-style hardfork quite risky even
> with consensus. But if the community wishes to adopt (by unanimous
> consensus)
> a 2 MB block size hardfork, this is probably the best way to do it right
> now.
> The only possible way to improve on this IMO would be to integrate it into
> MMHF/"spoonnet" style hardfork (and/or add other unrelated-to-block-size HF
> improvements).
>
> I have left Author blank, as I do not intend to personally champion this.
> Before it may be assigned a BIP number, someone else will need to step up
> to
> take on that role. Motivation and Rationale are blank because I do not
> personally think there is any legitimate rationale for such a hardfork at
> this
> time; if someone adopts this BIP, they should complete these sections. (I
> can
> push a git branch with the BIP text if someone wants to fork it.)
>
> <pre>
> BIP: ?
> Layer: Consensus (hard fork)
> Title: Post-segwit 2 MB block size hardfork
> Author: FIXME
> Comments-Summary: No comments yet.
> Comments-URI: ?
> Status: Draft
> Type: Standards Track
> Created: 2017-05-22
> License: BSD-2-Clause
> </pre>
>
> ==Abstract==
>
> Legacy Bitcoin transactions are given the witness discount, and a block
> size
> limit of 2 MB is imposed.
>
> ==Copyright==
>
> This BIP is licensed under the BSD 2-clause license.
>
> ==Specification==
>
> Upon activation, a block size limit of 2000000 bytes is enforced.
> The block weight limit remains at 4000000 WU.
>
> The calculation of block weight is modified:
> all witness data, including both scriptSig (used by pre-segwit inputs) and
> segwit witness data, is measured as 1 weight-unit (WU), while all other
> data
> in the block is measured as 4 WU.
>
> The witness commitment in the generation transaction is no longer required,
> and instead the txid merkle root in the block header is replaced with a
> hash
> of:
>
> 1. The witness reserved value.
> 2. The witness merkle root hash.
> 3. The transaction ID merkle root hash.
>
> The maximum size of a transaction stripped of witness data is limited to 1
> MB.
>
> ===Deployment===
>
> This BIP is deployed by flag day, in the block where the median-past time
> surpasses 1543503872 (2018 Nov 29 at 15:04:32 UTC).
>
> It is assumed that when this flag day has been reached, Segwit has been
> activated via BIP141 and/or BIP148.
>
> ==Motivation==
>
> FIXME
>
> ==Rationale==
>
> FIXME
>
> ==Backwards compatibility==
>
> This is a hardfork, and as such not backward compatible.
> It should not be deployed without consent of the entire Bitcoin community.
> Activation is scheduled for 18 months from the creation date of this BIP,
> intended to give 6 months to establish consensus, and 12 months for
> deployment.
>
> ==Reference implementation==
>
> FIXME
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--94eb2c084666018a1e0550390e09
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Personally, I would prefer if a 2MB lock-in that uses BIP1=
03 for the timing. =C2=A0=C2=A0<br><br>I think up to 20% per year can be ab=
sorbed by averages in bandwidth/CPU/RAM growth, of which bandwidth seems th=
e most constraining.<br><br>- Erik<br><br></div><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote">On Tue, May 23, 2017 at 4:23 PM, Luke Dashjr=
 via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.=
linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.or=
g</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In light of some =
recent discussions, I wrote up this BIP for a real 2 MB block<br>
size hardfork following Segwit BIP148 activation. This is not part of any<b=
r>
agreement I am party to, nor anything of that sort. Just something to throw=
<br>
out there as a possible (and realistic) option.<br>
<br>
Note that I cannot recommend this to be adopted, since frankly 1 MB blocks<=
br>
really are still too large, and this blunt-style hardfork quite risky even<=
br>
with consensus. But if the community wishes to adopt (by unanimous consensu=
s)<br>
a 2 MB block size hardfork, this is probably the best way to do it right no=
w.<br>
The only possible way to improve on this IMO would be to integrate it into<=
br>
MMHF/&quot;spoonnet&quot; style hardfork (and/or add other unrelated-to-blo=
ck-size HF<br>
improvements).<br>
<br>
I have left Author blank, as I do not intend to personally champion this.<b=
r>
Before it may be assigned a BIP number, someone else will need to step up t=
o<br>
take on that role. Motivation and Rationale are blank because I do not<br>
personally think there is any legitimate rationale for such a hardfork at t=
his<br>
time; if someone adopts this BIP, they should complete these sections. (I c=
an<br>
push a git branch with the BIP text if someone wants to fork it.)<br>
<br>
&lt;pre&gt;<br>
BIP: ?<br>
Layer: Consensus (hard fork)<br>
Title: Post-segwit 2 MB block size hardfork<br>
Author: FIXME<br>
Comments-Summary: No comments yet.<br>
Comments-URI: ?<br>
Status: Draft<br>
Type: Standards Track<br>
Created: 2017-05-22<br>
License: BSD-2-Clause<br>
&lt;/pre&gt;<br>
<br>
=3D=3DAbstract=3D=3D<br>
<br>
Legacy Bitcoin transactions are given the witness discount, and a block siz=
e<br>
limit of 2 MB is imposed.<br>
<br>
=3D=3DCopyright=3D=3D<br>
<br>
This BIP is licensed under the BSD 2-clause license.<br>
<br>
=3D=3DSpecification=3D=3D<br>
<br>
Upon activation, a block size limit of 2000000 bytes is enforced.<br>
The block weight limit remains at 4000000 WU.<br>
<br>
The calculation of block weight is modified:<br>
all witness data, including both scriptSig (used by pre-segwit inputs) and<=
br>
segwit witness data, is measured as 1 weight-unit (WU), while all other dat=
a<br>
in the block is measured as 4 WU.<br>
<br>
The witness commitment in the generation transaction is no longer required,=
<br>
and instead the txid merkle root in the block header is replaced with a has=
h<br>
of:<br>
<br>
1. The witness reserved value.<br>
2. The witness merkle root hash.<br>
3. The transaction ID merkle root hash.<br>
<br>
The maximum size of a transaction stripped of witness data is limited to 1 =
MB.<br>
<br>
=3D=3D=3DDeployment=3D=3D=3D<br>
<br>
This BIP is deployed by flag day, in the block where the median-past time<b=
r>
surpasses 1543503872 (2018 Nov 29 at 15:04:32 UTC).<br>
<br>
It is assumed that when this flag day has been reached, Segwit has been<br>
activated via BIP141 and/or BIP148.<br>
<br>
=3D=3DMotivation=3D=3D<br>
<br>
FIXME<br>
<br>
=3D=3DRationale=3D=3D<br>
<br>
FIXME<br>
<br>
=3D=3DBackwards compatibility=3D=3D<br>
<br>
This is a hardfork, and as such not backward compatible.<br>
It should not be deployed without consent of the entire Bitcoin community.<=
br>
Activation is scheduled for 18 months from the creation date of this BIP,<b=
r>
intended to give 6 months to establish consensus, and 12 months for<br>
deployment.<br>
<br>
=3D=3DReference implementation=3D=3D<br>
<br>
FIXME<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</blockquote></div><br></div>

--94eb2c084666018a1e0550390e09--