From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqR1T-0008Dr-3u for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 18:59:51 +0000 X-ACL-Warn: Received: from homie.mail.dreamhost.com ([208.97.132.208] helo=homiemail-a9.g.dreamhost.com) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YqR1R-0003pD-Op for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 18:59:51 +0000 Received: from homiemail-a9.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTP id 47030626070 for ; Thu, 7 May 2015 11:59:44 -0700 (PDT) Received: from [192.168.0.6] (cpc12-cmbg17-2-0-cust830.5-4.cable.virginm.net [86.30.131.63]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jrn@jrn.me.uk) by homiemail-a9.g.dreamhost.com (Postfix) with ESMTPSA id C84CE62606E for ; Thu, 7 May 2015 11:59:43 -0700 (PDT) Message-ID: <554BB61D.1040602@jrn.me.uk> Date: Thu, 07 May 2015 19:59:41 +0100 From: Ross Nicoll User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <554A91BE.6060105@bluematt.me> <554BA032.4040405@bluematt.me> In-Reply-To: Content-Type: multipart/alternative; boundary="------------030002080602000609090701" X-Spam-Score: 0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [208.97.132.208 listed in list.dnswl.org] 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YqR1R-0003pD-Op Subject: Re: [Bitcoin-development] Block Size Increase X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 18:59:51 -0000 This is a multi-part message in MIME format. --------------030002080602000609090701 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I'm presuming that schedule is just an example, as you'd end up with insanely large block sizes in a few years. Absolutely, yes, an increase schedule is an option if people agree on it, and I think the better option, as the current limit too low, but jumping straight to a value big enough for "indefinitely" is a huge jump. Gave some thought to scaling block size based on transaction fees, but suspect it would end up with miners sending huge fees to themselves with transactions that aren't relayed (so they only are actioned if they make it into a block that miner mines) to make the network allow bigger blocks. Ross On 07/05/2015 19:38, Chris Wardell wrote: > Instead of raising the block size to another static number like 20MB, > can we raise it dynamically? > > Make the max block size something like: > pow(2, nHeight/100000) * 1MB; //double every ~2 years > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development --------------030002080602000609090701 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm presuming that schedule is just an example, as you'd end up with insanely large block sizes in a few years.

Absolutely, yes, an increase schedule is an option if people agree on it, and I think the better option, as the current limit too low, but jumping straight to a value big enough for "indefinitely" is a huge jump.

Gave some thought to scaling block size based on transaction fees, but suspect it would end up with miners sending huge fees to themselves with transactions that aren't relayed (so they only are actioned if they make it into a block that miner mines) to make the network allow bigger blocks.

Ross

On 07/05/2015 19:38, Chris Wardell wrote:
Instead of raising the block size to another static number like 20MB, can we raise it dynamically?

Make the max block size something like:
pow(2, nHeight/100000) * 1MB;=A0 //double every ~2 years



----------------------------------------------------=
--------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud=20
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;11=
7567292;y


_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development

--------------030002080602000609090701--