Roles of the public and privileged bitcoind users #727
-
I recently migrated my bitcoind and lnd instances over to nix-bitcoin, but ran into just one small hiccup during the process. I have bitcoind and lnd running on different machines and wanted to keep it that way. I got bitcoind running no problem and then followed these recommend settings for "remote bitcoind" on my lnd instance. lnd wasn't happy at first and it took me a bit to realize it was using the wrong rpc username. I interpreted the docs as "use the Is there a reason to not just set both the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yes, the docs only make minimal assumptions about the remote bitcoind node, which may not be a nix-bitcoin node. Setting all RPC user names to the same privileged user name does away with the security benefits of nix-bitcoin's fine-grained RPC permissions, but it requires no further setup on the bitcoind node. If your remote bitcoind node runs on nix-bitcoin, you can configure
|
Beta Was this translation helpful? Give feedback.
Yes, the docs only make minimal assumptions about the remote bitcoind node, which may not be a nix-bitcoin node.
So they assume that just a privileged RPC user exists.
Setting all RPC user names to the same privileged user name does away with the security benefits of nix-bitcoin's fine-grained RPC permissions, but it requires no further setup on the bitcoind node.
If your remote bitcoind node runs on nix-bitcoin, you can configure
lnd
to use the restrictedpublic
RPC user like so:Remove these settings that are mentioned in the manual: