From: Peter R <peter_r@gmx•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] The Excessive-Block Gate: How a Bitcoin Unlimited Node Deals With Large Blocks
Date: Tue, 22 Nov 2016 08:31:50 -0800 [thread overview]
Message-ID: <C10BF9D1-435D-47C9-B98C-9B118B5922A1@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Dear all,
Bitcoin Unlimited’s 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’s excessive-block logic works from the perspective of a single node. (I’m hoping to do a follow-up article that describe how this “node-scale” 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-unlimited-node-deals-with-large-blocks-22a4a5c322d4 <https://medium.com/@peter_r/the-excessive-block-gate-how-a-bitcoin-unlimited-node-deals-with-large-blocks-22a4a5c322d4>
Best regards,
Peter R
[-- Attachment #2: Type: text/html, Size: 1241 bytes --]
next reply other threads:[~2016-11-22 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 16:31 Peter R [this message]
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
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=C10BF9D1-435D-47C9-B98C-9B118B5922A1@gmx.com \
--to=peter_r@gmx$(echo .)com \
--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