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 190F1904 for ; Tue, 23 May 2017 10:50:39 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3B25A13D for ; Tue, 23 May 2017 10:50:38 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 758B12077C for ; Tue, 23 May 2017 06:50:37 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute2.internal (MEProxy); Tue, 23 May 2017 06:50:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=0p9vaDFhhx44zNwXxGCZCm3L21qSA Mz0A4I9wf1cMf4=; b=cCPIx3cZVZoQh7ikq+m6fk5bWXK7iewtpg41KlvXUvqHj 7yf0jp3OXRSK9CyTMEG1SXpdmg32p9ilYdTKnVxRufJLEm56lDqawE/yvKrLelb3 QYmZuSJSBdbixOVaL4BH3qhMSW6NUJbzP4qxsKD6+tNXK9j44cRCq1cLFITxUFHI uHJW68y4RYTQ4F9SLEVywpdq5yLK2e3++FOzcggVaZJY5BF8cUq+fU6vrSBfWp74 H+tfonIub5mEF4ppwLBwjdYfDXULt4OLixQ30O5OFd3mBtDlYBbT9s+M9lB/DDyz eu+OpBWpj51qR9o06wGjLlg3mD0Ql3ZvamQ00698A== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 55522BAB67; Tue, 23 May 2017 06:50:37 -0400 (EDT) Message-Id: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com> From: Tomas To: Bitcoin Dev MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-a5162694 Date: Tue, 23 May 2017 12:50:37 +0200 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,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, 23 May 2017 12:02:46 +0000 Subject: [bitcoin-dev] Proposal to allow users to configure the maximum block weight based on a support threshold X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 10:50:39 -0000 I have a proposal that would allow each user to optionally configure the maximum block weight at a support threshold. It recognizes that there is no need for off chain bickering, by providing a mechanism that lets each users freely choose their own parameters while still maintaining full coordination of any changes. The BIP can be found here: https://github.com/tomasvdw/bips/blob/master/bip-changing-the-maximum-block%20weight-based-on-a-support-threshold.mediawiki It is worth noting that this proposal does neither gives more power to miners nor reduces decentralization. Miners still rely on their blocks being accepted by economic nodes to sell their minted coins. This proposal doesn't change that. Regards, Tomas van der Wansem bitcrust