Peter Todd

Sorry, I really don't have any idea. :( I'm not a web-dev expert; if I were in your position I'd open up yoru browsers network debugging console and start trying...

Actually, that sounds like a mistake in python-opentimestamps; I can't think of a good reason for equality to ignore attestations. -- https://petertodd.org 'peter'[:-1]@petertodd.org

For tech support, I'd suggest opening an issue on github for your problem. That way everyone else who is also having that issue can see the problem and resolution.

@marcosgabbardo Cool! Q: is your system actually using the standard OpenTimestamps calendars? Or your own set?

On Fri, Jan 04, 2019 at 10:47:07PM +0000, Marcos Gabbardo wrote: > @petertodd we use standard OpenTimestamps calendar and our own at: http://btc.calendar.datastamp.io > > i do not restrict only...

On Fri, Jan 04, 2019 at 03:01:41PM -0800, Marcos Gabbardo wrote: > today we do have in our API do download do download backups, but they can use our web...

Basically it takes time for a transaction to get mined. But your timestamp is complete the moment you make it in the sense that you *will* be any to verify...

> I thought that 1 confirmation is enough? Can you please help me understand: The timestamp calendars wait a few confirmations before adding the proof to the database, because the...

> For simplicity, I am OK to display in the UI how many confirmations have passed (if less than 6) and after that show the date. I'm not. It's misleading...

Concept ACK I'm proposing this for python-bitcoinlib too, which is where all this code comes from originally: https://github.com/petertodd/python-bitcoinlib/pull/299