<div dir="auto"><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">Den 28 jan. 2017 05:04 skrev "Luke Dashjr via bitcoin-dev" <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>>:<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Satoshi envisioned a system where full nodes could publish proofs of invalid<br>
blocks that would be automatically verified by SPV nodes and used to ensure<br>
even they maintained the equivalent of full node security so long as they were<br>
not isolated. But as a matter of fact, this vision has proven impossible, and<br>
there is to date no viable theory on how it might be fixed. As a result, the<br>
only way for nodes to have full-node-security is to actually be a true full<br>
node, and therefore the plan of only having full nodes in datacenters is<br>
simply not realistic without transforming Bitcoin into a centralised system.<br>
<div class="quoted-text"></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Beside Zero-knowledge proofs, which is capable of proving much so more than just validity, there are multi types of fraud proofs that only rely on the format of the blocks. Such as publishing the block header + the two colliding transactions included in it (in the case of double spending), or if the syntax or logic is broken then you just publish that single transaction. </div><div dir="auto"><br></div><div dir="auto">There aren't all that many cases where fraud proofs are unreasonably large for a networked system like in Bitcoin. If Zero-knowledge proofs can be applied securely, then I can't think of any exceptions at all for when the proofs would be unmanageable. (Remember that full Zero-knowledge proofs can be chained together!) </div><div class="gmail_extra" dir="auto"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text"></div></blockquote></div><br></div></div>