I have just started running nostr:nprofile1qqsp2k6lqqqw5uyaeaaeayjd22yu9rymg9ntqsu66kplcc9uu75khtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzfmhxue69uhk7enxvd5xz6tw9ec82cspz3mhxue69uhhyetvv9ujumn0wd68ytnzvuawauwv and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz'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 nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw.


Remember that none of this would be possible without nostr:npub1ej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqm3ndrm's amazing work at OpenTimestamps, so remember to always be grateful to him.


how does it scales? Like how many notes/vbyte we can timestamp?


100% 🙏


Even reactions and ephemeral events? That sounds ... costly...


No, I'm not doing these, but still all that goes on Bitcoin is a 32 byte merkle root every couple of hours or more.

Also nostr:npub1ej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqm3ndrm is paying, so we don't have to worry.


Scales very well, basically infinite.


future of elections?


Remember which podcast episode number?


They already kinda did that in Guatemala. https://theusecasesofbitcoin.com/use-cases/841-ensuring-election-integrity-with-bitcoin-the-guatemala-case


To be pedantic, I'm not personally paying for OpenTimestamps transaction fees. There's a community fundraiser for that: https://geyser.fund/project/opentimestamps 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...


yes, familiar w/Guat. i was thinking imput 4 wider adoption.  t-y


Can we get a tldr on benefits?


This is how we beat the T-9000.
nostr:nevent1qqsqqqyzft33yl5s3a30m5mdksfwyzmkw4jfgeg8gk25tf69sm42lpgpz9mhxue69uhkummnw3ezuamfdejj7q3q80cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsxpqqqqqqz8s4mxf


Onward 🫡


how often do the calendars publish on chain? Is there a way to track those transactions on a website like mempool.space?


There's a list of the four calendars on https://opentimestamps.org/; each calendar has a website showing you stats.

The most frequent transactions at the moment are done by https://alice.btc.calendar.opentimestamps.org/, on average once every 5 hours at a cost of 20,000sats/week.


I hope the AI doesn't take revenge by making thousands of copies of your brain and torturing them for eternity!


yes.
much good


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.


No, I don't remember, you have to listen to all of them.


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?


I see what you did there


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.


1527 timestamps published, 47 pending.


I have just started running nostr:nprofile1qqsp2k6lqqqw5uyaeaaeayjd22yu9rymg9ntqsu66kplcc9uu75khtgpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzfmhxue69uhk7enxvd5xz6tw9ec82cspz3mhxue69uhhyetvv9ujumn0wd68ytnzvuawauwv and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz'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 nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw.