From: Mashuri Clark <mashuribc@gmail.com>
To: <pieter.wuille@gmail.com>,
	<bitcoin-dev@lists.linuxfoundation.org>
Date: Wed, 8 Jul 2015 12:15:08 -0700
Message-ID: <007801d0b9b2$6815f0d0$3841d270$@GMail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0079_01D0B977.BBB78E00"
Thread-Index: AdC5skuxXXIgUveNSvCCZEPFOWoEiA==
Content-Language: en-us
Subject: [bitcoin-dev] [Bitcoin-development] Mining centralization pressure
	from non-uniform propagation speed
Precedence: list

This is a multipart message in MIME format.

------=_NextPart_000_0079_01D0B977.BBB78E00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0079_01D0B977.BBB78E00
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
=2EMsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3D"#0563C1=
" vlink=3D"#954F72"><div class=3DWordSection1><p class=3DMsoNormal>Would it=
 be easy to code in another variable?&nbsp; I think it would be useful to k=
now how a per-node imposed max block size limit (with this limit, a node wo=
uld still accept all incoming blocks, but refuse to relay any above a speci=
fied size) would affect orphan rates and reorgs.&nbsp; Example: What would =
the orphan rate be of an 8MB block if 80% of all nodes refuse to relay it?&=
nbsp; The resulting data would provide insight into how nodes can enforce a=
 dynamic maximum block size in absence of a hard limit.<o:p></o:p></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I would do this m=
yself but I am not a coder.&nbsp; I&#8217;m hoping someone here who is capa=
ble finds this data worth pursuing.<o:p></o:p></p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>--<o:p></o:p></p><p class=3DMsoNormal=
>MC<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div>
<br /><br />
<hr style=3D'border:none; color:#909090; background-color:#B0B0B0; height: =
1px; width: 99%;' />
<table style=3D'border-collapse:collapse;border:none;'>
	<tr>
		<td style=3D'border:none;padding:0px 15px 0px 8px'>
			<a href=3D"https://www.avast.com/antivirus">
				<img border=3D0 src=3D"http://static.avast.com/emails/avast-mail-stamp.=
png" alt=3D"Avast logo" />
			</a>
		</td>
		<td>
			<p style=3D'color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helv=
etica"; font-size:12pt;'>
				This email has been checked for viruses by Avast antivirus software.
				<br><a href=3D"https://www.avast.com/antivirus">www.avast.com</a>
			</p>
		</td>
	</tr>
</table>
<br />
</body></html>
------=_NextPart_000_0079_01D0B977.BBB78E00--