pull down to refresh

62 sats \ 11 replies \ @k00b OP 22 Jan 2023 \ parent \ on: SN release: OpenTimestamps timestamps meta

When you delete, you delete the pre image. The hash is still timestamped, viewable, and verifiable.

Eg if I say something regarded, you can store the pre image yourself if you’d like, and prove to people it was said when it was said regardless of its deletion status.

write
preview
0 sats \ 3 replies \ @TonyGiorgio 22 Jan 2023

How do you see the item number of a comment?

reply
21 sats \ 1 reply \ @k00b OP 22 Jan 2023

Click on the time, e.g. 35m, or the 1 replies.

reply
0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 3 replies \ @petertodd 23 Jan 2023

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.

reply
0 sats \ 1 reply \ @petertodd 23 Jan 2023

Correction: from the hash digest of course. Not the preimage. That doesn't need bruteforcing!

reply
0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 1 reply \ @ama 23 Jan 2023

Outstanding!

reply
0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author

0 sats \ 0 replies \ @247bf84fda 25 Aug freebie

deleted by author