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
|
Return-Path: <flyingkiwiguy@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CF01A514
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Jul 2015 16:57:06 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f180.google.com (mail-yk0-f180.google.com
[209.85.160.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F990ED
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Jul 2015 16:57:03 +0000 (UTC)
Received: by ykax123 with SMTP id x123so38990354yka.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 30 Jul 2015 09:57:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=nXwo/zgjTWngypPR+b4He1G0eWcQnqL0b6Kec3+B8WM=;
b=ttpWrITwPo6OZZ99J2478zwrAfMEl9ligHxu8hkyyUOyv07WChvgbxrF3R5NxCFmu2
uMReQZ+Ht3b7mXG4f/ro7vs1drF9LE67yjYO5zfkJitaG8p0IwIwxz56qCupnMfTAOj9
y0luh+8lQ2bCKIsltBqOOnKaSVPtfRlTDmyeKlr33VBJ3eY2B5eQUDijYkPytQWcvfXG
fPHeU/3xN+UT32LtOi83Wr4k+ygKUfKWren8qhbDfpMHpQXhqsnWsBoV6vEljhL7DSEm
jscLO2X9ateG3cVQFh2haaOE92uCS/mVFKW00p0d8axObajiw1bvFD+pOnjUPSgvc1we
o/0Q==
X-Received: by 10.13.204.150 with SMTP id o144mr52859464ywd.54.1438275423023;
Thu, 30 Jul 2015 09:57:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.74.8 with HTTP; Thu, 30 Jul 2015 09:56:23 -0700 (PDT)
In-Reply-To: <CABm2gDrHjfkC+whh3Vh2LZNdSR1WSAXpNitR-jEdxtbKj7J25g@mail.gmail.com>
References: <CAPg+sBj-wA1DMrwkQRWnzQoB5NR-q=2-5=WDAAUYfSpXRZSTqw@mail.gmail.com>
<CABm2gDrHjfkC+whh3Vh2LZNdSR1WSAXpNitR-jEdxtbKj7J25g@mail.gmail.com>
From: Gary Mulder <flyingkiwiguy@gmail.com>
Date: Thu, 30 Jul 2015 17:56:23 +0100
Message-ID: <CAKy9zTA1j6311Y8uo-c_z2JQr8gEwf_gH+HH56rRgZac9fqh9Q@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=001a114e43a6adb56c051c1a9766
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Block size following technological growth
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: Thu, 30 Jul 2015 16:57:06 -0000
--001a114e43a6adb56c051c1a9766
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On 30 July 2015 at 16:12, Jorge Tim=C3=B3n <bitcoin-dev@lists.linuxfoundati=
on.org
> wrote:
> 1) Unlike previous blocksize hardfork proposals, this uses median time
> instead of block.nTime for activation. I like that more but my
> preference is still using height for everything. But that discussion
> is not specific to this proposal, so it's better if we discuss that
> for all of them here:
>
> http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009731.h=
tml
Note that a "median" is a special case of a 50% percentile. If you desire
to apply a more stringent criteria you can use the 75th or even 90th
percentile.
https://en.wikipedia.org/wiki/Percentile
Perhaps if a statistician (i.e. not me) could be found to offer her
services, she could become a resource for helping selecting the most
appropriate statistical algorithms on request (and implemented Integer math
as per Gavin, from memory), considering the consequences of learning
post-fork that a "bad statistical model" was chosen.
e.g. an exponentially weighted moving average is usually much less volatile
and harder to manipulate than a simple moving average, but still can
"respond" to short term drivers.
Regards,
Gary
--001a114e43a6adb56c051c1a9766
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><span style=3D"font-size:12.800=
0001907349px">On 30 July 2015 at 16:12, Jorge Tim=C3=B3n=C2=A0</span><span =
dir=3D"ltr" style=3D"font-size:12.8000001907349px"><<a href=3D"mailto:bi=
tcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.li=
nuxfoundation.org</a>></span><span style=3D"font-size:12.8000001907349px=
">=C2=A0wrote:</span><br style=3D"font-size:12.8000001907349px"><blockquote=
class=3D"gmail_quote" style=3D"font-size:12.8000001907349px;margin:0px 0px=
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-=
left-style:solid;padding-left:1ex">1) Unlike previous blocksize hardfork pr=
oposals, this uses median time<br>instead of block.nTime for activation. I =
like that more but my<br>preference is still using height for everything. B=
ut that discussion<br>is not specific to this proposal, so it's better =
if we discuss that<br>for all of them here:<br><a href=3D"http://lists.linu=
xfoundation.org/pipermail/bitcoin-dev/2015-July/009731.html" rel=3D"norefer=
rer" target=3D"_blank">http://lists.linuxfoundation.org/pipermail/bitcoin-d=
ev/2015-July/009731.html</a></blockquote><div style=3D"font-size:12.8000001=
907349px"><br></div><div style=3D"font-size:12.8000001907349px">Note that a=
"median" is a special case of a 50% percentile. If you desire to=
apply a more stringent criteria you can use the 75th or even 90th percenti=
le.</div><div style=3D"font-size:12.8000001907349px"><br></div><div style=
=3D"font-size:12.8000001907349px"><a href=3D"https://en.wikipedia.org/wiki/=
Percentile" target=3D"_blank">https://en.wikipedia.org/wiki/Percentile</a><=
br></div><div style=3D"font-size:12.8000001907349px"><br></div><div style=
=3D"font-size:12.8000001907349px">Perhaps if a statistician (i.e. not me) c=
ould be found to offer her services, she could become a resource for helpin=
g selecting the most appropriate statistical algorithms on request (and imp=
lemented Integer math as per Gavin, from memory), considering the consequen=
ces of learning post-fork that a "bad statistical model" was chos=
en.</div><div style=3D"font-size:12.8000001907349px"><br></div><div style=
=3D"font-size:12.8000001907349px">e.g. an exponentially weighted moving ave=
rage is usually much less volatile and harder to manipulate than a simple m=
oving average, but still can "respond" to short term drivers.=C2=
=A0</div><div style=3D"font-size:12.8000001907349px"><br></div><div style=
=3D"font-size:12.8000001907349px">Regards,</div><div style=3D"font-size:12.=
8000001907349px">Gary</div></div></div>
--001a114e43a6adb56c051c1a9766--
|
