Add possibility to use custom or non-bitcoin Bitcore server

[prusnak]

Add possibility to use custom or non-bitcoin Bitcore server

[kantai]

Hi @prusnak -- I'd like to cast a vote in favor of option (2) -- perhaps giving the user a dialog to chose a different bitcore URL during the connect-approval popup (a related question is, does the bitcore node configuration setting in a user's wallet affect this at all?)

A (probably common?) use case currently not served by connect.js is the ability to use a Trezor to make testnet transactions on a local regtest network. This is useful for a couple different things, but mostly it is much easier to test behaviors on a local regtest network than on the public testnet. This can be done with trezor.js, but I see that's being deprecated in favor of connect.js, so it'd be great to see support for that here as well.

[MrDefacto]

At least Dash instance +1 ;-)

[keraf]

Custom backends can be set using Trezor.blockchainSetCustomBackend.

See: https://github.com/trezor/connect/blob/develop/src/js/core/methods/blockchain/BlockchainSetCustomBackend.js

Closing issue.