<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed Double Spending Prevention · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/0802.0832/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/0802.0832/feed.xml" rel="self" type="application/rss+xml" /><item><title>Distributed Double Spending Prevention — mentioned by EGreg</title><link>https://news.ycombinator.com/item?id=41260780</link><guid isPermaLink="false">urn:hackerpapers:mention:0802.0832:41260780</guid><pubDate>Thu, 15 Aug 2024 21:52:26 GMT</pubDate><description>&lt;p&gt;Sorry, but you&amp;#x27;re not exactly an expert on this. There is a huge body of literature that says otherwise, and reference implementations. You don&amp;#x27;t NEED &amp;quot;a centralizing consensus&amp;quot;. IOTA did have one, called a &amp;quot;governor&amp;quot;. And now they also did away with it. I had a discussion with the CTO of Ripple (back then their chief cryptographer) David Schwartz about this exact issue in 2018, when I was also connecting with Leslie Lamport and others in the industry to discuss why and how global consensus was even needed https://community.intercoin.app/t/intercoin-technology-conse... You can also read this…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0802.0832/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Distributed Double Spending Prevention — mentioned by EGreg</title><link>https://news.ycombinator.com/item?id=35628070</link><guid isPermaLink="false">urn:hackerpapers:mention:0802.0832:35628070</guid><pubDate>Wed, 19 Apr 2023 13:46:33 GMT</pubDate><description>&lt;p&gt;(I fed it this PDF: https://arxiv.org/pdf/0802.0832v1.pdf) And got the same experience I often have with LLMs: How many validators are enough to make the scheme secure According to page 5 of the PDF, the system is secure with security parameters if the adversary must perform an expected O(2^s) amount of work in order to be successful. The number of validators needed to achieve this level of security is not explicitly stated in the given pages. Are you sure? Yes, I am sure. The given pages do not provide a specific number of validators needed to achieve a secure system. However, the authors do…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0802.0832/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Distributed Double Spending Prevention — mentioned by alex_sf</title><link>https://news.ycombinator.com/item?id=35469397</link><guid isPermaLink="false">urn:hackerpapers:mention:0802.0832:35469397</guid><pubDate>Thu, 06 Apr 2023 15:11:29 GMT</pubDate><description>&lt;p&gt;&amp;gt; - Bitcoin doesn&amp;#x27;t use DHTs. I didn&amp;#x27;t say it did. But the idea of distributing data in a P2P fashion is not novel. &amp;gt; - The term blockchain was coined after the Bitcoin white paper was published, to describe the mechanism used in Bitcoin. I&amp;#x27;m not very interested in the particular etymology. The fundamental ideas of a blockchain, regardless of what you call it, had been laid out by multiple people years before the bitcoin whitepaper[0]. &amp;gt; - Bitcoin was the first system to solve the double spending problem in a decentralized way. No, it wasn&amp;#x27;t[1][2]. &amp;gt; The network is actively used. Just…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0802.0832/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Distributed Double Spending Prevention — mentioned by alex_sf</title><link>https://news.ycombinator.com/item?id=35464244</link><guid isPermaLink="false">urn:hackerpapers:mention:0802.0832:35464244</guid><pubDate>Thu, 06 Apr 2023 04:49:02 GMT</pubDate><description>&lt;p&gt;Sure. Whitepaper was released in 2008. Genesis block was in 2009. In 2007 we had Combating Double-Spending Using Cooperative P2P Systems[0]. Prior to both the whitepaper and the genesis block, we had Distributed Double Spending Prevention[1]. These are all particular subsets of distributed consensus problems, which have been studied in the context of CS for at least 30+ years (Consensus in the Presence of Partial Synchrony[2]). [0] https://ieeexplore.ieee.org/document/4268195 [1] https://arxiv.org/abs/0802.0832 [2] http://groups.csail.mit.edu/tds/papers/Lynch/jacm88.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0802.0832/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Distributed Double Spending Prevention — mentioned by EGreg</title><link>https://news.ycombinator.com/item?id=25808640</link><guid isPermaLink="false">urn:hackerpapers:mention:0802.0832:25808640</guid><pubDate>Sun, 17 Jan 2021 06:25:05 GMT</pubDate><description>&lt;p&gt;Yes, it is a good step forward. Really, what you need is a distributed hash table (like MaidSAFE), or randomness beacons (like Algorand) to select a subset of the network. This paper shows mathematically that the probability of a double-spend goes down exponentially with the number of notaries, and having the entire network secure every transaction, no matter the size, is wayyyy overkill: https://arxiv.org/pdf/0802.0832v1.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0802.0832/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
