Riccardo Casatta

Hi @dhimmel, In a test [branch](https://github.com/RCasatta/opentimestamps-client/tree/keccak) I have the verbose output info which will print the following: ``` $ ./ots -v info examples/hello-world.txt.ots File sha256 hash: 03ba204e50d126e4674c005e04d82e84c21366780af1f43bd54a37816b6ab340 Timestamp: ripemd160 (03ba204e50d126e4674c005e04d82e84c21366780af1f43bd54a37816b6ab340)...

> I still think that in the long run you may want to use a standardized file format. I expect many users will want to do automated tasks using this...

> How about we make the text output look something like: > `sha256 == c703019e959a8dd3faef7489bb328ba485574758e7091f01464eb65872c975c8efa898490f9cc0dcd698220e9a9c1acc01b54c1c14b23520ace3cd82341f6b45` This is already better. We should consider also Andrew's more verbose output: https://gist.github.com/RCasatta/538e7e9bce6dc1158ced877035ce9f1a

Here is my last test: - After `==` there is the result of the current operation - There are tags starting with `#` for bitcoin transaction and merkle root (this...

> You could get the block hash from several online block explorers that provide an API. This might be an OK compromise for your scenario depending on your trust/security requirements....

I agree to match standard commands semantics, so exit 0 in the highlighted code, we should probably change also the message to something like "Temporary failure! Timestamp not yet complete"

I can reproduce on Mac Os X Catalina 10.15.4, looks an issue with SSL lib ``` Process: Python [16877] Path: /usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: 3.7.6 (3.7.6) Code Type: X86-64 (Native)...

temporary fix: if you have openssl installed (if not you could run `brew install openssl`) you can do: `export DYLD_LIBRARY_PATH=/usr/local/opt/openssl/lib:$DYLD_LIBRARY_PATH` before running `ots` and it should work

It would work **roughly** work like this: `ots verify proof.ots` - if bitcoin is running use it - if it's not running do *light verification* ## light verification `proof.ots` attestation...

I think we don't support the bitcoin conf with sections. `stamp` is not using the local node at all, that's why it's working.