Open rsafier opened 3 years ago
I have received a little bit more information from someone that connected to this custom signet with btcd. They did have to include the bitcoin.signetchallenge=512102ee856c56a5aaadd1656f849bafa4c9dacc86a2878fe546c6189185f842ae2c1851ae in order to properly connect, without it they received similiar chain control error. So it appears that this issue only applies to users of bitcoind backend, behavior is working as expected when using btcd backend
Also have tested running in neutrino mode, this does require bitcoin.signetchallenge= be set in order to properly sync with a custom signet chain.
I encountered this issue as well with a custom signet. Removing the signet challenge from lnd.conf allowed lnd to connect and sync with bitcoin core. For me it had different integers in both expected and actual:
unable to create partial chain control: expected network Unknown BitcoinNet (2400167808), got Unknown BitcoinNet (1087308554)
Hmm, weird. I'm pretty sure I tested this specifically against bitcoind
. What version are you using? Perhaps something changed recently?
@guggero
bitcoin-rpc:$ lnd --version lnd version 0.17.3-beta commit=v0.17.3-beta bitcoin-rpc:$ bitcoind --version Bitcoin Core version v25.1.0
Working conf files:
https://gist.github.com/pinheadmz/6b7393b61f7b19e1c5bc02219f5c7712
Background
When trying to setup a custom signet and providing custom signetchallenge parameter in lnd.conf results in LND process termination
Your environment
Steps to reproduce
Setup a custom signet in bitcoind Add correct signetchallenge into lnd.conf in my case that is: bitcoin.signetchallenge=512102ee856c56a5aaadd1656f849bafa4c9dacc86a2878fe546c6189185f842ae2c1851ae
Expected behaviour
I expected this to properly validate that I was connected to proper custom signet network
Actual behaviour
lnd terminates with: [ERR] LTND: unable to create chain control: expected network Unknown BitcoinNet (1034399232), got Unknown BitcoinNet (1087308554)
I found that if I simply do not provide any bitcoin.signetchallenge it will sync to the custom signet without issues, but this was unexpected based on how I read the lnd.conf documentation.