<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">Den 1 apr. 2017 01:13 skrev "Eric Voskuil via bitcoin-dev" <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>>:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<div class="quoted-text"><br>
On 03/31/2017 02:23 PM, Rodney Morris via bitcoin-dev wrote:<br>
> If the obsession with every personal computer being able to run a<br>
> fill node continues then bitcoin will be consigned to the dustbin<br>
> of history,<br>
<br>
</div>The cause of the block size debate is the failure to understand the<br>
Bitcoin security model. This failure is perfectly exemplified by the<br>
above statement. If a typical personal computer cannot run a node<br>
there is no security. </blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">If you're capable of running and trusting your own node chances are you already have something better than a typical personal computer! </div><div dir="auto"><br></div><div dir="auto">And those who don't have it themselves likely know where they can run or access a node they can trust. </div><div dir="auto"><br></div><div dir="auto">If you're expecting average joe to trust the likely not updated node on his old unpatched computer full of viruses, you're going to have a bad time. </div><div dir="auto"><br></div><div dir="auto">The real solution is to find ways to reduce the required trust in a practical manner. </div><div dir="auto"><br></div><div dir="auto">Using lightweight clients with multiple servers have already been mentioned, Zero-knowledge proofs (if the can be made practical and stay secure...) is another obvious future tool, and hardware wallets helps against malware. </div><div dir="auto"><br></div><div dir="auto">If you truly want everybody to run their own full nodes, the only plausible solution is managed hardware in the style of Chromebooks, except that you could pick your own distribution and software repository. Meaning you're still trusting the exact same people whose nodes you would otherwise rely on, except now you're mirroring their nodes on your own hardware instead. Which at most improves auditability. </div><div dir="auto"><br></div><div dir="auto"></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div></div></div></div>