The article recommends to split your SHA256 hash into two pieces. However, one transaction to one address is sufficient. You just have to create the address in

The article recommends to split your SHA256 hash into two pieces. However, one transaction to one address is sufficient. You just have to create the address in the same way in which Bicoin generates an address for a public key: Base58(RIPEMD160(SHA256(public key))) So there's nothing wrong with doing it the same way for your data: Base58(RIPEMD160(SHA256(data))) (That's what I'm also using in Bitcoinproof http://vog.github.io/bitcoinproof/ http://vog.github.io/bitcoinproof/) Using this hash is not any "less secure" than the plain SHA256 hash, because the RIPEMD160+SHA256 combination is used by the Bitcoin network itself. So if this one is broken, the Bitcoin network itself is broken, and your timestamps would be no longer trustable anyway.