-
Notifications
You must be signed in to change notification settings - Fork 39
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
cashexplorer.bitcoin.com was taken down, replace with api.bitcore.io? #42
Comments
I don't thing cashexplorer.bitcoin.com was ever a thing (it's explorer.bitcoin.com). I added bitcore support in #46. I would like implement rest.bitcoin.com support for redundancy :) |
Looks like this API blocks Tor users so does cause issues that way. |
This issue should be fixed by #47
Both rest.bitcoin.com and api.bitcore.io work for me on Tor Browser. Are you still experiencing this issue? |
Ok, off topic:
Is it really a GET request for sending a TX? Not a POST? Also gives me a 404, but over Tor. Not sure over clearnet. Looks like Tor Browser works with https://rest.bitcoin.com/v2/address/utxo/bitcoincash:qzfyvx77v2pmgc0vulwlfkl3uzjgh5gnmqk5hhyaa6 but the library does not. If you curl it, it blocks it ( Edit: Wanted to add this: https://forum.bitcoin.com/post299881.html |
Yes, for a single transaction it is a GET. Regarding Tor, I will ask the Bitcoin.com team if they can expedite this. |
Gotcha. Thank you! |
@teran-mckinney could you close this? 👍 |
@merc1er thanks for finding this issue! Bitcoin-com/rest.bitcoin.com#333 Good to know we have an answer now. |
Some progress here: https://github.com/teran-mckinney/bitcash
The text was updated successfully, but these errors were encountered: