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
161
162
163
164
165
|
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 3756A481
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 May 2017 02:42:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f182.google.com (mail-qt0-f182.google.com
[209.85.216.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BE947284
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 May 2017 02:42:31 +0000 (UTC)
Received: by mail-qt0-f182.google.com with SMTP id v27so144423494qtg.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 23 May 2017 19:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:reply-to:in-reply-to:references:from:date:message-id
:subject:to:cc;
bh=YZREkcGU8gACMm9oJ6mhwEkxc0tP8zj9vIyhfHHQ+gs=;
b=H8dIpLVg1ybmRiZrWyDt9qg1FC663Yac7O4QB4uUEilx+iVCCRJ9Xn+6l/dRF5Dsj6
G1p8x2q5qwEs6ZrCinADJqfYVJQ8976reRbjJOTg5OfH1LtzKB3bjQpIpjHj8EvKyTNb
lVMILOEIp2nFmCGSuUEddhtEpN+eGly8dHtMChP8RQFK9TncfGiPScDxjSYZkTkifQ+t
oeHqEJYzHtPh84S0867rwxi8KJsnV7yxQqO6yFdlI1Qp2+jDCdZyokrbuni3oquWZOUV
t7q9DUgEZWp0jnrLENPibVubtIthYOcJzfoI16laMEKdnsWIv77/h39k0E1CWeZvTeQ+
kLKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:reply-to:in-reply-to:references
:from:date:message-id:subject:to:cc;
bh=YZREkcGU8gACMm9oJ6mhwEkxc0tP8zj9vIyhfHHQ+gs=;
b=LZAk2N4s+pFJUyX67W0NV0rmsyx54srNI26R5FsUUN/Y1IVL0jd9o1Fty5pWfuozdP
cIyp9bRVHMMU9fDe34Upyd5j2qvLc5jD4wO66179RvWQ02UigYujxdOftbdUTA0KfNbD
0yRRYFnTDEQgoIPsjbuGWMyW2GYaASVzpLDT8czx/AAH1CLTCywQWU5IS4qxuGqokIq4
rAuWUd3jN5iyf9hY/qIQyjTceIqYOC7xVevI6J7lBvuffpj4CjP2PJRi5CBHE265hr48
Gtgt9x+mhhoJVeLEJc2wmvGTDrRf9ra+nVfwKk9DEwHIos495quZ/FHQmgMOPqWDb6cW
CeDw==
X-Gm-Message-State: AODbwcB/SPnb+K+ExCR+pBurS3qenrqeKMbd97P3K95ZkikvZ93e6ERE
VV/bRMYs18km+W4iYCJf1YxUK2ge6oOs
X-Received: by 10.237.53.229 with SMTP id d34mr33364313qte.46.1495593750979;
Tue, 23 May 2017 19:42:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.48.102 with HTTP; Tue, 23 May 2017 19:42:30 -0700 (PDT)
Received: by 10.237.48.102 with HTTP; Tue, 23 May 2017 19:42:30 -0700 (PDT)
Reply-To: erik@q32.com
In-Reply-To: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com>
References: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com>
From: Erik Aronesty <earonesty@gmail.com>
Date: Tue, 23 May 2017 22:42:30 -0400
Message-ID: <CAJowKgJs-cVR7w1QvSKr+ZXeQd4giq-aGLOEktqHn3a83tNGBA@mail.gmail.com>
To: Tomas <tomas@tomasvdw.nl>
Content-Type: multipart/alternative; boundary="001a11c00a484167c205503c0ebb"
X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_LOW,
RCVD_IN_SORBS_SPAM 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, 24 May 2017 02:43:15 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal to allow users to configure the maximum
block weight based on a support threshold
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: Wed, 24 May 2017 02:42:32 -0000
--001a11c00a484167c205503c0ebb
Content-Type: text/plain; charset="UTF-8"
Instead of block thresholds, use utxo bits to coordinate size changes
(larger and smaller should be allowed).
There is no reason for miners to be involved in a decision to change this
aspects of the protocol. Plenty of other ways to coordinate.
Otherwise someone can make it seem to a miner like 99pct of nodes are ready
for a larger weight.... even though that's false.
On May 23, 2017 8:03 AM, "Tomas via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I have a proposal that would allow each user to optionally configure the
> maximum block weight at a support threshold.
>
> It recognizes that there is no need for off chain bickering, by
> providing a mechanism that lets each users freely choose their own
> parameters while still maintaining full coordination of any changes.
>
> The BIP can be found here:
>
> https://github.com/tomasvdw/bips/blob/master/bip-changing-
> the-maximum-block%20weight-based-on-a-support-threshold.mediawiki
>
> It is worth noting that this proposal does neither gives more power to
> miners nor reduces decentralization. Miners still rely on their blocks
> being accepted by economic nodes to sell their minted coins. This
> proposal doesn't change that.
>
> Regards,
> Tomas van der Wansem
> bitcrust
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a11c00a484167c205503c0ebb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Instead of block thresholds, use utxo bits to coordinate =
size changes (larger and smaller should be allowed).<div dir=3D"auto"><br><=
/div><div dir=3D"auto">There is no reason for miners to be involved in a de=
cision to change this aspects of the protocol. =C2=A0 Plenty of other ways =
to coordinate.<br><div dir=3D"auto"><br></div><div dir=3D"auto">Otherwise s=
omeone can make it seem to a miner like 99pct of nodes are ready for a larg=
er weight.... even though that's false.</div></div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On May 23, 2017 8:03 AM, "=
Tomas via bitcoin-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfo=
undation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br type=
=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">I have a proposal that woul=
d allow each user to optionally configure the<br>
maximum block weight at a support threshold.<br>
<br>
It recognizes that there is no need for off chain bickering, by<br>
providing a mechanism that lets each users freely choose their own<br>
parameters while still maintaining full coordination of any changes.<br>
<br>
The BIP can be found here:<br>
<br>
<a href=3D"https://github.com/tomasvdw/bips/blob/master/bip-changing-the-ma=
ximum-block%20weight-based-on-a-support-threshold.mediawiki" rel=3D"norefer=
rer" target=3D"_blank">https://github.com/tomasvdw/<wbr>bips/blob/master/bi=
p-changing-<wbr>the-maximum-block%20weight-<wbr>based-on-a-support-threshol=
d.<wbr>mediawiki</a><br>
<br>
It is worth noting that this proposal does neither gives more power to<br>
miners nor reduces decentralization. Miners still rely on their blocks<br>
being accepted by economic nodes to sell their minted coins. This<br>
proposal doesn't change that.<br>
<br>
Regards,<br>
Tomas van der Wansem<br>
bitcrust<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></div>
--001a11c00a484167c205503c0ebb--
|
