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
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
Return-Path: <tier.nolan@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 36839FD8
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Feb 2016 19:29:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com
[209.85.213.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C3FA5168
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Feb 2016 19:29:32 +0000 (UTC)
Received: by mail-ig0-f179.google.com with SMTP id 5so19380631igt.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 01 Feb 2016 11:29:32 -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:cc
:content-type; bh=PNyn+QXQ5+e/dWnnbuBOjhCq2MK3psWSxDTPTRODu0M=;
b=hw42btSvq7Ombte2xXdjsvTN9F7x5at6fq8xRUdSBj783gv2CH+yIVBNJWjbIG0Dgx
+TQ238AYBcM1Jzl9AG+RMO4RTPNIqyFxuTlTKZn2CZ862fX6wI8hKc34HACl+tccU2sP
O93ehyvnqxrEyfXHLFz6f83ozww/H8KyR//C4T4NcVyejYXgWOdOQsKdGDwL84kNN0oj
bQi2Xo8fRBrguQF1EHKBB2/EktV5beV7diiPxR+2wwINrZgc8oNhB2j/0Eo/tPb3PbPC
NrEmjTVsXOt1nnEWBHD/M/24W947JroYR3dNpfftJCnNnDqLBYZG9wesIxkwxVhxON+0
xHzw==
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:cc:content-type;
bh=PNyn+QXQ5+e/dWnnbuBOjhCq2MK3psWSxDTPTRODu0M=;
b=NsP6gHve//uIdGMMY3JfgyASZS941/7lhuaK7cjO5cewlwWpAB9VugqTUH7i2C/7OR
mxqr4cWcYTAHCQvkTjaNixoVYKB5CAFdYpgqN7sLVpf0bOhC2DFyAPT8PzXIAPBxpT+5
UtGYU2R/zL/AaP1Ms05qU3Q/sbU7xRcgnFy8uWa4Mufuyi7Wlm1QmFPsSPCWmcgG04gT
1AILsrvrYQyRghJJ+F/DceBu9g6C1JPL3m+3oxwed1mdXRD3PyplYd8cblqUG/FGcOx/
u37QiDh9oLmEYCgr2trytONdoEUPCxpvfRD68Lz10TGgP3Ib6Q1+p/tL7eYDaJSViAUX
TvLg==
X-Gm-Message-State: AG10YOSWiolH5wBtBl7VrFaUTzEByb6+LZ69pWhiDu12TPldVry8o/UB1OzOMsExbfBP4mGMBODetZpxfEuxmA==
MIME-Version: 1.0
X-Received: by 10.50.73.137 with SMTP id l9mr13043271igv.95.1454354972181;
Mon, 01 Feb 2016 11:29:32 -0800 (PST)
Received: by 10.79.77.65 with HTTP; Mon, 1 Feb 2016 11:29:32 -0800 (PST)
In-Reply-To: <CAPg+sBgH0SegmFemRPA1BdAjgM=u3SZK=FDkZkbpuobEUQ1YHw@mail.gmail.com>
References: <20160128185124.GA5140@savin.petertodd.org>
<CAPg+sBgH0SegmFemRPA1BdAjgM=u3SZK=FDkZkbpuobEUQ1YHw@mail.gmail.com>
Date: Mon, 1 Feb 2016 19:29:32 +0000
Message-ID: <CAE-z3OWoeBbX2yJOiBanToytf5AAOnERNBe-XFDL+Sfv-KZe2w@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=089e013a22687e8e8f052aba67e0
X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_IMAGE_ONLY_28,
HTML_MESSAGE,
MALFORMED_FREEMAIL,MISSING_HEADERS,RCVD_IN_DNSWL_LOW,T_REMOTE_IMAGE
autolearn=no version=3.3.1
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Segwit Upgrade Procedures & Block Extension Data
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 01 Feb 2016 19:29:33 -0000
--089e013a22687e8e8f052aba67e0
Content-Type: text/plain; charset=UTF-8
On Mon, Feb 1, 2016 at 4:55 PM, Pieter Wuille via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> * The coinbase scriptSig gets a second number push (similar to the
> current BIP34 height push), which pushes a number O. O is a byte
> offset inside the coinbase transaction (excluding its witness data)
> that points to a 32-byte hash H. This is more flexible and more
> compact than what we have now (a suggestion by jl2012).
>
So, the script sig is "<height> <offset> ..... <H>"?
Why is this just not the offset in the extra nonce?
> A significant design consideration is that if arbitrary data can be
> > added, it is very likely that miners will make use of that ability for
> > non-Bitcoin purposes;
> I agree with the concern, but I don't really understand how this idea
> solves it.
>
>
It could be enforced that the data in the coinbase witness stack has a
fixed number of entries, which depends on the block version number.
Version 5 blocks would only have 1 entry.
This would mean a soft-fork could be used to add new entries in the stack.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
This
email has been sent from a virus-free computer protected by Avast.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--089e013a22687e8e8f052aba67e0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Feb 1, 2016 at 4:55 PM, Pieter Wuille via bitcoin-dev <span dir=
=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" targe=
t=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
* The coinbase scriptSig gets a second number push (similar to the<br>
current BIP34 height push), which pushes a number O. O is a byte<br>
offset inside the coinbase transaction (excluding its witness data)<br>
that points to a 32-byte hash H. This is more flexible and more<br>
compact than what we have now (a suggestion by jl2012).<br></blockquote><di=
v><br></div><div>So, the script sig is=C2=A0 "<height> <offse=
t> ..... <H>"?<br></div><div>=C2=A0<br></div><div>Why is this=
just not the offset in the extra nonce?<br></div><div><br></div></div><div=
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
> A significant design consideration is that if arbitrary data can be<br=
>
> added, it is very likely that miners will make use of that ability for=
<br>
> non-Bitcoin purposes; <br>
</span>I agree with the concern, but I don't really understand how this=
idea solves it.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>It could be enforced that the data in the coinbase w=
itness stack has a fixed number of entries, which depends on the block vers=
ion number.=C2=A0 Version 5 blocks would only have 1 entry.<br><br></div><d=
iv>This would mean a soft-fork could be used to add new entries in the stac=
k. <br></div></div></div></div><div id=3D"DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9F=
DF2"><table style=3D"border-top:1px solid #aaabb6;margin-top:30px">
<tr>
<td style=3D"width:105px;padding-top:15px">
<a href=3D"https://www.avast.com/sig-email?utm_medium=3Demail&utm_so=
urce=3Dlink&utm_campaign=3Dsig-email&utm_content=3Dwebmail" target=
=3D"_blank"><img src=3D"https://ipmcdn.avast.com/images/logo-avast-v1.png" =
style=3D"width: 90px; height:33px;"></a>
</td>
<td style=3D"width:470px;padding-top:20px;color:#41424e;font-size:13px;fo=
nt-family:Arial,Helvetica,sans-serif;line-height:18px">This email has been =
sent from a virus-free computer protected by Avast. <br><a href=3D"https://=
www.avast.com/sig-email?utm_medium=3Demail&utm_source=3Dlink&utm_ca=
mpaign=3Dsig-email&utm_content=3Dwebmail" target=3D"_blank" style=3D"co=
lor:#4453ea">www.avast.com</a>
</td>
</tr>
</table><a href=3D"#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width=3D"1" heigh=
t=3D"1"></a></div>
--089e013a22687e8e8f052aba67e0--
|
