mikedilger on Nostr: An unlimited number of Open Timestamps can be put onto the blockchain with just 32 ...

An unlimited number of Open Timestamps can be put onto the blockchain with just 32 bytes (plus some overhead) thanks to the magic of Merkle trees. You then have to keep the path from your hash up to the root, and all siblings long that path, as proof that your hash was created prior to the block being mined. There is a service that collects all these timestamps, builds the Merkle tree and pays to put the final result onto the blockchain. This should be supported somehow (though I'm not sure the actual expenses are) as it is becoming (or will soon become) critical infrastructure.

quoting nevent1q…g2t0

I have just started running ots_nbot (nprofile…auwv) and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to Mazin (npub18kz…x5sz)'s cellar.nostr.wine which is not going to delete them -- and to some other relays.

Somehow this will protect the humanity against the AI takeover in the future, so I recommend other people to do the same with other events. The source code is at https://git.fiatjaf.com/ots_nbot and you can customize the relays, kinds and authors it tries to timestamp, among other things, via environment variables.

If you don't understand how such a simple gesture has such immense powers, listen to Antihashed Podcast episode where this is explained, or ask constant (npub1t6j…ksrw).

fiatjaf (npub180c…h6w6) pkt (npub1ej4…ndrm)