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 10AD91BB for ; Fri, 31 Jul 2015 02:02:17 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BCDBAB0 for ; Fri, 31 Jul 2015 02:02:16 +0000 (UTC) Received: by pacan13 with SMTP id an13so32828014pac.1 for ; Thu, 30 Jul 2015 19:02:16 -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=e1/TR/+uS8BfIQOIlfKTRscy4JJ6d/rumHVJ7QF+BwI=; b=jGmdaSMXSAcvw+xaEPCCpdN+MjvsPZKnH6RhDFNMAZ4Gx7c5PSKKYR+W5NKMn+13Tn 4Mx61uez2dnbtPt70OK51y0JsweXDm5Hyzc0uFBcu+ztG+uAzP2nXN5mE/y7GgZ0ReIe 7O0YO7ZCNtYGPTRKOZJI1bFaF+RSpCi4a4jJRR8tS9qiiYuGTeSB/wrtQiv0As8YILT7 rmJ+/AVg2VxWgB7XPvZxBuiCarqJ6AN6xBe7AaMi7vIv/ZjVZX1h2Z5Hb3lm7LELlGI0 9v/WVJ9H3XdkKS/pnrOQrkzCuxIymILO6a8HrdaFZ7lNpE4ZPgW7sMoywFoYAfnBge5m cLGg== X-Gm-Message-State: ALoCoQnME/oT/P+6zBJFdXhxJovsSUQCveyS+SiIkRRl1HblUUEZXj1lexJlPht/gNRSSEav5MEM X-Received: by 10.66.145.195 with SMTP id sw3mr1001434pab.72.1438308136454; Thu, 30 Jul 2015 19:02:16 -0700 (PDT) Received: from [192.168.1.89] (99-8-65-117.lightspeed.davlca.sbcglobal.net. [99.8.65.117]) by smtp.googlemail.com with ESMTPSA id ex13sm4421537pac.17.2015.07.30.19.02.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jul 2015 19:02:15 -0700 (PDT) To: bitcoin-dev@lists.linuxfoundation.org References: From: Tom Harding X-Enigmail-Draft-Status: N1110 Message-ID: <55BAD726.8070200@thinlink.com> Date: Thu, 30 Jul 2015 19:02:14 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 Subject: Re: [bitcoin-dev] Another block size limit solution - dynamic block size limit. 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, 31 Jul 2015 02:02:17 -0000 On 7/30/2015 8:03 AM, Максим Божко via bitcoin-dev wrote: > I propose to implement dynamic block size limit. Its short summary is > here in doc: > > https://docs.google.com/document/d/1ixt0loN7LOF6M_2HXvV0D-3ZCayvcfj0rzVm-h-6ONg/edit > > A dynamic limit based on recent block sizes has been discussed, but with all the traffic on the list, finding the discussions is bound to be difficult. I think the main reason this kind of thing hasn't gotten traction is that it would allow miners alone to chart the course of block sizes. Miners are likely to have more powerful equipment than everybody else, and with the current network design, that could reduce the population of nodes able to keep up, with no limit in the loss of decentralization.