Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A369F7D for ; Fri, 25 Mar 2016 17:27:31 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3A2DBEB for ; Fri, 25 Mar 2016 17:27:31 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id fe3so50215118pab.1 for ; Fri, 25 Mar 2016 10:27:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=Thboz9lXsDDKZ4b/MunTA62Ewwr+GbQ/WCnQrqOMFuU=; b=qXYB+QiQQ1bxkENi5Vh4v/uk8NA3Zt6IsX+tYS1v6UXs/dHN1PKsbl/sy+HI8FRjhB MRMTJqomKHi964CxDWED3/OF+LSv00dj6wthrYtDASgSmVUHTp1DmPK+BabC4P+dR+sy Q6kn+kXuBYhaWb7/EHzRQIrZI0T1g7hik0/HHK2nED0tgslB2M8hnMUPb+wyBKGh0AQC x6W/QouvbcmxPe9akTs8xXKX/2GII0OCGraN2cTOff8sjAXpNNNsJdUm8JNt9+uavH0w Hs7O5uWeEuIvLIhIi70FXWyt5OyRt4wgtvSUbWYLP6QJ5GhVirjMb7B0eQgTP5bzCFjo zvLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=Thboz9lXsDDKZ4b/MunTA62Ewwr+GbQ/WCnQrqOMFuU=; b=Btp6hwHUdqM4PFtvLkb7u7yuwseH34Ty910hO/enbSyBfrpBzSERnMgejHvRUUfDUl CUPBfJdNlMGNo3oonnbFsKJi+whWYaDg/L8uL/AfnvuT+aBmsL7Bu61B/t7NHDRsGzTd mCb/JtXL4GRfYikyplkXN4rpDevaAatrXPhJQlXQzdb/xX/K5KH2C7VTjvmiz4wIySKW FkttyhGaVaViKdHXWAr/Zzk1dhGVBAoi2+VtnkpVPMgQrM3cBe5FSOKP0TBkcksRMTXs GX6RpMvzsI0RImb8Xmwc25+KEAZDIqp8LrcbglwAH5SAqZuf6r64JstEpgpWAbthFGQ+ hRYQ== X-Gm-Message-State: AD7BkJJ1Y7H1cePVYpFOFaz9d0Ooql8GTK5GXhRPgFeHfrNCb2TjuL/2igPb+7cCnJQUVdvLl9+9AYcqLGZ2kQ== MIME-Version: 1.0 X-Received: by 10.66.154.233 with SMTP id vr9mr22757168pab.66.1458926850956; Fri, 25 Mar 2016 10:27:30 -0700 (PDT) Received: by 10.66.111.193 with HTTP; Fri, 25 Mar 2016 10:27:30 -0700 (PDT) Date: Fri, 25 Mar 2016 13:27:30 -0400 Message-ID: From: Chris Kleeschulte To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary=047d7b6d83b6b46270052ee2e0dd X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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 X-Mailman-Approved-At: Fri, 25 Mar 2016 17:35:18 +0000 Subject: [bitcoin-dev] Proposed BIP: Maximum block size consensus rule based on median block size (adaptive block size) 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, 25 Mar 2016 17:27:31 -0000 --047d7b6d83b6b46270052ee2e0dd Content-Type: text/plain; charset=UTF-8 The following draft BIP proposes changing the MAX_BLOCK_SIZE consensus rule to be a function of the median block size over the last 12,960 blocks (about three months) multiplied by 2 and calculated when a block is connected to the blockchain. Motivation: The purpose of this consensus rule change is to allow the maximum block size to increase or decrease based on actual network usage. A block size limit, as discussed here, prevents certain types of denial of service attacks on the Bitcoin network, however a fixed limit does not allow the capacity of the network to increase as advancements in scaling are realized. By adjusting the limit based on the sizes of blocks in the recent past, the throughput of the network can adjust to changes in user demand and scaling related technology advancements while still being protected from denial of service attacks. Full proposal here: https://github.com/bitpay/bips/blob/master/bip-adaptiveblocksize.mediawiki I look forward to your consideration. thank you, -- Chris Kleeschulte --047d7b6d83b6b46270052ee2e0dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The following draft BIP proposes changing the MAX_BLOCK_SI= ZE consensus rule to be a function of the median block size over the last 1= 2,960 blocks (about three months) multiplied by 2 and calculated when a blo= ck is connected to the blockchain.

Motivation:

The purpose of this consensus rule change is to allow the m= aximum block size to increase or decrease based on actual network usage. A = block size limit, as discussed here, prevents certain types of denial of se= rvice attacks on the Bitcoin network, however a fixed limit does not allow = the capacity of the network to increase as advancements in scaling are real= ized.=C2=A0 By adjusting the limit based on the sizes of blocks in the rece= nt past, the throughput of the network can adjust to changes in user demand= and scaling related technology advancements while still being protected fr= om denial of service attacks.


Full = proposal here:


<= /div>
I look forward to your consideration.

th= ank you,
--
<= div dir=3D"ltr">
Chris Kleeschulte

=
--047d7b6d83b6b46270052ee2e0dd--