j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÏ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=721.msg8114#msg8114">Quote from: satoshi on August 07, 2010, 05:46:09 PM</a></div><div class="quote">It's the same situation as gold and gold mining. The marginal cost of gold mining tends to stay near the price of gold. Gold mining is a waste, but that waste is far less than the utility of having gold available as a medium of exchange. I think the case will be the same for Bitcoin. The utility of the exchanges made possible by Bitcoin will far exceed the cost of electricity used. Therefore, <i>not</i> having Bitcoin would be the net waste.<br/>[...] <br/>Proof-of-work has the nice property that it can be relayed through untrusted middlemen. We don't have to worry about a chain of custody of communication. It doesn't matter who tells you a longest chain, the proof-of-work speaks for itself.<br/></div><br/>Thanks very much for your reply. I agree with your analysis, and this thread has actually changed my mind as to my initial criticism. After more careful study of the design of the Bitcoin network and trying to understand the exact manner in which Bitcoin attempts to create value from the computational work invested, I am now inclined to think that bitcoin is in fact high EFFICIENT rather than inefficient. My thinking now is that bitcoin does not, in fact "waste" computational work at all - instead it works hard to deliver the most value possible from that computational work. Something like a governnment issued fiat currency may not have any obvious energy burden beyond its printing - but in fact, maintaining the value of a fiat currency requires a substantial investment in maintaining police enforcement, a legal system, and national defense. In comparison to the energy cost of hiring police officers to enforce economic honesty, the energy costs of investing cpu cycles in guaranteeing that honesty mathematically seem very small!<br/></div> text/html
https://whatsonchain.com/tx/2c8564d85851e43dd18faaef22f003a8e278707a541191a97ae2bea97fca8d88