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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1YqP8r-0006oF-Fu
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 16:59:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.49 as permitted sender)
client-ip=209.85.215.49; envelope-from=gavinandresen@gmail.com;
helo=mail-la0-f49.google.com;
Received: from mail-la0-f49.google.com ([209.85.215.49])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YqP8q-0008LE-4Z
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 16:59:21 +0000
Received: by labbd9 with SMTP id bd9so35278392lab.2
for <bitcoin-development@lists.sourceforge.net>;
Thu, 07 May 2015 09:59:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.4.72 with SMTP id i8mr3967262lai.32.1431017953760; Thu,
07 May 2015 09:59:13 -0700 (PDT)
Received: by 10.25.90.75 with HTTP; Thu, 7 May 2015 09:59:13 -0700 (PDT)
In-Reply-To: <CABm2gDq12a8p8+fB14nM5S8CVz=sdESMowZJUeKBwvx16WDSDQ@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
<CABm2gDpgBNjuPLnFiU2TspgLws7JjWnsxih09JG9bQycraS=sQ@mail.gmail.com>
<CANEZrP1ay64jryeUyDJ9Y+1C-Bre1U_1xMyuB4cqQprd1-qbCA@mail.gmail.com>
<CABm2gDq12a8p8+fB14nM5S8CVz=sdESMowZJUeKBwvx16WDSDQ@mail.gmail.com>
Date: Thu, 7 May 2015 12:59:13 -0400
Message-ID: <CABsx9T1nwastEoN12B2Y-TA2V1fYtDcm9-nkiOQNVhXmbCjcGQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=089e01494248cd1e48051580d4d5
X-Spam-Score: -0.6 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YqP8q-0008LE-4Z
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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: Thu, 07 May 2015 16:59:21 -0000
--089e01494248cd1e48051580d4d5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Fee dynamics seems to come up over and over again in these discussions,
with lots of talk and theorizing.
I hope some data on what is happening with fees right now might help, so I
wrote another blog post (with graphs, which can't be done in a mailing list
post):
http://gavinandresen.ninja/the-myth-of-not-full-blocks
We don=E2=80=99t need 100% full one megabyte blocks to start to learn about=
what is
likely to happen as transaction volume rises and/or the one megabyte block
size limit is raised.
--=20
--
Gavin Andresen
--089e01494248cd1e48051580d4d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div>Fee dynamics seems to come=
up over and over again in these discussions, with lots of talk and theoriz=
ing.</div><div><br></div><div>I hope some data on what is happening with fe=
es right now might help, so I wrote another blog post (with graphs, which c=
an't be done in a mailing list post):</div><div>=C2=A0 =C2=A0<a href=3D=
"http://gavinandresen.ninja/the-myth-of-not-full-blocks">http://gavinandres=
en.ninja/the-myth-of-not-full-blocks</a></div><div><br></div>We don=E2=80=
=99t need 100% full one megabyte blocks to start to learn about what is lik=
ely to happen as transaction volume rises and/or the one megabyte block siz=
e limit is raised.<br></div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">-- <br><div class=3D"gmail_signature">--<br>Gavin Andresen=
<br></div>
</div></div>
--089e01494248cd1e48051580d4d5--
|
