I was more worried about memory as I may end up polling a large number of invoices. Does lnd write each invoice to disk? I didn't know that.
Discussion
I would expect invoice creation to result in a disk IO, as I'd expect it to write the invoice data synchronously to disk as a power outage at the wrong time could otherwise cause issues. But maybe it delays that until payment happens. Maybe.
This thread encouraged me to explore open timestamps further.
wonder if there is any precedence of opentimestamps accepted as evidence in a say copyright lawsuit?
Any usage metrics?
BTW, a cost saving workflow I discovered recently. moved my full Bitcoin node & lightning node to my home (Proxmox) lab where storage cost is nothing (mirrored ZFS, some fault tolerance). Got a cheap VPS which runs my ln address server (I could have left it at home server as well) etc. Established a tunnel using wireguard. works great, next step is signed heartbeat calls from home to vps to update ISP provided IP address if that ever changes. Works great so far.
As far as I can tell timestamps have pretty much never come up officially in the US federal court system. But that doesn't mean they're worthless. Quite the contrary! It probably means they're so strong that no-one has been foolish enough to contest one in court rather than just settling.
Re: usage, people are likely making something like 1 to 10 timestamps per second average with OpenTimestamps. I can't tell for sure though, as people making large numbers of timestamps per second can (and should!) aggregate their timestamps with merkle trees on their end.