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?

  • Which lightning client are you using? c-lightning?
    – m1xolyd1an
    Nov 21, 2019 at 4:47
  • nope, the lightning network. github.com/lightningnetwork/lnd
    – Hami
    Nov 21, 2019 at 5:45
  • That’s lnd, not the lightning network.
    – Claris
    Nov 21, 2019 at 6:26
  • so lighting network includes lnd, c-lightning etc?
    – Hami
    Nov 22, 2019 at 6:16
  • 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
    Feb 4, 2020 at 15:14


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.