Open JeffWScott opened 5 years ago
It's not possible to access the BCH API?
Url is now api.bitcore.io
On Sun, Aug 11, 2019, 8:09 AM Vimiso notifications@github.com wrote:
It's not possible to access the BCH API?
ie. https://bch-insight.bitpay.com/api/status
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitpay/insight/issues/990?email_source=notifications&email_token=AAAYEHDVQ3K6DYS66QLCDOTQD7XQPA5CNFSM4IF3JNZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4A6W5I#issuecomment-520219509, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAYEHB3IP2YMKC5ZU4EN6LQD7XQPANCNFSM4IF3JNZA .
Given https://api.bitcore.io/api/BCH/mainnet, for example, it seems to use a different URI structure for all requests?
expected /api/BCH/mainnet/blocks
=> actual /api/BCH/mainnet/block?limit=50
.
Should this API be treated differently to a bitcore insight REST API? And what differentiates them?
Also checking to see if a chain is fully synced is not possible? The closest I can see is /api/status/enabled-chains
but no sync details exist.
Looks like you guys are ditching the network. Is that true?