pull down to refresh
Correction: from the hash digest of course. Not the preimage. That doesn't need bruteforcing!
reply
deleted by author
deleted by author
pull down to refresh
Correction: from the hash digest of course. Not the preimage. That doesn't need bruteforcing!
deleted by author
deleted by author
Note from the preimage in some cases someone could brute-force the deleted message. You could fix this by creating a 128-bit nonce for every item and including that nonce in the hashed data - OpenTimestamps itself does to prevent the OTS calendars from learning anything about what is being timestamped.