[spam][crazy][wrong] considering timestamps

Undiscussed Horrific Abuse, One Victim of Many gmkarl at gmail.com
Sat Feb 19 08:47:18 PST 2022


okay, i have no idea what's going on :)

i haven't reread this thread. i dunno where i left off.

but _presently_ i have a problem where i have too much corrupted data,
and i keep corrupting it, and it has reached too large a point.
handling it is a priority for me.

i'd like to store hashes of it somewhere that doesn't let me corrupt
it. i want those hashes to be like a stone mountain, where i keep
punching it and punching it and take out my hacksaw and desperately
try to mess it up, and it just stays there.

it turns out that opentimestamps and origintimestamps are _separate_
efforts that to me appear obfuscating and disconnecting of users from
blockchains. dunno. but i already made an opentimestamps client!
woohoo! i also made similar work in libtoilet.

i'm not running a bitcoin peer to hash anything on its chain. and i
can see that people's confidence in bitcoin's price is being whittled
away with a little more precision than before.
i'll try the old opentimestamps client hack out. it was at
https://github.com/xloem/opentimestamps-client .


More information about the cypherpunks mailing list