From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqcYn-00030V-6C for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 07:19:01 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.176 as permitted sender) client-ip=209.85.216.176; envelope-from=mickeybob@gmail.com; helo=mail-qc0-f176.google.com; Received: from mail-qc0-f176.google.com ([209.85.216.176]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqcYm-0000xK-FR for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 07:19:01 +0000 Received: by qcbgy10 with SMTP id gy10so33158292qcb.3 for ; Fri, 08 May 2015 00:18:55 -0700 (PDT) X-Received: by 10.140.31.133 with SMTP id f5mr3108099qgf.23.1431069535088; Fri, 08 May 2015 00:18:55 -0700 (PDT) Received: from [192.168.1.119] (173-22-35-150.client.mchsi.com. [173.22.35.150]) by mx.google.com with ESMTPSA id 21sm3073012qks.47.2015.05.08.00.18.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 May 2015 00:18:53 -0700 (PDT) From: Michael Naber Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (12B435) Message-Id: Date: Fri, 8 May 2015 03:18:51 -0400 To: "bitcoin-development@lists.sourceforge.net" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mickeybob[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1YqcYm-0000xK-FR Subject: [Bitcoin-development] Suggestion: Dynamic block size that updates like difficulty 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: Fri, 08 May 2015 07:19:01 -0000 Why can't we have dynamic block size limit that changes with difficulty, suc= h as the block size cannot exceed 2x the mean size of the prior difficulty p= eriod?=20 I recently subscribed to this list so my apologies if this has been addresse= d already.