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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marcel@jamin.net>) id 1YzOz4-0004XF-G2
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 12:38:26 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of jamin.net
designates 209.85.213.42 as permitted sender)
client-ip=209.85.213.42; envelope-from=marcel@jamin.net;
helo=mail-yh0-f42.google.com;
Received: from mail-yh0-f42.google.com ([209.85.213.42])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YzOz3-0001S8-BR
for bitcoin-development@lists.sourceforge.net;
Mon, 01 Jun 2015 12:38:26 +0000
Received: by yhom41 with SMTP id m41so32739620yho.1
for <bitcoin-development@lists.sourceforge.net>;
Mon, 01 Jun 2015 05:38:19 -0700 (PDT)
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:to:cc:content-type;
bh=pwtg2EvTi/Ds5nKUpvu+MNDEOgvPijtFkEx6NdslWuw=;
b=UgjQQMPrBKdkdSXGNN6IxDfsoPYoZhRGqSFGDaJ34lPBCezt6lDxS+JvyF1OijlTWf
gE/uPqS9t3OHGmN6lWirJS7Whd3XoN/bdPUDh/+YBfXm7PovFkjraD3jFPZYzGzh5xY2
l8Z5PT1tAxQaJkmNPFM0fIYY8MHRGiFxvexNxHOASjHsXS2P7dM3BgMIqnIQSx8zvxAC
QWPcL+F1Sqt+s+h2sByxTEV/XiPjQq9IZbuobPgXFJabgzh0+lBFcHLNrnQNy7nozmOT
gmuQ6lmNhbITEtUBazDFkfMVWnksSJzlXqcUF0/hy89IGyzd08jzFvL34U3C7FZOOn6e
LNjg==
X-Gm-Message-State: ALoCoQkfPXtlgCKFkFiAkHIkATYUM+FYGWHJD1W7CDkcb+3kU2GSIPfu3vexIMErncuJHNs0keSz
MIME-Version: 1.0
X-Received: by 10.170.71.5 with SMTP id n5mr25237754ykn.85.1433159191009; Mon,
01 Jun 2015 04:46:31 -0700 (PDT)
Received: by 10.13.224.7 with HTTP; Mon, 1 Jun 2015 04:46:30 -0700 (PDT)
In-Reply-To: <CALC81CNidPEgLpTVCRWqXYn0UpSCU-nuo5S85NSQ4UCce=n4EA@mail.gmail.com>
References: <16096345.A1MpJQQkRW@crushinator>
<CABsx9T3-zxCAagAS0megd06xvG5n-3tUL9NUK9TT3vt7XNL9Tg@mail.gmail.com>
<CANEZrP3VCaFsW4+gPm2kCJ9z7oVUZYVaeNf=_cJWEWwh4ZxiPQ@mail.gmail.com>
<CABsx9T21zjHyO-nh1aSBM3z4Bg015O0rOfYq7=Sy4mf=QxUVQA@mail.gmail.com>
<CANEZrP2BaKwhpPgcUHWAHswOmUeFLgEk4ysrn4+73qNzWDJ=yQ@mail.gmail.com>
<CABsx9T3nCJ-w_v-yEbEE2Ytb+xC65mhYqhoAhoOHw9tkPpG0TA@mail.gmail.com>
<CANEZrP1qH+zucYsGrMgnfi99e61Edxaj+xm=u_xYXga1g0WzJQ@mail.gmail.com>
<CAE-z3OVmw+0doCe0hmYE6A1D61h0AUh4Mtnf5Fg1e4zQBkpraQ@mail.gmail.com>
<CANEZrP0psA7hcJdKdA-r01UEt7ig3O-9vjwBMqKSEq-csu0hPQ@mail.gmail.com>
<CABsx9T23r_y2R9OEgqb3AAZf47Hh8BUJncjxxmPp5v_9uKEiqQ@mail.gmail.com>
<CA+VAk3O7SmDkxL9rATWe9oqCVVKcT=cFXDJnARPN8pv=UiHaiA@mail.gmail.com>
<CACq0ZD7-qr4BCdnqOSXLYv-i58vAXWGcQ1oLsrbHoNFMeiNTtg@mail.gmail.com>
<CALC81CNidPEgLpTVCRWqXYn0UpSCU-nuo5S85NSQ4UCce=n4EA@mail.gmail.com>
Date: Mon, 1 Jun 2015 13:46:30 +0200
Message-ID: <CAAUq484AGnEm91TAUJzLUHdxyNTERJ=FtT3w5UYc+oiFVOaq1w@mail.gmail.com>
From: Marcel Jamin <marcel@jamin.net>
To: Ricardo Filipe <ricardojdfilipe@gmail.com>
Content-Type: multipart/alternative; boundary=001a1139e66c7cb18405177360cd
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YzOz3-0001S8-BR
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
function
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2015 12:38:26 -0000
--001a1139e66c7cb18405177360cd
Content-Type: text/plain; charset=UTF-8
> Let the block size limit be a function of the number of current transactions
in the mempool.
There is no single mempool which transactions could be counted and there is
no consensus about the average number of unconfirmed transactions.
2015-06-01 13:30 GMT+02:00 Ricardo Filipe <ricardojdfilipe@gmail.com>:
> I've been following the discussion of the block size limit and IMO it
> is clear that any constant block size limit is, as many have said
> before, just kicking the can down the road.
> My problem with the dynamic lower limit solution based on past blocks
> is that it doesn't account for usage spikes. I would like to propose
> another dynamic lower limit scheme:
> Let the block size limit be a function of the number of current
> transactions in the mempool. This way, bitcoin usage regulates the
> block size limit.
>
> I'm sorry i don't have the knowledge of the code base or time to make
> simulations on this kind of approach, but nevertheless I would like to
> leave it here for discussion or foster other ideas.
>
> cheers
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a1139e66c7cb18405177360cd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>>=C2=A0<span style=3D"font-size:12.8000001907349px=
">Let the block size limit be a function of the number of current=C2=A0</sp=
an><span style=3D"font-size:12.8000001907349px">transactions in the mempool=
.</span></div><div><br></div><div>There is no single mempool which transact=
ions could be counted and there is no consensus about the average number of=
unconfirmed transactions.</div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">2015-06-01 13:30 GMT+02:00 Ricardo Filipe <span dir=3D=
"ltr"><<a href=3D"mailto:ricardojdfilipe@gmail.com" target=3D"_blank">ri=
cardojdfilipe@gmail.com</a>></span>:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I=
've been following the discussion of the block size limit and IMO it<br=
>
is clear that any constant block size limit is, as many have said<br>
before, just kicking the can down the road.<br>
My problem with the dynamic lower limit solution based on past blocks<br>
is that it doesn't account for usage spikes. I would like to propose<br=
>
another dynamic lower limit scheme:<br>
Let the block size limit be a function of the number of current<br>
transactions in the mempool. This way, bitcoin usage regulates the<br>
block size limit.<br>
<br>
I'm sorry i don't have the knowledge of the code base or time to ma=
ke<br>
simulations on this kind of approach, but nevertheless I would like to<br>
leave it here for discussion or foster other ideas.<br>
<br>
cheers<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--001a1139e66c7cb18405177360cd--
|
