<p>You could be running Bitcoin Core on your desktop and issuing RPC commands from your laptop. In this example you might want to put <code>rpcbind=0.0.0.0</code> and <code>rpcallowip=192.168.1.10</code> or your laptop’s lan IP.</p>
<p>Rpcbind binds to a socket, this happens in the networking layer. Without it packets won’t even reach bitcoin core. Rpcallowip is used for authorization which happens in the application layer. Packets need to be able to reach bitcoin core before the command can be authorized so in a sense rpcallowip needs to be a subnet of rpcbind</p>

CC BY-SA 4.0
2023-01-09T13:25:24.023Z
2023-01-09T13:25:24.023Z
Mike D
<p>What's the difference between these two settings in the bitcoin conf file?
'rpcallowip' and 'rpcbind'</p>

<bitcoin-core><json-rpc><bitcoin.conf>
What's the difference between 'rpcallowip' and 'rpcbind'?
PaperFrog
# What's the difference between 'rpcallowip' and 'rpcbind'?

(Asked by: username_0 on 2023-01-09)

What's the difference between these two settings in the bitcoin conf file?
'rpcallowip' and 'rpcbind'

**Tags:** bitcoin-core, json-rpc, bitcoin.conf


---

## 1 answers

### Answer by username_1 on 2023-01-09. Score: 4 | Accepted answer

You could be running Bitcoin Core on your desktop and issuing RPC commands from your laptop. In this example you might want to put `rpcbind=0.0.0.0` and `rpcallowip=192.168.1.10` or your laptop’s lan IP.

Rpcbind binds to a socket, this happens in the networking layer. Without it packets won’t even reach bitcoin core. Rpcallowip is used for authorization which happens in the application layer. Packets need to be able to reach bitcoin core before the command can be authorized so in a sense rpcallowip needs to be a subnet of rpcbind


---

