-
Notifications
You must be signed in to change notification settings - Fork 385
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
Skip channel_update
signature checks if we have a newer state
#1380
Skip channel_update
signature checks if we have a newer state
#1380
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1380 +/- ##
==========================================
+ Coverage 90.81% 90.94% +0.13%
==========================================
Files 73 73
Lines 41187 42311 +1124
Branches 41187 42311 +1124
==========================================
+ Hits 37402 38480 +1078
- Misses 3785 3831 +46
Continue to review full report at Codecov.
|
9a1e989
to
7819cbd
Compare
`channel_update` messages already have their signatures checked with the network graph write lock held, so there's no reason to check the signatures before doing other quicker checks first, including checking if we're already aware of a newer update for the channel. This reduces common-case CPU usage as `channel_update`s are sent rather liberally over the p2p network to gossip them.
15a036a
to
63ca72e
Compare
Squashed without changes. |
channel_update
messages already have their signatures checkedwith the network graph write lock held, so there's no reason to
check the signatures before doing other quicker checks first,
including checking if we're already aware of a newer update for the
channel.
This reduces common-case CPU usage as
channel_update
s are sentrather liberally over the p2p network to gossip them.