Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 6A8F210C6 for ; Thu, 3 Sep 2015 18:23:59 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F364A203 for ; Thu, 3 Sep 2015 18:23:58 +0000 (UTC) Received: by pacwi10 with SMTP id wi10so53944902pac.3 for ; Thu, 03 Sep 2015 11:23:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=v7YUU7vPIkSzn3up4oaoP4ZzdsraEs/bDC+g1d4Fp4U=; b=k2rv1LiVmfIvRpTSx77P+ZDwz0BVsRi/grIIznFA7hLzDFCqGqxt4oE2sBcYBWVeO2 aCKuPYbJVtSkvSb5HB6UYii3Rrk1SMLUp+aMVXm7IardiVFdYxyB06trnVaPp9rRLUyC umgUrPJkgnqhNz17BvXSsQUn4ygxfvw+H61iv340BrjBAcYwNb2K59+Ljz8IUM0JFaRM uqkOuLDfcHtf2RW6DeScu2tuIYlH5UESVFdG/CWl6NwOTMy7MVRR2JPDd3Rs0VU7ko4p ++HyuCdc+YBmWjgvJxC2Mv5JQHyI2L2zR6rVmedu76KuZqSqF/YS2bDlSIpgXb7MrhgB tgUA== X-Gm-Message-State: ALoCoQkMvbTyf9z4457VLtZPV3C2rIJj38Hyt/vYQk7CmTpbx3WLzX7XWSINDhoBdklGn26nczHR X-Received: by 10.66.117.200 with SMTP id kg8mr11749758pab.37.1441304638722; Thu, 03 Sep 2015 11:23:58 -0700 (PDT) Received: from [10.100.1.239] ([204.58.254.99]) by smtp.googlemail.com with ESMTPSA id ob4sm26029209pbb.40.2015.09.03.11.23.57 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 11:23:57 -0700 (PDT) To: bitcoin-dev@lists.linuxfoundation.org References: From: Tom Harding Message-ID: <55E8900F.4050007@thinlink.com> Date: Thu, 3 Sep 2015 11:23:11 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_SORBS_WEB autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] block size - pay with difficulty 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: Thu, 03 Sep 2015 18:23:59 -0000 On 9/2/2015 9:05 PM, Jeff Garzik via bitcoin-dev wrote: > Schemes proposing to pay with difficulty / hashpower to change block > size should be avoided. The miners incentive has always been fairly > straightforward - it is rational to deploy new hashpower as soon as > you can get it online. Introducing the concepts of (a) requiring > out-of-band collusion to change block size and/or (b) requiring miners > to have idle hashpower on hand to change block size are both > unrealistic and potentially corrosive. That potentially makes the > block size - and therefore fee market - too close, too sensitive to > the wild vagaries of the mining chip market. > > Pay-to-future-miner has neutral, forward looking incentives worth > researching. > Another market dependency is even more direct. Blocksize that can be bought with either difficulty or bitcoin has incentives whose strength (though not direction) is subject to the exchange rate. Hence those incentives are subject to the whims of fiat holders, who can push the exchange rate around.