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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1Yqhi3-00026V-2r
for bitcoin-development@lists.sourceforge.net;
Fri, 08 May 2015 12:48:55 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.51 as permitted sender)
client-ip=209.85.215.51; envelope-from=gavinandresen@gmail.com;
helo=mail-la0-f51.google.com;
Received: from mail-la0-f51.google.com ([209.85.215.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yqhi2-0002z9-54
for bitcoin-development@lists.sourceforge.net;
Fri, 08 May 2015 12:48:55 +0000
Received: by labbd9 with SMTP id bd9so51918699lab.2
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 May 2015 05:48:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.5.134 with SMTP id s6mr2648987las.99.1431089327780; Fri,
08 May 2015 05:48:47 -0700 (PDT)
Received: by 10.25.90.75 with HTTP; Fri, 8 May 2015 05:48:47 -0700 (PDT)
In-Reply-To: <CAGKSKfW7fJB6n3B-OoyXOep7hAQqWGGDTiZCkpJ7vXxWRFgveA@mail.gmail.com>
References: <16096345.A1MpJQQkRW@crushinator>
<CAP63atbdFSw0rDeuwgtjsDYsXnKSHNN9=zedzip2MsZ0hSY59w@mail.gmail.com>
<CAGKSKfW7fJB6n3B-OoyXOep7hAQqWGGDTiZCkpJ7vXxWRFgveA@mail.gmail.com>
Date: Fri, 8 May 2015 08:48:47 -0400
Message-ID: <CABsx9T0y2sQzV6suxD9H0g37tqorsBSNs9AGHP+AVncRFkD+GQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
Content-Type: multipart/alternative; boundary=089e013d1010063b74051591737d
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: 1Yqhi2-0002z9-54
Cc: Bitcoin Development <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: Fri, 08 May 2015 12:48:55 -0000
--089e013d1010063b74051591737d
Content-Type: text/plain; charset=UTF-8
I like the bitcoin days destroyed idea.
I like lots of the ideas that have been presented here, on the bitcointalk
forums, etc etc etc.
It is easy to make a proposal, it is hard to wade through all of the
proposals. I'm going to balance that equation by completely ignoring any
proposal that isn't accompanied by code that implements the proposal (with
appropriate tests).
However, I'm not the bottleneck-- you need to get the attention of the
other committers and convince THEM:
a) something should be done "now-ish"
b) your idea is good
We are stuck on (a) right now, I think.
On Fri, May 8, 2015 at 8:32 AM, Joel Joonatan Kaartinen <
joel.kaartinen@gmail.com> wrote:
> Matt,
>
> It seems you missed my suggestion about basing the maximum block size on
> the bitcoin days destroyed in transactions that are included in the block.
> I think it has potential for both scaling as well as keeping up a constant
> fee pressure. If tuned properly, it should both stop spamming and increase
> block size maximum when there are a lot of real transactions waiting for
> inclusion.
>
> - Joel
>
--
--
Gavin Andresen
--089e013d1010063b74051591737d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I like the bitcoin days destroyed idea.<div><br></div><div=
>I like lots of the ideas that have been presented here, on the bitcointalk=
forums, etc etc etc.</div><div><br></div><div>It is easy to make a proposa=
l, it is hard to wade through all of the proposals. I'm going to balanc=
e that equation by completely ignoring any proposal that isn't accompan=
ied by code that implements the proposal (with appropriate tests).</div><di=
v><br></div><div>However, I'm not the bottleneck-- you need to get the =
attention of the other committers and convince THEM:</div><div><br></div><d=
iv>a) something should be done "now-ish"<br></div><div><div>b) yo=
ur idea is good</div></div><div><br></div><div>We are stuck on (a) right no=
w, I think.</div><div><br></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, May 8, 2015 at 8:32 AM, Joel Joonatan Kaartinen <s=
pan dir=3D"ltr"><<a href=3D"mailto:joel.kaartinen@gmail.com" target=3D"_=
blank">joel.kaartinen@gmail.com</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div>Matt,</div><div><br></div>It seems you =
missed my suggestion about basing the maximum block size on the bitcoin day=
s destroyed in transactions that are included in the block. I think it has =
potential for both scaling as well as keeping up a constant fee pressure. I=
f tuned properly, it should both stop spamming and increase block size maxi=
mum when there are a lot of real transactions waiting for inclusion.<span c=
lass=3D"HOEnZb"><font color=3D"#888888"><div><br></div></font></span><div><=
span class=3D"HOEnZb"><font color=3D"#888888">- Joel</font></span></div></d=
iv></blockquote></div><br clear=3D"all"><div><br></div>-- <br><div class=3D=
"gmail_signature">--<br>Gavin Andresen<br></div>
</div></div>
--089e013d1010063b74051591737d--
|
