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; 
MIME-Version: 1.0
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
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
	function
Precedence: list

--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&#39;m going to balanc=
e that equation by completely ignoring any proposal that isn&#39;t accompan=
ied by code that implements the proposal (with appropriate tests).</div><di=
v><br></div><div>However, I&#39;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 &quot;now-ish&quot;<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">&lt;<a href=3D"mailto:joel.kaartinen@gmail.com" target=3D"_=
blank">joel.kaartinen@gmail.com</a>&gt;</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--