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
Remove ErrSynchronizingChain #7039
Conversation
@Crypt-iQ: review reminder |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR! Could you rebase it? We've added several new linters rules and new itests, kinda wanna see if they'd be affected.
4ddc773
to
5bc7969
Compare
Rebased. Let me know if there's any errors to fix. I noticed the CI hasn't been healthy for awhile so I can't tell if there's something I need to fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool missing a release note, and the git commit message needs to be changed according to the contribution guidelines, otherwise LGTM👍
5bc7969
to
0953759
Compare
I think that should do it, let me know if the release note comment should be any different. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM🙏
// ErrChanTooLarge is returned by a remote peer that receives a | ||
// FundingOpen request for a channel that is above their current | ||
// soft-limit. | ||
ErrChanTooLarge FundingError = 3 | ||
ErrChanTooLarge FundingError = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Crypt-iQ so even though this is declared in the lnwire
package, this constant is never used on the wire? So changing the number shouldn't have any side effects? I guess we only created the type for internal handling then...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes its not used on the wire
Change Description
This fixes #7034 where an LND node reveals that is it vulnerable to chain tip sync problems such as #7002, which may be exploited by those with existing channels with the node by broadcasting a previous channel state. It would be better if other actors do not know if a node is synced or not.
Steps to Test
funding failed due to internal error
)