public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed
@ 2015-07-08 19:15 Mashuri Clark
  0 siblings, 0 replies; only message in thread
From: Mashuri Clark @ 2015-07-08 19:15 UTC (permalink / raw)
  To: pieter.wuille, bitcoin-dev

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-07-08 19:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-08 19:15 [bitcoin-dev] [Bitcoin-development] Mining centralization pressure from non-uniform propagation speed Mashuri Clark

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox