1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 19AFBBD4
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Mar 2017 23:26:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f43.google.com (mail-lf0-f43.google.com
[209.85.215.43])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 77009D3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Mar 2017 23:26:19 +0000 (UTC)
Received: by mail-lf0-f43.google.com with SMTP id z15so393470lfd.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 14 Mar 2017 16:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:sender:from:date:message-id:subject:to;
bh=RIERj+MZW3+/ZvlVB+Ls8oy6/JF8HDyWU3b5EkhcNy4=;
b=CU0zGInw9319rUH1SWNLHpHMK0kPKJmOUsEYZZ7rVbIjVOlCvecXXecVWAPgukinbT
fTS1bwieHkvYZ/t0lgfrIzhj0s3CHa4ZluxQCqBPdF4Ku+VEe9J3JRCih86NBwQhQTqw
3VzIdryWHcBVr5fWU6T1e23tVgAea1NPMEhDjZVR1cPHvzvw9fuYTCUqCTYo71gEGLOY
5Jz5L5MWJlmRg1eji8sxWVBUuJULmeVrG4s/a6AT4/x3JSutkgOjAZxFP2RWgn2GI7PC
6kE3pjx07JDzetdAXOrlo2zngBH61/hBrSf2UKr++7/O/CCOUWdRcsXpgidK3ac4F3lI
d3NQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
:to; bh=RIERj+MZW3+/ZvlVB+Ls8oy6/JF8HDyWU3b5EkhcNy4=;
b=rzhHM5PX5T4nuTUk4BjKb53e2+lVCm9yH9q/T8tMIgSJBWsfd0rlUsh8pkFUSe+599
GNT0j2jyiX4ZKXo4k2bmNxLBuFZ9GkYUlWaLIbn2vgTgd47PzA8m1kiJ13QpMqtXJRya
bFeTikvFEpO3DtQ8lD5g0cJ9Sqwr5zxWILyPfG/4wA//1qObnlszhysCMwS2iHBPQYEh
xXVNZA5wI65D7KvqSdQHDs0fXnal/04pdBiYcDmKrETD1xnzhNoGntyco+jpWryjHJ07
u0sgwKmzi+L095eGf1LTPvj3axenRqNBYLmq+Phf/gZdQ9VzF/pB+CYu9yFoYp6bOitH
p/nQ==
X-Gm-Message-State: AFeK/H1Juv3fynT8rbdtS3nwKB3zF4QfKMZB513olFYmbZgZl3Wea/IYuoUKtyuP7NQgDMtdeQd2UTYdhQPXEA==
X-Received: by 10.25.196.8 with SMTP id u8mr49401lff.21.1489533977688; Tue, 14
Mar 2017 16:26:17 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.25.160.203 with HTTP; Tue, 14 Mar 2017 16:26:17 -0700 (PDT)
From: Erik Aronesty <erik@q32.com>
Date: Tue, 14 Mar 2017 19:26:17 -0400
X-Google-Sender-Auth: eu0ZyTQDBUD-AS2I6ghKZwtJVAk
Message-ID: <CAJowKg+GGsvPAR1ywDody=GGQnEh5pwUMW48cLOmUGhU8SdDtA@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a114b1a309f83bd054ab9277c
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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: Wed, 15 Mar 2017 22:40:45 +0000
Subject: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2017 23:26:20 -0000
--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't have the hashing pr=
oblem could be included in the new non-witness segment of the block.</div><=
/div>
--001a114b1a309f83bd054ab9277c--
|
