ln node might only know about 1 side of channel #410
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pinheadmz
reviewed
Jul 16, 2024
pinheadmz
reviewed
Jul 16, 2024
pinheadmz
reviewed
Jul 16, 2024
m3dwards
force-pushed
the
cln-needs-a-full-channel
branch
from
95ff838 to
d4f37ca
Compare
Collaborator
Author
|
Ready for review @pinheadmz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because gossip for both sides of a channel doesn't arrive at the same time, nodes might not always be able to build a full picture of a channel. For the sake of comparison, if two nodes both do not know about the policy of one side of a channel we consider them to be in sync with each other.