MIME-Version: 1.0
Sender: earonesty@gmail.com
From: Erik Aronesty <erik@q32.com>
Date: Tue, 14 Mar 2017 19:26:17 -0400
Message-ID: <CAJowKg+GGsvPAR1ywDody=GGQnEh5pwUMW48cLOmUGhU8SdDtA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114b1a309f83bd054ab9277c
Subject: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork
Precedence: list

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

Some discussion today led me to believe that a post segwit hard fork could
include:

1MB old tx non-witness segment
XMB new segwit non-witness segment
XMB witness segment

By partitioning off old transactions, it allows users of older, more
expensive validation transactions to continue using them, albeit with
higher fees required for the restricted space.

New segwit blocks, which don't have the hashing problem could be included
in the new non-witness segment of the block.

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

<div dir=3D"ltr"><div><div><div><div><div><div>Some discussion today led me=
 to believe that a post segwit hard fork could include:<br></div><br></div>=
1MB old tx non-witness segment<br></div>XMB new segwit non-witness segment<=
br></div>XMB witness segment<br><br></div>By partitioning off old transacti=
ons, it allows users of older, more expensive validation transactions to co=
ntinue using them, albeit with higher fees required for the restricted spac=
e.<br><br></div><div>New segwit blocks, which don&#39;t have the hashing pr=
oblem could be included in the new non-witness segment of the block.</div><=
/div>

--001a114b1a309f83bd054ab9277c--