<p>To sync faster I have updated my bitcoin.conf file by adding the node addresses.
My latest config file is similar to this:</p>

<pre><code>testnet=1
regtest=0
dnsseed=0
upnp=0
setgenerate=1
blocksonly=1

server=1

addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151

maxconnections=15
minrelaytxfee=0.0001
maxmempool=200
maxreceiverbuffer=2500
maxsendbuffer=500
dbcache=16000

rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass
</code></pre>

CC BY-SA 4.0
2021-07-06T18:24:37.710Z
remember when using testnet rpc config needs to go under [test] section.
pseudozach
CC BY-SA 3.0
2018-04-12T08:20:42.493Z
2018-04-12T08:20:42.493Z
User97693321
<p>In general, you can use <a href="https://jlopp.github.io/bitcoin-core-config-generator/" rel="nofollow noreferrer">Lopp's Bitcoin Core config file generator</a> to set up your Bitcoin Core config files. Parameters are collected in groups by topic (e.g: Mining, Networking, ...). Moreover, each parameter contains a description of what it is used for and what is it's default value.</p>

CC BY-SA 3.0
2018-04-10T08:29:14.410Z
2018-04-10T08:29:14.410Z
sr_gi
<p>Meanwhile...</p>
<p>addnode needs to be in the [test] section for testnet. So it's</p>
<pre><code>[test]
addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151
</code></pre>
<p>now.</p>

CC BY-SA 4.0
2021-08-22T15:20:44.127Z
2021-08-22T15:20:44.127Z
Rainer Feike
<p>To sync faster your config should be like that:</p>

<pre><code>testnet=1
blocksonly=1
rpcport=5000
server=1
listen=0
prune=1000 # this has no effect during syncing 
dbcache=16000 # will take too much memory
rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass
</code></pre>

CC BY-SA 3.0
2018-04-07T16:06:32.363Z
Thanks @Adam, I will try this.  And I want to know should we use rpcallowip=0.0.0.0/0 or we can remove from the config file because this is 0 only?
User97693321
CC BY-SA 3.0
2018-04-07T17:04:50.760Z
If you want to use RPC remotely you should set here your IP range or 0.0.0.0/0 for any IP.
Tailer
CC BY-SA 3.0
2018-04-07T13:51:11.633Z
2018-04-07T13:51:11.633Z
Tailer
<p>I am new to blockchain, I want to setup my node in testnet network in my ubuntu machine. </p>

<p>I am using this below mentioned bitcoin.conf file. Is this the correct format to sync the node faster?  Or I need to do the changes in this config file.</p>

<pre><code>testnet=1
dnsseed=0
upnp=0
setgenerate=1
blocksonly=1

port=12000
rpcport=5000

server=1
prune=1000

rpcallowip=0.0.0.0/0

rpcuser=someuser
rpcpassword=somepass
</code></pre>

<p>I am referring this link to setup my bitcoin node <a href="https://www.codeooze.com/blockchain/bitcoind-running-in-docker/" rel="nofollow noreferrer">https://www.codeooze.com/blockchain/bitcoind-running-in-docker/</a></p>

CC BY-SA 3.0
2018-04-08T05:57:26.773Z
I have started the node sync:
User97693321
<bitcoin-core><bitcoind><testnet>
Bitcoin config file to setup bitcoin node in testnet network in ubuntu
User97693321
# Bitcoin config file to setup bitcoin node in testnet network in ubuntu

(Asked by: username_0 on 2018-04-07)

I am new to blockchain, I want to setup my node in testnet network in my ubuntu machine. 
I am using this below mentioned bitcoin.conf file. Is this the correct format to sync the node faster?  Or I need to do the changes in this config file.
testnet=1
dnsseed=0
upnp=0
setgenerate=1
blocksonly=1

port=12000
rpcport=5000

server=1
prune=1000

rpcallowip=0.0.0.0/0

rpcuser=someuser
rpcpassword=somepass

I am referring this link to setup my bitcoin node https://www.codeooze.com/blockchain/bitcoind-running-in-docker/

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

> **Comments:**
> **username_0**: I have started the node sync:  

---

## 4 answers

### Answer by username_0 on 2018-04-12. Score: 0 | Accepted answer

To sync faster I have updated my bitcoin.conf file by adding the node addresses.
My latest config file is similar to this:
testnet=1
regtest=0
dnsseed=0
upnp=0
setgenerate=1
blocksonly=1

server=1

addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151

maxconnections=15
minrelaytxfee=0.0001
maxmempool=200
maxreceiverbuffer=2500
maxsendbuffer=500
dbcache=16000

rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass

> **Comments:**
> **username_1**: remember when using testnet rpc config needs to go under [test] section.  

---

### Answer by username_2 on 2018-04-10. Score: 2

In general, you can use [Lopp's Bitcoin Core config file generator](https://jlopp.github.io/bitcoin-core-config-generator/) to set up your Bitcoin Core config files. Parameters are collected in groups by topic (e.g: Mining, Networking, ...). Moreover, each parameter contains a description of what it is used for and what is it's default value.


---

### Answer by username_3 on 2021-08-22. Score: 2

Meanwhile...
addnode needs to be in the [test] section for testnet. So it's
[test]
addnode=104.237.131.138
addnode=151.80.205.132
addnode=192.155.82.123
addnode=74.220.255.190
addnode=80.100.203.151

now.


---

### Answer by username_4 on 2018-04-07. Score: 1

To sync faster your config should be like that:
testnet=1
blocksonly=1
rpcport=5000
server=1
listen=0
prune=1000 # this has no effect during syncing 
dbcache=16000 # will take too much memory
rpcallowip=0.0.0.0/0
rpcuser=someuser
rpcpassword=somepass

> **Comments:**
> **username_0**: Thanks @Adam, I will try this.  And I want to know should we use rpcallowip=0.0.0.0/0 or we can remove from the config file because this is 0 only?  
> **username_4**: If you want to use RPC remotely you should set here your IP range or 0.0.0.0/0 for any IP.  

---

