Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REF: lnd major bug reported #7002 (affecting all nodes) - Unable to deserialize block: readScript: script witness item is larger than the max allowed size [count 33970, max 11000]` #702

Closed
LightningLuke opened this issue Oct 10, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@LightningLuke
Copy link

LightningLuke commented Oct 10, 2022

Describe the bug
2022-10-09 16:04:09.544 [ERR] LNWL: Unable to deserialize block: readScript: script witness item is larger than the max allowed size [count 33970, max 11000]

Here's the link to the bug reported over on lnd. ALL 100% of nodes are affected and we'll need an update from myNode once btcd, and lnd have patches out.
#7002 over on lnd

Expected behavior
Will need myNode to make an update available asap

@LightningLuke LightningLuke added the bug Something isn't working label Oct 10, 2022
@otech47
Copy link

otech47 commented Oct 10, 2022

patches for

BTCD: btcsuite/btcd#1896
LND: lightningnetwork/lnd#7004

currently in review

@0xEDD1E5
Copy link

My node is affected. Do I need to stop my node and wait for the fix? What is the best way to handle this?

@LightningLuke
Copy link
Author

totally fine to leave your node running..... lightning just won't be able to sync to chain until you apply the necessary update they release. I see there is a PR fix available and Roasbeef said "we'll be cherry picking this PR onto a new 0.15.2 release (branched off from 0.15.1) which'll backport the fix."

Just not sure if that means we can upgrade to 0.15.1 if on a previous version and that will apply the fix or not...?

@otech47
Copy link

otech47 commented Oct 10, 2022

probably best to leave node online and wait for a fix, then update ASAP

your node will be out of sync with the chaintip until then but risk seems low at the moment... worst case you will have to reopen channels

@LightningLuke
Copy link
Author

closing this now....just upgrade to latest myNode release and you're good to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants