Peter Todd

> The issue with a minimum work threshold is for older timestamps you need to validate a _lot_ of headers to get a reasonable amount of total work. ASICs have...

Alright, who knows what I should be using? I try to do Rust these days so I have no idea what's up with Python now.

Closing, as this has been fixed in v0.6.0

BTW we're now using a third-party service to monitoring OTS calendar uptime: https://uptime.opentimestamps.net/ This isn't perfect, as it isn't smart enough to check if the timestamps returned are actually correct....

Doesn't seem like we made enough progress on this to do anything. You're welcome to open a new pull-req though later! Though in general, I think "performance-based" tests for availability...

Fixed as of v0.6.0

Fixed as of https://github.com/opentimestamps/opentimestamps-server/tree/opentimestamps-server-v0.6.0

Closing as "won't fix" for now, as there's potential security issues in giving third-parties the ability to get data into OTS proofs via their transactions. That'd probably be ok with...

It's important to recognize that this *is* a security reduction, even though it only applies to assumed-valid blocks: one of the reasons why assume-valid is acceptable, is because the data...

On February 9, 2023 12:57:27 PM GMT+01:00, Sjors Provoost ***@***.***> wrote: >> an adversary can easily spin up patched Bitcoin nodes that do not serve those witnesses, in conjunction with...