Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMn<div class="post">New transaction templates can be added as needed. &nbsp;Within a few days, there will be plenty of GPU power that accepts and works on it. &nbsp;Network support will be thorough <i>long before</i> there'll be enough clients who understand how to receive and interpret the new transaction.<br/><br/>Timestamp hashes are still already possible:<br/><br/>txin: 0.01<br/>txout: 0.00 &nbsp;&lt;appid, hash&gt; OP_CHECKSIG<br/>fee: 0.01 <br/><br/>If there's an actual application like BitDNS getting ready to actually start inserting hashes, we can always add a specific transaction template for timestamps.<br/><br/>I like Hal Finney's idea for user-friendly timestamping. &nbsp;Convert the hash of a file to a bitcoin address and send 0.01 to it:<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=2077.msg27173#msg27173">Quote from: Hal on December 05, 2010, 11:43:56 PM</a></div><div class="quote">I thought of a simple way to implement the timestamp concept I mentioned above. Run sha1sum on the file you want to timestamp. Convert the result to a Bitcoin address, such as via <a href="http://blockexplorer.com/q/hashtoaddress">http://blockexplorer.com/q/hashtoaddress</a> . Then send a small payment to that address.<br/><br/>The money will be lost forever, as there is no way to spend it further, but the timestamp Bitcoin address will remain in the block chain as a record of the file's existence.<br/><br/>I understand that this is arguably not a good use of the Bitcoin distributed database, but nothing stops people from doing this so we should be aware that it may be done.<br/></div></div> text/html