<p>my lightning network backend is <code>bitcoind</code>. Interesting when I execute <code>getnewaddress label bech32</code> another bech32 address is automatically generated. I found it because at the lightning network console pops up a new line <code>[INF] RPCS: [newaddress] addr=xxxxx</code> and it is not the same as the address at <code>bitcoind</code>. </p>

<p>It doesn't happen if I created with another wallet type such as legacy wallet.</p>

<p>So my questions are
1. why another address? what is the purpose of this automative generation?
2. what is the link between these two addresses? does deposit at one affect another in a descrete way?</p>

CC BY-SA 4.0
2019-11-21T04:47:06.970Z
Which lightning client are you using? c-lightning?
m1xolyd1an
CC BY-SA 4.0
2019-11-21T05:45:07.110Z
nope, the lightning network. https://github.com/lightningnetwork/lnd
Hami
CC BY-SA 4.0
2019-11-21T06:26:52.403Z
That’s lnd, not the lightning network.
Claris
CC BY-SA 4.0
2019-11-22T06:16:37.507Z
so lighting network includes lnd, c-lightning etc?
Hami
CC BY-SA 4.0
2020-02-04T15:14:34.860Z
LND, C-Lightning, are implementations that both follow the specifications of the lightning network, and so, for the most part can communicate and function together on the same lightning network. It would be possible to: 1. fork LND, change one line, and then claim there is a third implementation on the lightning network. 2. Run a separate lightning network that listens on different ports, that exists on another plane than the lightning network we have today.
Paul Kania
CC BY-SA 4.0
2020-02-05T02:48:57.233Z
@HamiltonWong `lnd` and `c-lightning` are both Lightning implementations. You can choose either. It's like you can use Firefox or Chrome to browse the WWW.
Pieter Wuille
<bitcoind><lightning-network><address-generation><bech32-address>
Creating bech32 address on bitcoin core automatically generate another address on lightning network
Hami
# Creating bech32 address on bitcoin core automatically generate another address on lightning network

(Asked by: username_0 on 2019-11-21)

my lightning network backend is `bitcoind`. Interesting when I execute `getnewaddress label bech32` another bech32 address is automatically generated. I found it because at the lightning network console pops up a new line `[INF] RPCS: [newaddress] addr=xxxxx` and it is not the same as the address at `bitcoind`.

It doesn't happen if I created with another wallet type such as legacy wallet.

So my questions are
1. why another address? what is the purpose of this automative generation?
2. what is the link between these two addresses? does deposit at one affect another in a descrete way?

**Tags:** bitcoind, lightning-network, address-generation, bech32-address

> **Comments:**
> **username_1**: Which lightning client are you using? c-lightning?  
> **username_0**: nope, the lightning network. https://github.com/lightningnetwork/lnd  
> **username_2**: That’s lnd, not the lightning network.  
> **username_0**: so lighting network includes lnd, c-lightning etc?  
> **username_3**: LND, C-Lightning, are implementations that both follow the specifications of the lightning network, and so, for the most part can communicate and function together on the same lightning network. It would be possible to: 1. fork LND, change one line, and then claim there is a third implementation on the lightning network. 2. Run a separate lightning network that listens on different ports, that exists on another plane than the lightning network we have today.  
> **username_4**: @HamiltonWong `lnd` and `c-lightning` are both Lightning implementations. You can choose either. It's like you can use Firefox or Chrome to browse the WWW.  

---

## 0 answers

