From: Tom Zander <tomz@freedommail•ch>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] The Excessive-Block Gate: How a Bitcoin Unlimited Node Deals With Large Blocks
Date: Sat, 26 Nov 2016 16:01:16 +0100 [thread overview]
Message-ID: <2318925.r6f9XVyAit@cherry> (raw)
In-Reply-To: <CAKzdR-oE44Qcb1sfz3RmcVmtR9qzB+9J5ufTgGmdQ_Xctenh7A@mail.gmail.com>
On Friday, 25 November 2016 20:45:20 CET Sergio Demian Lerner wrote:
> I now think my reasoning and conclusions are based on a false premise:
> that BU block size policies for miners can be heterogeneous.
Agreed.
> There can't be short forks because forks are not in the best interest of
> the honest miner majority. All miners need to announce and follow the same
> block size policy to prevent short forks.
What you appear to want to say is that it is in everyones best interest to
avoid short forks.
Its impossible to guarentee they can't happen, but very possible to minimize
them.
> If block size negotiations are meant to be open and carried on on-chain,
> then it's much better to let miners increase or decrease the block size
> limit by 1% per block (such as what Ethereum does with the gas limit).
No, there are no block-size-negotiations on chain.
The blockchain is used here for one purpose, to state the position of
individual miners. But what may not be clear is that you can use this as a
time-stamped way to hold them to it. Which means that if they lie (by
rejecting a block), everyone in the world will be able to individually
verify that fact and their credibility will be affected.
Which will not help their case next time any block size negotiations will
happen.
--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel
next prev parent reply other threads:[~2016-11-26 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 16:31 Peter R
2016-11-25 1:39 ` Sergio Demian Lerner
2016-11-25 15:25 ` Tom Zander
2016-11-25 22:31 ` Sergio Demian Lerner
2016-11-25 23:45 ` Sergio Demian Lerner
2016-11-26 15:01 ` Tom Zander [this message]
2016-11-26 23:35 ` Peter R
2016-11-27 7:47 ` Tom Zander
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=2318925.r6f9XVyAit@cherry \
--to=tomz@freedommail$(echo .)ch \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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