From: Mashuri Clark <mashuribc@gmail•com>
To: <pieter.wuille@gmail•com>, <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed
Date: Wed, 8 Jul 2015 12:15:08 -0700 [thread overview]
Message-ID: <007801d0b9b2$6815f0d0$3841d270$@GMail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Would it be easy to code in another variable? I think it would be useful to
know how a per-node imposed max block size limit (with this limit, a node
would still accept all incoming blocks, but refuse to relay any above a
specified size) would affect orphan rates and reorgs. Example: What would
the orphan rate be of an 8MB block if 80% of all nodes refuse to relay it?
The resulting data would provide insight into how nodes can enforce a
dynamic maximum block size in absence of a hard limit.
I would do this myself but I am not a coder. I'm hoping someone here who is
capable finds this data worth pursuing.
--
MC
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
[-- Attachment #2: Type: text/html, Size: 3133 bytes --]
reply other threads:[~2015-07-08 19:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007801d0b9b2$6815f0d0$3841d270$@GMail.com' \
--to=mashuribc@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pieter.wuille@gmail$(echo .)com \
/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