pull down to refresh
0 sats \ 1 reply \ @petertodd 23 Jan 2023 \ parent \ on: SN release: OpenTimestamps timestamps meta
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.
Correction: from the hash digest of course. Not the preimage. That doesn't need bruteforcing!
reply