Yeah, that’s my thinking. The public calendar servers work great, but from a resilience perspective, I want to know that I *can*, so whatever software or processes I have that depends on ots can survive beyond the operations of those public servers :-)

rijndael

bitcoin

OpenTimestamps: Scalable, Trust-Minimized, Distributed Timestamping with Bitcoin

petertodd

Thanks for the donation!

Yeah, running your own calendar server isn't very helpful right now. We've got four of them, and that's plenty; each additional one means there's more data that the world needs to save to be sure we can validate every timestamp.

On the other hand, it's very helpful if lots of people know _how to_ run a calendar server, in case the centralized ones go down and the community needs to create new ones. So feel free to experiment with running one! But better off that no-one uses it in production.