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 3756A481 for ; Wed, 24 May 2017 02:42:32 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qt0-f182.google.com (mail-qt0-f182.google.com [209.85.216.182]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BE947284 for ; Wed, 24 May 2017 02:42:31 +0000 (UTC) Received: by mail-qt0-f182.google.com with SMTP id v27so144423494qtg.2 for ; Tue, 23 May 2017 19:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=YZREkcGU8gACMm9oJ6mhwEkxc0tP8zj9vIyhfHHQ+gs=; b=H8dIpLVg1ybmRiZrWyDt9qg1FC663Yac7O4QB4uUEilx+iVCCRJ9Xn+6l/dRF5Dsj6 G1p8x2q5qwEs6ZrCinADJqfYVJQ8976reRbjJOTg5OfH1LtzKB3bjQpIpjHj8EvKyTNb lVMILOEIp2nFmCGSuUEddhtEpN+eGly8dHtMChP8RQFK9TncfGiPScDxjSYZkTkifQ+t oeHqEJYzHtPh84S0867rwxi8KJsnV7yxQqO6yFdlI1Qp2+jDCdZyokrbuni3oquWZOUV t7q9DUgEZWp0jnrLENPibVubtIthYOcJzfoI16laMEKdnsWIv77/h39k0E1CWeZvTeQ+ kLKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=YZREkcGU8gACMm9oJ6mhwEkxc0tP8zj9vIyhfHHQ+gs=; b=LZAk2N4s+pFJUyX67W0NV0rmsyx54srNI26R5FsUUN/Y1IVL0jd9o1Fty5pWfuozdP cIyp9bRVHMMU9fDe34Upyd5j2qvLc5jD4wO66179RvWQ02UigYujxdOftbdUTA0KfNbD 0yRRYFnTDEQgoIPsjbuGWMyW2GYaASVzpLDT8czx/AAH1CLTCywQWU5IS4qxuGqokIq4 rAuWUd3jN5iyf9hY/qIQyjTceIqYOC7xVevI6J7lBvuffpj4CjP2PJRi5CBHE265hr48 Gtgt9x+mhhoJVeLEJc2wmvGTDrRf9ra+nVfwKk9DEwHIos495quZ/FHQmgMOPqWDb6cW CeDw== X-Gm-Message-State: AODbwcB/SPnb+K+ExCR+pBurS3qenrqeKMbd97P3K95ZkikvZ93e6ERE VV/bRMYs18km+W4iYCJf1YxUK2ge6oOs X-Received: by 10.237.53.229 with SMTP id d34mr33364313qte.46.1495593750979; Tue, 23 May 2017 19:42:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.237.48.102 with HTTP; Tue, 23 May 2017 19:42:30 -0700 (PDT) Received: by 10.237.48.102 with HTTP; Tue, 23 May 2017 19:42:30 -0700 (PDT) Reply-To: erik@q32.com In-Reply-To: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com> References: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com> From: Erik Aronesty Date: Tue, 23 May 2017 22:42:30 -0400 Message-ID: To: Tomas Content-Type: multipart/alternative; boundary="001a11c00a484167c205503c0ebb" X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, RCVD_IN_SORBS_SPAM 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: Wed, 24 May 2017 02:43:15 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [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: Wed, 24 May 2017 02:42:32 -0000 --001a11c00a484167c205503c0ebb Content-Type: text/plain; charset="UTF-8" Instead of block thresholds, use utxo bits to coordinate size changes (larger and smaller should be allowed). There is no reason for miners to be involved in a decision to change this aspects of the protocol. Plenty of other ways to coordinate. Otherwise someone can make it seem to a miner like 99pct of nodes are ready for a larger weight.... even though that's false. On May 23, 2017 8:03 AM, "Tomas via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --001a11c00a484167c205503c0ebb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Instead of block thresholds, use utxo bits to coordinate = size changes (larger and smaller should be allowed).

<= /div>
There is no reason for miners to be involved in a de= cision to change this aspects of the protocol. =C2=A0 Plenty of other ways = to coordinate.

Otherwise s= omeone can make it seem to a miner like 99pct of nodes are ready for a larg= er weight.... even though that's false.

On May 23, 2017 8:03 AM, "= Tomas via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org> wrote:
I have a proposal that woul= d 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/bi= p-changing-the-maximum-block%20weight-based-on-a-support-threshol= d.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
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
--001a11c00a484167c205503c0ebb--