Skip to content
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

Closed
ghost opened this issue Sep 4, 2019 · 8 comments
Closed

Comments

@ghost
Copy link

ghost commented Sep 4, 2019

Some progress here: https://github.com/teran-mckinney/bitcash

@merc1er
Copy link
Member

merc1er commented Nov 22, 2019

I don't thing cashexplorer.bitcoin.com was ever a thing (it's explorer.bitcoin.com).
But now the API is located at rest.bitcoin.com.

I added bitcore support in #46. I would like implement rest.bitcoin.com support for redundancy :)

@ghost
Copy link
Author

ghost commented Nov 22, 2019

Looks like this API blocks Tor users so does cause issues that way.

@merc1er
Copy link
Member

merc1er commented Dec 8, 2019

This issue should be fixed by #47

Looks like this API blocks Tor users so does cause issues that way.

Both rest.bitcoin.com and api.bitcore.io work for me on Tor Browser. Are you still experiencing this issue?

@ghost
Copy link
Author

ghost commented Dec 8, 2019

Ok, off topic:

urllib3.connectionpool: DEBUG: Starting new HTTPS connection (1): trest.bitcoin.com:443
urllib3.connectionpool: DEBUG: https://trest.bitcoin.com:443 "GET /v2//rawtransactions/sendRawTransaction/01000000016450c5c7fb706f5c0cdf1b3fbb1d98b66f8d049770c61fd8763c8e8cda712b83010000006a4730440220528f7ac6565916f1ad2e4e8e8f453efa47afa349203b08a2de0e9af78d19229802202a4a00cdda40c4dfbe03ee9208ea0f6b2898a4271013e6a014c4902fa50461e64121033d5c2875c9bd116875a71a5db64cffcb13396b163d039b1d9327824891804334ffffffff02d0070000000000001976a914e7c1345fc8f87c68170b3aa798a956c2fe6a9eff88ac64621b00000000001976a914990ef60d63b5b5964a1c2282061af45123e93fcb88ac00000000 HTTP/1.1" 404 36

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 (torsocks curl). So rest.bitcoin.com needs to configure Cloudflare to not filter by user agent.

Edit: Wanted to add this: https://forum.bitcoin.com/post299881.html

@merc1er
Copy link
Member

merc1er commented Dec 8, 2019

Is it really a GET request for sending a TX? Not a POST?

Yes, for a single transaction it is a GET.
You can also use POST for multiple transactions (as per the docs on rest.bitcoin.com).

Regarding Tor, I will ask the Bitcoin.com team if they can expedite this.

@ghost
Copy link
Author

ghost commented Dec 9, 2019

Gotcha. Thank you!

@merc1er
Copy link
Member

merc1er commented Dec 26, 2019

@teran-mckinney could you close this? 👍

@ghost ghost closed this as completed Dec 26, 2019
@ghost
Copy link
Author

ghost commented Jan 5, 2020

@merc1er thanks for finding this issue! Bitcoin-com/rest.bitcoin.com#333

Good to know we have an answer now.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant