Hi y'all, we're aware of the current issue affecting lnd nodes. We've identified the fix to btcd's wire parsing library, which'll be packaged in a hot fix release (v0.15.2) for lnd eminently
the PR fix is available for those that wish to apply directly:
Conversation
Replying to
so what happend?
the issue was in btcd's wire parsing library that deserializes raw blocks, the initial implementation of segwit v0 included a consensus level check for witness size limits but _also_ hoisted this check up to the wire parsing layer
2
3
38
with segwit v1, this prior limit of the max accepted witness size was removed, in place of things like the sigop cost abstraction, effectively leaving the limit to the max block weight/size
2
1
33
btcd's initial segwit v1 implementation correctly updated the consensus logic, but failed to also update the defense-in-depth check in the wire parsing layer (when parsing off the wire you want _some_ sort of upper limit)
4
1
28
the fix to btcd's wire parsing library can be found here: github.com/btcsuite/btcd/
those running btcd nodes can apply this patch (an official release is forthcoming) and their nodes will accept the block as expected, since this wasn't a consensus issue
5
2
28
how was lnd affected?
lnd uses this library to parse blocks we get from either the full node backend or p2p network, due to this bug lnd wasn't able to parse a new block, but was able to continue to forward as normal (synced_to_chain: false)
7
5
40
any rpc requests to open *new* channels were also rejected as lnd recognized that its internal wallet wasn't synced to the chain
2
1
12
Replying to
btcd back-ends v22 and v23 also affected regardless of older lnd version
about to try the PR that's there
3
