SN-3801 已核对来源，附原文与上下文。
新的交易模板能按需添加。几天之内就会有大量 GPU 算力接受并处理它。网络支持会远远早于「出现足够多懂得接收和解释新交易的客户端」而就绪。
New transaction templates can be added as needed. Within a few days, there will be plenty of GPU power that accepts and works on it. Network support will be thorough long before there'll be enough clients who understand how to receive and interpret the new transaction.
时间戳哈希现在已经可行：
Timestamp hashes are still already possible:
txin: 0.01
txin: 0.01
txout: 0.00
txout: 0.00
fee: 0.01
fee: 0.01
如果真有像 BitDNS 这样的应用准备开始插入哈希，我们随时能为时间戳加一个专门的交易模板。
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.
我喜欢 Hal Finney 那个用户友好的时间戳构想。把文件的哈希转换成一个比特币地址，从而向它发送 0.01：
I like Hal Finney's idea for user-friendly timestamping. Convert the hash of a file to a bitcoin address and send 0.01 to it:
其他参与者原话Hal原帖 ↗我想到了一个简单办法来实现上面说的时间戳概念。对想加时间戳的文件跑 sha1sum。把结果转换成一个比特币地址，比如通过 http://blockexplorer.com/q/hashtoaddress。从而向那个地址发一笔小额支付。
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 http://blockexplorer.com/q/hashtoaddress . Then send a small payment to that address.
这笔钱将永远丢失，因没有办法再花出去，但这个时间戳比特币地址会留在区块链里，作为该文件存在过的记录。
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.
我明白这算不算对比特币分布式数据库的正当用法尚有争议，但没有什么能阻止人们这么做，因此我们应该意识到这可能会发生。
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.
