From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A99CD83D for ; Fri, 26 Jun 2015 19:07:40 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 28C24108 for ; Fri, 26 Jun 2015 19:07:40 +0000 (UTC) Received: by qcmc1 with SMTP id c1so32186500qcm.2 for ; Fri, 26 Jun 2015 12:07:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=gbdnX6xl2ytGbwLjS3hG4IFqrNNOt/aPnViHJl0dgwQ=; b=EItyQC13Mb4YsNhBzw1gLKXdRBOHyHbyssoKZ7XtUpazmv2Wmwcq1Yyz685OqkA+m1 CTcR9PGnW9OLub06zt6UliFYPxuL+FX0QqhKgH+wR3pvBrAmtAxiQqQncIaCxrOCLOsC pWaRB1VeClbTG9i4tsi0ceaBZm9wU0aj2yy3kqvUkuNzYi9yq60rkBSEK/AfmPOiKPXo f5x8DATtfr6IwpxgKe3F2LnPeRR8UVLN7HciaNkOl5BEz3zafErzGfXxvqhKFkP8wS2J E5QrLXq6u+kdNMMjcFx08Kz9on8rPanuem3doOat2agqmZYC6hz2yukMrBQ4wPxdrwb7 UBxA== X-Gm-Message-State: ALoCoQmn5X+VtKi+mkytyKTK1XwTwt2JEvtWeYW4iB8pYhTw9eJN67noO0+/MHwqOeh7tfpXHvQ+ X-Received: by 10.140.30.166 with SMTP id d35mr4350177qgd.85.1435345659477; Fri, 26 Jun 2015 12:07:39 -0700 (PDT) Received: from [10.125.67.236] (mobile-166-171-059-190.mycingular.net. [166.171.59.190]) by mx.google.com with ESMTPSA id q68sm7360379qgd.42.2015.06.26.12.07.37 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Jun 2015 12:07:38 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-E8F3CEFD-4951-4FBA-9DCD-AA222FD7CD90 Mime-Version: 1.0 (1.0) From: Will X-Mailer: iPhone Mail (12F70) In-Reply-To: Date: Fri, 26 Jun 2015 15:07:30 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <558A0B4A.7090205@riseup.net> <558A1E8E.30306@novauri.com> <0CAB4453-0C88-4CCB-86C1-DA192D4F77A1@gmail.com> <19956282-19CC-4150-8865-F211774AF70E@novauri.com> To: Gavin Andresen X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: "bitcoin-dev@lists.linuxfoundation.org" Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 19:07:40 -0000 --Apple-Mail-E8F3CEFD-4951-4FBA-9DCD-AA222FD7CD90 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Moving averages have upsides and downsides vs fixed growth. Moving averages= are backwards looking and don't handle seasonalities or unanticipated incre= ases in demand very well. Think "Black Friday" or the horribly named "Cyber=20 Monday" in retail or market hysteria where millions of noobs jump into or ou= t of bitcoin. If you want to create fee pressure I think this can be done, but I would kee= p both of these in mind before choosing a value for N. Adjustments would ne= ed to be frequent and nimble enough to handle seasonalities and other unanti= cipated outliers. > On Jun 26, 2015, at 1:39 PM, Gavin Andresen wrot= e: >=20 >> On Fri, Jun 26, 2015 at 11:13 AM, Will wrote: >> Make the lazy miners' default choice grow at the hard cap growth rate and= you should be ok if you want voting. >=20 > I think the default block size is an orthogonal issue to the max block siz= e. >=20 > HOWEVER: I think changing the default 'target' block size from the current= , fixed 750K to the average of the size of the last N blocks would have some= nice properties. It is policy-neutral (we should get out of the business of= deciding the right block size and let the miners who care drive block size u= p or down) and if there are a significant proportion of lazy miners going wi= th defaults it gives the system a healthy "fee pressure." >=20 > --=20 > -- > Gavin Andresen --Apple-Mail-E8F3CEFD-4951-4FBA-9DCD-AA222FD7CD90 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Moving averages have upsides and downs= ides vs fixed growth.  Moving averages are backwards looking and don't h= andle seasonalities or unanticipated increases in demand very well.

Think "Black Friday" or the horribly named "Cyber 
Monday" in retail or market hysteria where millions of noobs jump int= o or out of bitcoin.

If you want to create fee pres= sure I think this can be done, but I would keep both of these in mind before= choosing a value for N.  Adjustments would need to be frequent and nim= ble enough to handle seasonalities and other unanticipated outliers.

On Jun 26, 2015, at 1:39 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:

On Fri, Jun 26, 2015 at 11:13 AM, Will <will.m= adden@novauri.com> wrote:
Mak= e the lazy miners' default choice grow at the hard cap growth rate and you s= hould be ok if you want voting.

I think the default bl= ock size is an orthogonal issue to the max block size.

HOWEVER: I think changing th= e default 'target' block size from the current, fixed 750K to the average of= the size of the last N blocks would have some nice properties. It is policy= -neutral (we should get out of the business of deciding the right block size= and let the miners who care drive block size up or down) and if there are a= significant proportion of lazy miners going with defaults it gives the syst= em a healthy "fee pressure."

= --
--
Gavin Andresen
= --Apple-Mail-E8F3CEFD-4951-4FBA-9DCD-AA222FD7CD90--