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

Add a rejection for update when channel is pruned #1378

Merged
merged 1 commit into from
Apr 15, 2020

Conversation

pm47
Copy link
Member

@pm47 pm47 commented Apr 15, 2020

In case a channel has been pruned, and we receive a recent update, we
"unprune" it and immediately request the channel announcement again
(which will cause us to revalidate it). We also discard the update,
assuming that we will receive it again with the channel announcement.

We were using a GossipDecision.Duplicate rejection for the channel
update, which is inaccurate. This PR introduces a new
GossipDecision.RelatedChannelPruned.

In case a channel has been pruned, and we receive a recent update, we
"unprune" it and immediately request the channel announcement again
(which will cause us to revalidate it). We also discard the update,
assuming that we will receive it again with the channel announcement.

We were using a `GossipDecision.Duplicate` rejection for the channel
update, which is inaccurate. This PR introduces a new
`GossipDecision.RelatedChannelPruned`.
@pm47 pm47 requested a review from t-bast April 15, 2020 14:53
Copy link
Member

@t-bast t-bast left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@pm47 pm47 merged commit 9103b99 into master Apr 15, 2020
@pm47 pm47 deleted the gossip-decision-pruned branch April 15, 2020 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants