Open m-schmoock opened 5 years ago
Noticed this as well: https://github.com/opentimestamps/javascript-opentimestamps/issues/37#issuecomment-439115754
Looks like http://www.localbitcoinschain.com/ is down:
Maybe we need a patch that prevents from making subsequent calls to broken insight servers. Shall I make one?
When I comment out the broken server I still some of the error messages:
Could not connect to local Bitcoin node
Could not connect to local Bitcoin node
Could not connect to local Bitcoin node
Could not connect to local Bitcoin node
Insight response error: StatusCodeError: 400 - "Block height out of range. Code:-8"
Insight response error: StatusCodeError: 400 - "Block height out of range. Code:-8"
Insight response error: StatusCodeError: 400 - "Block height out of range. Code:-8"
Insight response error: StatusCodeError: 400 - "Block height out of range. Code:-8"
Lite-client verification, assuming block 0000000000000000001b7bb07548b2ea609cf018b88026d14d28d56bf96b5869 is valid
Lite-client verification, assuming block 0000000000000000001b7bb07548b2ea609cf018b88026d14d28d56bf96b5869 is valid
Lite-client verification, assuming block 0000000000000000001b7bb07548b2ea609cf018b88026d14d28d56bf96b5869 is valid
Lite-client verification, assuming block 0000000000000000001b7bb07548b2ea609cf018b88026d14d28d56bf96b5869 is valid
Insight response error: StatusCodeError: 400 - "Can't read block from disk. Code:-32603"
Insight response error: StatusCodeError: 400 - "Can't read block from disk. Code:-32603"
Insight response error: StatusCodeError: 400 - "Can't read block from disk. Code:-32603"
Insight response error: StatusCodeError: 400 - "Can't read block from disk. Code:-32603"
Success! Bitcoin block 550218 attests existence as of 2018-11-15 CET
Could not connect to local Bitcoin node
Not sure, but could it be that after an upgrade
it expects a local Bitcoin node in the used environment?
With a non-upgraded OTS file I get the same messages.
True, then it might just be the error message from the missing localbitcoinschain.com server.
nope, the otther errors come from bitaccess.co server:
=> Can\'t read block from disk. Code:-32603
How do you handle failing servers in this repo? Just removing them ist the dirty way, should there be a way to detect and blacklist failing endpoints?
When you remove localbitcoinschain and bitaccess the lib does not produce ugly output anymore.
A good way would be to have a DNS bootstrap list or something for this project that we can update.
Hi, lite client verification sucks very often, and it is a not a "safe" verification. For this reason, the library calls multiple explorers. Moreover, only a few explorers in the list support cors (to work inside the browser). The safe way is to connect to your bitcoin node. Every suggestion on error message is welcome (as https://github.com/opentimestamps/javascript-opentimestamps/pull/41).
So my suggestion:
localbitcoinschain
and bitaccess
.I will update #41 as soon as my bitcore server is ready.
Done. I updated PR #41
When I try to verify a timestamp using the CLI, the output looks broken.
The verification seems to go trhough, also the OTS can be upgraded, but the output looks seriously broken. Tried this on serveral machines and networks.
This issue exist for me at least for a month.