<p>By default <code>bitcoind</code> will look for the file <code>bitcoin.conf</code> in its <code>datadir</code> directory, whether running on testnet or mainnet.  But you could use the <code>-conf</code> option when starting one or both of the daemons, to point it to a different file.</p>

CC BY-SA 3.0
2017-11-12T21:55:56.790Z
2017-11-12T21:55:56.790Z
Nate Eldredge
<p>No, it is currently not possible to have network specific configuration files. However there are currently open pull requests which enable such functionality.</p>

CC BY-SA 3.0
2017-12-13T03:28:58.193Z
2017-12-13T03:28:58.193Z
Ava Chow
<p>When running <code>bitcoind</code> on testnet, can I put its configuration settings in a separate <code>bitcoin.conf</code> file from the "real" <code>bitcoin.conf</code> file?  I would like to be able to run two nodes concurrently, one on the live network and one on the test network, each with its own configuration settings.</p>

<bitcoin-core><bitcoind><testnet>
Can a testnet node have a separate bitcoin.conf file?
Jan Hettich
# Can a testnet node have a separate bitcoin.conf file?

(Asked by: username_0 on 2017-11-12)

When running `bitcoind` on testnet, can I put its configuration settings in a separate `bitcoin.conf` file from the "real" `bitcoin.conf` file? I would like to be able to run two nodes concurrently, one on the live network and one on the test network, each with its own configuration settings.

**Tags:** bitcoin-core, bitcoind, testnet


---

## 2 answers

### Answer by username_1 on 2017-11-12. Score: 3

By default `bitcoind` will look for the file `bitcoin.conf` in its `datadir` directory, whether running on testnet or mainnet. But you could use the `-conf` option when starting one or both of the daemons, to point it to a different file.


---

### Answer by username_2 on 2017-12-13. Score: 0

No, it is currently not possible to have network specific configuration files. However there are currently open pull requests which enable such functionality.


---

