pull down to refresh

It only effects lnd nodes using btcd (a golang implementation) not bitcoin-core afaict. The changeset was confirmed to fix the problem and is available on master.
My node running LND with a Bitcoin core backend was affected. Upgrading to current release fixed the issue.
reply
No, it affects lnd nodes that uses bitcoind backend as well. The bug is in the transaction parser.
reply
looks like you can check your node with the "lncli getinfo" command line
reply
My node is effected and I'm using bitcoin-core, so this isn't isolated to btcd as the ticket alludes.
After uninstalling the default raspian verison of go, and manually installing go 1.18 as per lnd compile instructions, then compiling and installing LND v0.15.2-beta branch, my node is back up and running.
I'm afraid this procedure isn't for the passive noderunner and the lightning network is going to be crippled until a new lnd package is released.
reply
That's unfortunate, and yes, this is no walk in the park...
reply