Return-Path: <Peter_R@gmx.com> Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1D9FA902 for <bitcoin-dev@lists.linuxfoundation.org>; Tue, 22 Nov 2016 16:31:56 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 09ED2125 for <bitcoin-dev@lists.linuxfoundation.org>; Tue, 22 Nov 2016 16:31:54 +0000 (UTC) Received: from [192.168.50.29] ([69.50.179.106]) by mail.gmx.com (mrgmx003 [212.227.17.184]) with ESMTPSA (Nemesis) id 0LmKag-1cj6hW2cCI-00ZuTb for <bitcoin-dev@lists.linuxfoundation.org>; Tue, 22 Nov 2016 17:31:53 +0100 From: Peter R <peter_r@gmx.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_B235C2DA-4E0F-481A-8EF3-5139D65C4074" Message-Id: <C10BF9D1-435D-47C9-B98C-9B118B5922A1@gmx.com> Date: Tue, 22 Nov 2016 08:31:50 -0800 To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Sender: <Peter_R@gmx.com> X-Provags-ID: V03:K0:X617QFc+/ECQesdPSiFoalfWKkBtRaKRgQBqTwddzkTCvLbibgA QwrucCfagiq1OjysTVv5ntfk4PvriLuqgEoiV8GeecKj/wypkYGAPitXc3IbAeB1nW9teG5 0/EImHFlWxlnfmBsT4TYJvvRZxexAArQpEQQduUxF8IrQq9GEfGk0KF7zvEpxVuq7VTeDGZ 0QWDyYE2TQd0e7WMDjtTw== X-UI-Out-Filterresults: notjunk:1;V01:K0:zdNAeVqQ3n8=:tUX0ED9+O3Sn+g+KIW9CGk tAzGYIA3lpkjM3zbuv9amX92+Rzr+WS0F1nlW7vw3dFfYxCVGVAdCe+MpnfnNUFbSB2GBmDSg UKSVVzNcw+RAbSG7tQRL0No63SEW7TaaCAGdaCsiWvYHav4wmahSi4CNCKVJ3p9IMD+GTGwoo LjJAN8ZG7idA3spqmJPfpck7TVA2suXUuplx0SfnuL/vbqeQeZIehD/Pzvdasxa5bv7CpdLQs FEaJ9mHjORs0uPDX8o9EJUzkrCNSN8hq+QmwwDCsmPfql8QiY36olywGGomLLtdhl/O9m9Xz9 6n+fqpcMbC6grjyYjR3aui9EAeFI3oOj+h5v32uJEK+7sGCMk8+F13nOjV2YPO0P4+h8FbG6T IITf2g7mdWLaulUdat0luOmKo6OnsOrnwuXnr6FbT33uv2L0ucXIirD5rk45Qfkzk0c1e7soq QVAKmenjzYowahjeDvGEsmApft3MlPIfyEyfRStcEqX5wtmits9Kejvfpz2bNZ6YbQbsxN2sh TKvP+d54vRxkBkGx0WaoAIMdh+twtUiRfamk69VGS1cXfhtoobdERpZED1YugYiOj0yDRMdwJ knpI9LYJxeXZoZ11WZ9I7m1HkKKfm9yaJFqkEgcEpU2Hv0bU1TOLwlHy6cAHwbKxqE9hmUwQ2 Ye2DiQ6FYqJiHeQox7LMdJoP3RcQvHDuxg61qaFgwv7Q57kdj5OhnYLi6LnRB1FlHFoC/A+PH EFnBDpyg93RtV4GTB7ki+nISvnD8PVwG72TOd7sfC7lTRb8WpySBCAuLFyPmEfXUyNx9xvQhH b4inGPn X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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: Tue, 22 Nov 2016 20:36:52 +0000 Subject: [bitcoin-dev] The Excessive-Block Gate: How a Bitcoin Unlimited Node Deals With Large Blocks X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> X-List-Received-Date: Tue, 22 Nov 2016 16:31:56 -0000 --Apple-Mail=_B235C2DA-4E0F-481A-8EF3-5139D65C4074 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Dear all, Bitcoin Unlimited=E2=80=99s market-based solution to the block-size = limit is slowly winning support from node operators and miners. With = this increased attention, many people are asking for a better = explanation of how Bitcoin Unlimited actually works. The article linked = below describes how Bitcoin Unlimited=E2=80=99s excessive-block logic = works from the perspective of a single node. (I=E2=80=99m hoping to do a = follow-up article that describe how this =E2=80=9Cnode-scale=E2=80=9D = behavior facilitates the emergence of a fluid and organic block size = limit at the network scale.) = https://medium.com/@peter_r/the-excessive-block-gate-how-a-bitcoin-unlimit= ed-node-deals-with-large-blocks-22a4a5c322d4 = <https://medium.com/@peter_r/the-excessive-block-gate-how-a-bitcoin-unlimi= ted-node-deals-with-large-blocks-22a4a5c322d4> Best regards, Peter R= --Apple-Mail=_B235C2DA-4E0F-481A-8EF3-5139D65C4074 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div class=3D"">Dear all,</div><div class=3D""><br = class=3D""></div><div class=3D"">Bitcoin Unlimited=E2=80=99s = market-based solution to the block-size limit is slowly winning support = from node operators and miners. With this increased attention, = many people are asking for a better explanation of how Bitcoin Unlimited = actually works. The article linked below describes how Bitcoin = Unlimited=E2=80=99s excessive-block logic works from the perspective of = a single node. (I=E2=80=99m hoping to do a follow-up article that = describe how this =E2=80=9Cnode-scale=E2=80=9D behavior facilitates the = emergence of a fluid and organic block size limit at the network = scale.)</div><div class=3D""><br class=3D""></div><a = href=3D"https://medium.com/@peter_r/the-excessive-block-gate-how-a-bitcoin= -unlimited-node-deals-with-large-blocks-22a4a5c322d4" = class=3D"">https://medium.com/@peter_r/the-excessive-block-gate-how-a-bitc= oin-unlimited-node-deals-with-large-blocks-22a4a5c322d4</a><div = class=3D""><br class=3D""></div><div class=3D"">Best regards,</div><div = class=3D"">Peter R</div></body></html>= --Apple-Mail=_B235C2DA-4E0F-481A-8EF3-5139D65C4074--