<oembed><type>rich</type><version>1.0</version><author_name>npub1n8ytpf4jzavm7hl9t5zksuefcguu6k3frvztqqc4kgcdkwduqesq0637cg</author_name><author_url>https://nostr.ae/npub1n8ytpf4jzavm7hl9t5zksuefcguu6k3frvztqqc4kgcdkwduqesq0637cg</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-10-14&#xA;📝 Original message:On Wed, Oct 14, 2015 at 2:12 PM, Bryan Bishop &lt;kanzure at gmail.com&gt; wrote:&#xA;&#xA;&gt; On Wed, Oct 14, 2015 at 1:02 PM, Emin Gün Sirer&#xA;&gt; &lt;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&gt; &gt; while the whitepaper has all the nitty gritty details:&#xA;&gt; &gt;      http://arxiv.org/abs/1510.02037&#xA;&gt;&#xA;&gt; Taking reward compensation back by fraud proofs is not enough to fix&#xA;&gt; the problems associated with double spending (such as, everyone has to&#xA;&gt; wait for the &#34;real&#34; confirmations instead of the &#34;possibly&#xA;&gt; double-spend&#34; confirmations). Some of this was discussed in -wizards&#xA;&gt; recently:&#xA;&gt; http://gnusha.org/bitcoin-wizards/2015-09-19.log&#xA;&#xA;&#xA;Fraud proof removes all the attacker&#39;s revenue. It&#39;s like the attacker&#xA;sacrifices an entire block for double spending in the current system. I&#xA;think Luke-Jr got it right at that discussion.&#xA;&#xA;Best,&#xA;Ittay&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151014/0630ba8f/attachment.html&gt;</html></oembed>