2

Let's say that I were to pass --rpc-bind-ip 0.0.0.0 to monerod, and also --restricted-rpc (along with the external bind confirmation), what would the outcome be? What does the second command do when interacting with the first? What happens when we add rpc-login specifications into the mix?

I'd love to understand how the different combinations of these parameters interact. What's going on under the hood?

  • --rpc-bind-ip 0.0.0.0
  • --restricted-rpc
  • --rpc-login user:pw
  • --rpc-bind-ip 0.0.0.0 --restricted-rpc
  • --restricted-rpc --rpc-login user:pw
  • --rpc-bind-ip 0.0.0.0 --rpc-login user:pw
  • --rpc-bind-ip 0.0.0.0 --restricted-rpc --rpc-login user:pw

1 Answer 1

1

--restricted-rpc, answered here and detailed in the --help:

Restrict RPC to view only commands and do not return privacy sensitive data in RPC calls

You'd probably want to use this if you plan on making your daemon publicly accessible.

--rpc-bind-ip 0.0.0.0, means that the daemon will bind (listen) on all the IP addresses on all interfaces.

--rpc-login user:pw, means that a username "user" and password "pw" is required to access the RPC interface. You'd probably want to use this if you plan on making your daemon publicly accessible.

All these options are documented in the help output (monerod --help), and you can use any mixture/combination of them (or none at all).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.