MIME-Version: 1.0
In-Reply-To: <004E1123-8346-48B6-9BCB-94BAE00EC34B@me.com>
References: <201705232023.40588.luke@dashjr.org>
	<CAJowKgJK9zBkVAM1NyOsjU04gvwV3zGnk+1ebfpt6rnbiKy6Og@mail.gmail.com>
	<CABm2gDpet31gEcBY6NTxEG+xA4rvg8_c79L+J=mJySGbf7Ydbg@mail.gmail.com>
	<CAOG=w-uei5-c-Mpp_R6RrN29NTrSV+gpNd79FC3cB6QPG65sEw@mail.gmail.com>
	<CAH+Axy5yYQywpy0s9pBZt_fNoLPpWfra-cU9HrUwH71GDOchsQ@mail.gmail.com>
	<004E1123-8346-48B6-9BCB-94BAE00EC34B@me.com>
From: Jacob Eliosoff <jacob.eliosoff@gmail.com>
Date: Tue, 30 May 2017 23:07:43 -0400
Message-ID: <CAAUaCyjbObcb1mJVmeEDmgzNddQCY3QhrHV3fgNbin-ZyqgfeA@mail.gmail.com>
To: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Content-Type: multipart/alternative; boundary="001a1142bb7060c4140550c9394f"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hypothetical 2 MB hardfork to follow BIP148
Precedence: list

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

Maybe there's some hole in Jorge's logic and scrapping blockmaxsize has
quadratic hashing risks, and maybe James' 10KB is too ambitious; but even
if so, a simple 1MB tx size limit would clearly do the trick.  The broader
point is that quadratic hashing is not a compelling reason to keep
blockmaxsize post-HF: does someone have a better one?


On May 30, 2017 9:46 PM, "Jean-Paul Kogelman via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> That would invalidate any pre-signed transactions that are currently out
> there. You can't just change the rules out from under people.
>
>
> On May 30, 2017, at 4:50 PM, James MacWhyte via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>
>
>>  The 1MB classic block size prevents quadratic hashing
>> problems from being any worse than they are today.
>>
>>
> Add a transaction-size limit of, say, 10kb and the quadratic hashing
> problem is a non-issue. Donezo.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

<div dir=3D"auto"><div>Maybe there&#39;s some hole in Jorge&#39;s logic and=
 scrapping blockmaxsize has quadratic hashing risks, and maybe James&#39; 1=
0KB is too ambitious; but even if so, a simple 1MB tx size limit would clea=
rly do the trick.=C2=A0 The broader point is that quadratic hashing is not =
a compelling reason to keep blockmaxsize post-HF: does someone have a bette=
r one?<br><div class=3D"gmail_extra" dir=3D"auto"><br></div><div class=3D"g=
mail_extra"><br><div class=3D"gmail_quote">On May 30, 2017 9:46 PM, &quot;J=
ean-Paul Kogelman via bitcoin-dev&quot; &lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.<wbr>linuxfou=
ndation.org</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div dir=3D"auto"><div>That would invalidate any pre-signed transact=
ions that are currently out there. You can&#39;t just change the rules out =
from under people.<br><br></div><div><br>On May 30, 2017, at 4:50 PM, James=
 MacWhyte via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoun=
dation.org" target=3D"_blank">bitcoin-dev@lists.linuxfounda<wbr>tion.org</a=
>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><=
div class=3D"gmail_quote"><div>=C2=A0<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">=C2=A0The 1MB classic block size prevents quadratic hashing<br>
problems from being any worse than they are today.<br><br></blockquote><div=
><br></div><div>Add a transaction-size limit of, say, 10kb and the quadrati=
c hashing problem is a non-issue. Donezo.</div></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
___________<wbr>_________________</span><br><span>bitcoin-dev mailing list<=
/span><br><span><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" ta=
rget=3D"_blank">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a></span><br><s=
pan><a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-d=
ev" target=3D"_blank">https://lists.linuxfoundation.<wbr>org/mailman/listin=
fo/bitcoin-d<wbr>ev</a></span><br></div></blockquote></div><br>____________=
__________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.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-d<wbr>ev</a><br>
<br></blockquote></div></div>
</div></div>

--001a1142bb7060c4140550c9394f--