Closed buck54321 closed 9 months ago
Nothing notable logged for the client.
How about neutrino.log?
Nothing notable logged for the client.
How about neutrino.log?
Bingo. Thanks. Still don't know how it would get to this state.
2023-03-25 09:24:24.928 [WRN] NTRNO: Header doesn't pass sanity check: block target difficulty of 7fffff0000000000000000000000000000000000000000000000000000000000 is higher than max of 1fffff0000000000000000000000000000000000000000000000000000000000 -- disconnecting peer
2023-03-25 09:24:24.929 [DBG] NTRNO: Removed peer 127.0.0.1:20575 (outbound)
Still don't know how it would get to this state.
No clue. https://github.com/lightningnetwork/lnd/issues/6938#issuecomment-1263925295 https://github.com/lightninglabs/neutrino/issues/211
Based on the linked issues with ln, maybe not something we're doing wrong. Can close?
Can close when we update btcd dep with the following merged: https://github.com/lightninglabs/neutrino/pull/256
Update. btcd fix is merged, in https://github.com/btcsuite/btcd/pull/1985. Then the neutrino fix that uses the newly exported btcd functions is in https://github.com/lightninglabs/neutrino/pull/283, which looks to be almost ready to merge. When that goes in, we can update both btcd and neutrino's requires to get this issue resolved.
Bitcoin native SPV connects by default to the simnet harness alpha node. Yesterday afternoon, I created a new wallet and had zero peers. Restarting the client did not fix it. Restarting the harness did fix it. Left client running overnight. This morning I see a notification that the wallet has no peers again.
Nothing notable logged for the client.
Alpha node logs
Log sequence repeats periodically. Connection is clearly made, information is exchanged apparently successfully. Then the connection is inexplicably dropped.