<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>I have heard such theory before, it's a complete mistake to think
that others would run full nodes to protect their business and
then yours, unless it is proven that they are decentralized and
independent</p>
<p>Running a full node is trivial and not expensive for people who
know how to do it, even with much bigger blocks, assuming that the
full nodes are still decentralized and that they don't have to
fight against big nodes who would attract the traffic first<br>
</p>
<p>I have posted many times here a small proposal, that exactly
describes what is going on now, yes miners are nodes too... it's
disturbing to see that despite of Tera bytes of BIPs, papers, etc
the current situation is happening and that all the supposed
decentralized system is biased by centralization</p>
<p>Do we know what majority controls the 6000 full nodes?</p>
<br>
<div class="moz-cite-prefix">Le 29/03/2017 à 22:32, Jared Lee
Richardson via bitcoin-dev a écrit :<br>
</div>
<blockquote
cite="mid:CAD1TkXtze_TVegXz4AeJCxK59+cuwRQ=w4upzX+HoQ90Py52OA@mail.gmail.com"
type="cite">
<div dir="ltr">> <span style="font-size:12.8px">Perhaps you are
fortunate to have a home computer that has more than a single
512GB SSD. Lots of consumer hardware has that little storage.</span><br>
<br>
<span style="font-size:12.8px">That's very poor logic, sorry.
Restricted-space SSD's are not a cost-effective hardware
option for running a node. Keeping blocksizes small has
significant other costs for everyone. Comparing the cost of
running a node under arbitrary conditons A, B, or C when there
are far more efficient options than any of those is a very bad
way to think about the costs of running a node. You basically
have to ignore the significant consequences of keeping blocks
small.<br>
<br>
If node operational costs rose to the point where an entire
wide swath of users that we do actually need for security
purposes could not justify running a node, that's something
important for consideration. For me, that translates to
modern hardware that's relatively well aligned with the needs
of running a node - perhaps budget hardware, but still modern
- and above-average bandwidth caps.</span>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">You're free to disagree, but
your example only makes sense to me if blocksize caps didn't
have serious consequences. Even if those consequences are
just the threat of a contentious fork by people who are
mislead about the real consequences, that threat is still a
consequence itself.</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Mar 29, 2017 at 9:18 AM, David
Vorick via bitcoin-dev <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bitcoin-dev@lists.linuxfoundation.org"
target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>
<div class="gmail_extra">Perhaps you are fortunate to
have a home computer that has more than a single 512GB
SSD. Lots of consumer hardware has that little
storage. Throw on top of it standard consumer usage,
and you're often left with less than 200 GB of free
space. Bitcoin consumes more than half of that, which
feels very expensive, especially if it motivates you
to buy another drive.</div>
</div>
<div class="gmail_extra" dir="auto"><br>
</div>
<div class="gmail_extra" dir="auto">I have talked to
several people who cite this as the primary reason that
they are reluctant to join the full node club.</div>
</div>
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
<a moz-do-not-send="true"
href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"
rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
</body>
</html>