-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
verify gives a lot of HTML/HTTP 502 and 400 messages on stderror #40
Comments
Noticed this as well: #37 (comment) Looks like http://www.localbitcoinschain.com/ is down: |
Maybe we need a patch that prevents from making subsequent calls to broken insight servers. |
When I comment out the broken server I still some of the error messages:
|
Not sure, but could it be that after an |
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: => 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 #41). |
So my suggestion:
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.
The text was updated successfully, but these errors were encountered: