<p>The rpc user/pass is only needed if you're planning to access the node via RPC. If you're running Armory on top of it, for example, that requires RPC and hence you would need it (Armory auto-creates the rpcuser/password for you, though).</p>

<p>If you're running a node and don't need the RPC functionality, no, you don't need those parameters set.</p>

CC BY-SA 3.0
2016-12-16T19:04:25.273Z
Thanks v much Jimmy. This means I can keep same config file.
Sven Williamson
CC BY-SA 3.0
2016-12-16T18:51:16.613Z
2016-12-16T18:51:16.613Z
Jimmy Song
<p>When running several <code>bitcoind</code> nodes on different machines, can I simply keep the same <code>bitcoin.conf</code> file everywhere, or do I need to ensure that a different <code>rpcuser</code> is set up for each? </p>

<bitcoind><json-rpc><bitcoin.conf><authentication>
Do you need to change 'rpcuser' and 'rpcpassword' for each bitcoind node you run?
Sven Williamson
# Do you need to change 'rpcuser' and 'rpcpassword' for each bitcoind node you run?

(Asked by: username_0 on 2016-12-16)

When running several `bitcoind` nodes on different machines, can I simply keep the same `bitcoin.conf` file everywhere, or do I need to ensure that a different `rpcuser` is set up for each?

**Tags:** bitcoind, json-rpc, bitcoin.conf, authentication


---

## 1 answers

### Answer by username_1 on 2016-12-16. Score: 1 | Accepted answer

The rpc user/pass is only needed if you're planning to access the node via RPC. If you're running Armory on top of it, for example, that requires RPC and hence you would need it (Armory auto-creates the rpcuser/password for you, though).

If you're running a node and don't need the RPC functionality, no, you don't need those parameters set.

> **Comments:**
> **username_0**: Thanks v much Jimmy. This means I can keep same config file.  

---

