<blockquote>
  <p>I have to fill in these values in the config:
  <code>bitcoind.rpcuser=bitcoind_rpc_user_string</code>
  <code>bitcoind.rpcpass=bitcoind_rpc_password_string</code></p>
</blockquote>

<p>These are user defined, and used to authenticate and communicate with your full node. There is no authentication to the network, anyone is free to join. </p>

<p>You’ll want to define a username and password in your bitcoind <code>bitcoin.conf</code> file, and then input them here so that lnd can connect to your node. </p>

<blockquote>
  <p>Also can someone explain these settings to me:
  <code>bitcoind.zmqpubrawblock=tcp://127.0.0.1:18501</code>
  <code>bitcoind.zmqpubrawtx=tcp://127.0.0.1:18502</code>
  Is 127.0.0.1 ok to leave for these values?</p>
</blockquote>

<p>ZMQ allows lnd and bitcoind to exchange info through a socket connection (getting new info about blocks and transactions). If the nodes (lnd, bitcoind) are on the same machine you can leave the address as the localhost (127.0.0.1).</p>

CC BY-SA 4.0
2018-08-19T21:10:24.240Z
Also yes, my bitcoin full node and my LND node are running on the same machine. So I'm good with 127.0.0.1. Thanks again!
user99201
CC BY-SA 4.0
2018-08-19T20:57:22.817Z
2018-08-19T20:57:22.817Z
chytrik
<p>I'm setting up an LND node so I can learn about Lightning Networks. I apparently need a set of user credentials so that I can connect to the network.</p>

<p>How do I get the credentials that I need to set this up? Is it possible for an average user who is just trying to learn about LND? </p>

<p>Ideally I would like to connect to the main net, so that I can connect my Zap wallet to it.</p>

<p>I have to fill in these values in the config:</p>

<pre><code>bitcoind.rpcuser=bitcoind_rpc_user_string
bitcoind.rpcpass=bitcoind_rpc_password_string
</code></pre>

<p>Also can someone explain these settings to me:</p>

<pre><code>bitcoind.zmqpubrawblock=tcp://127.0.0.1:18501
bitcoind.zmqpubrawtx=tcp://127.0.0.1:18502
</code></pre>

<p>Is 127.0.0.1 ok to leave for these values?</p>

<p>Thanks</p>

<bitcoin-core><lightning-network-daemon><zap>
How do I get credentials on the bitcoin network?
user99201
# How do I get credentials on the bitcoin network?

(Asked by: username_0 on 2018-08-19)

I'm setting up an LND node so I can learn about Lightning Networks. I apparently need a set of user credentials so that I can connect to the network.
How do I get the credentials that I need to set this up? Is it possible for an average user who is just trying to learn about LND? 
Ideally I would like to connect to the main net, so that I can connect my Zap wallet to it.
I have to fill in these values in the config:
bitcoind.rpcuser=bitcoind_rpc_user_string
bitcoind.rpcpass=bitcoind_rpc_password_string

Also can someone explain these settings to me:
bitcoind.zmqpubrawblock=tcp://127.0.0.1:18501
bitcoind.zmqpubrawtx=tcp://127.0.0.1:18502

Is 127.0.0.1 ok to leave for these values?
Thanks

**Tags:** bitcoin-core, lightning-network-daemon, zap


---

## 1 answers

### Answer by username_1 on 2018-08-19. Score: 3 | Accepted answer

> I have to fill in these values in the config:
> `bitcoind.rpcuser=bitcoind_rpc_user_string`
> `bitcoind.rpcpass=bitcoind_rpc_password_string`

These are user defined, and used to authenticate and communicate with your full node. There is no authentication to the network, anyone is free to join.

You’ll want to define a username and password in your bitcoind `bitcoin.conf` file, and then input them here so that lnd can connect to your node.

> Also can someone explain these settings to me:
> `bitcoind.zmqpubrawblock=tcp://127.0.0.1:18501`
> `bitcoind.zmqpubrawtx=tcp://127.0.0.1:18502`
> Is 127.0.0.1 ok to leave for these values?

ZMQ allows lnd and bitcoind to exchange info through a socket connection (getting new info about blocks and transactions). If the nodes (lnd, bitcoind) are on the same machine you can leave the address as the localhost (127.0.0.1).

> **Comments:**
> **username_0**: Also yes, my bitcoin full node and my LND node are running on the same machine. So I'm good with 127.0.0.1. Thanks again!  

---

