j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÙ<div class="post">Forgot to add the good part about micropayments. While I don't think Bitcoin is practical for smaller micropayments right now, it will eventually be as storage and bandwidth costs continue to fall. If Bitcoin catches on on a big scale, it may already be the case by that time. Another way they can become more practical is if I implement client-only mode and the number of network nodes consolidates into a smaller number of professional server farms. Whatever size micropayments you need will eventually be practical. I think in 5 or 10 years, the bandwidth and storage will seem trivial.<br/><br/>I am not claiming that the network is impervious to DoS attack. I think most P2P networks can be DoS attacked in numerous ways. (On a side note, I read that the record companies would like to DoS all the file sharing networks, but they don't want to break the anti-hacking/anti-abuse laws.)<br/><br/>If we started getting DoS attacked with loads of wasted transactions back and forth, you would need to start paying a 0.01 minimum transaction fee. 0.1.5 actually had an option to set that, but I took it out to reduce confusion. Free transactions are nice and we can keep it that way if people don't abuse them.<br/><br/>That brings up the question: if there was a minimum 0.01 fee for each transaction, should we automatically add the fee if it's just the minimum 0.01? It would be awfully annoying to ask each time. If you have 50.00 and send 10.00, the recipient would get 10.00 and you'd have 39.99 left. I think it should just add it automatically. It's trivial compared to the fees many other types of services add automatically.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=287.msg7569#msg7569">Quote from: FreeMoney on August 04, 2010, 07:30:32 PM</a></div><div class="quote">Does including more slow down your hashing rate? <br/></div>No, not at all.<br/></div> text/html
https://whatsonchain.com/tx/8243f994be5fb7cbccee46ba1f04dbbabb68100bd7c82f2faa63f8b2bd946006