Replies: 1 comment 1 reply
-
|
https endpoint doesn't seem to be supported? Results in |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to use the RPC client with a 3rd party node provider such as Quicknode/Getblock etc. which all provide a URL to a testnet/mainnet node without any basic auth credentials.
Ex:
https://bright-misty-tudor.btc-testnet.quiknode.pro/<id>/https://go.getblock.io/<id>Looking at the docs/tracing through the code, one of username/password or cookie auth must be provided, when using the
rpcclient:(There's a
fs.staterror thrown since cookie path is empty).Is there a way to use the RPC client to work with 3rd party provider node URLs like the above?
I made sure that these work fine with a curl command like so:
Beta Was this translation helpful? Give feedback.
All reactions