Peter Todd

Thanks for the heads up! I didn't notice all the new stuff you've done. If I don't get back to you in a week or so with a response, bother...

In addition to my comment, let's go ahead and rename `ots-git-gpg-wrapper.sh` to `opentimestamps-git-gpg-wrapper` to both avoid any command completion issues, and because it being a shell script is an implementation...

Maybe we need two timeouts? A shorter "wait for every calendar" timeout and a longer "wait for minimum # of calendars" timeout? Not sure how we should communicate this to...

@makew0rld The tricky thing is the timeout I'm talking about is basically a two step: 1) wait a little bit to try to get timestamps from *every* calendar, 2) wait...

On August 3, 2023 5:01:23 PM GMT+02:00, makeworld ***@***.***> wrote: >My point is that it makes sense to time each calendar request individually, to prevent individual slow servers from slowing...

Also along these lines, it could be good to change the coinjoin transactions to opt-in to RBF via BIP-125. That'll make sure you've got all the necessary infrastructure to deal...

I made a pull-req, feedback appreciated! https://github.com/opentimestamps/opentimestamps-client/pull/133

Closing this as "won't fix", as backing up the calendars themselves is feasible and better for everyone.

AFAIK no-one uses the litecoin functionality, so closing.

Yeah, I think before this is actually merged it should be easier to use. But first, I want to figure out how to make this more secure. It should have...