I have just started running @npub1z4d4...j7rz and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to @npub18kzz...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.

Replies (25)

To be pedantic, I'm not personally paying for OpenTimestamps transaction fees. There's a community fundraiser for that: and the calendars themselves accept funds directly to their wallets. Last time I pushed for donations was in January, and I got enough donations to last until now (most donations, by value, were not sent through geyser). I'll probably run out of donated funds again in another 2-4 months. FWIW I share the funds donated to my calendars (and through geyser) with the other calendars.
In theory... In practice the calendars themselves aren't horizontally scalable, so with enough load they'll fail. We're not at that point yet. But a DoS attack would do it. This can be fixed with improved code. But I haven't been able to find any funding to spend the time to actually fix this. I gotta pay rent after all...
Default avatar
Rand 1 year ago
yes, familiar w/Guat. i was thinking imput 4 wider adoption. t-y
This is how we beat the T-9000.
fiatjaf's avatar fiatjaf
I have just started running @npub1z4d4...j7rz and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to @npub18kzz...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.
View quoted note →
how often do the calendars publish on chain? Is there a way to track those transactions on a website like mempool.space?
interesting
fiatjaf's avatar fiatjaf
I have just started running @npub1z4d4...j7rz and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to @npub18kzz...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.
View quoted note →
14 hours later, 229 timestamps published, 76 pending, now alternating between the 4 public calendar servers to alleviate the (enormous) load. One thing I don't get is how I can send 2 ids for timestamping at the same time and one goes in the next batch, the other only on the following batch many hours later.
Thanks. Open timestamps is a fascinating project. I noticed that the transactions are using Segwit. Would there be any significant savings by switching to Taproot?
TLDR: If you demand timestamps, it forces a lie to be made up in advance and cant be made after the fact. This gives truth a defensive advantage. If you dont understand what that means, dont ask for tldr's in the future.