From: Erik Aronesty <earonesty@gmail•com>
To: Tomas <tomas@tomasvdw•nl>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal to allow users to configure the maximum block weight based on a support threshold
Date: Tue, 23 May 2017 22:42:30 -0400 [thread overview]
Message-ID: <CAJowKgJs-cVR7w1QvSKr+ZXeQd4giq-aGLOEktqHn3a83tNGBA@mail.gmail.com> (raw)
In-Reply-To: <1495536637.1801543.985680712.6B788409@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2297 bytes --]
next prev parent reply other threads:[~2017-05-24 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 10:50 Tomas
2017-05-24 2:42 ` Erik Aronesty [this message]
2017-05-24 8:34 ` Tomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJowKgJs-cVR7w1QvSKr+ZXeQd4giq-aGLOEktqHn3a83tNGBA@mail.gmail.com \
--to=earonesty@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
--cc=tomas@tomasvdw$(echo .)nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox