Create rapid gossip sync blog post #160
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
✅ Deploy Preview for lightningdevkit ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
haleyberkoe
reviewed
Aug 30, 2022
arik-so
reviewed
Aug 30, 2022
|
|
||
| Before we delve too deeply into the optimizations that Rapid Gossip Sync relies on, first a primer on how gossip works today. It involves three main message types: channel announcements, channel updates, and node announcements. (The last of which isn’t really relevant to this post.) | ||
|
|
||
| As their names imply, channel announcements are sent when a public channel opens, and updates when changes are made to a channel. One peculiar characteristic of channels is that they aren't symmetrical: depending on the direction, some of their properties may vary. For instance, if Alice and Bob have a channel, Alice may charge higher fees for forwarding payments to Bob than vice versa, thus requiring that different channel updates be broadcast to the network for each direction. Just as balances may concentrate on one side, routing fees for forwarding payments through the channel are set by different parties depending on the direction. Unlike channel updates, channel announcements do not carry directional information, meaning opening a new channel requires sending at least two channel updates for direction-specific data. |
There was a problem hiding this comment.
thus requiring that different channel updates be broadcast to the network for each direction, because channel announcements cannot contain directional data.
There was a problem hiding this comment.
let me edit that on Google. I am just now noticing that this information is conveyed a bit late in that paragraph.
haleyberkoe
reviewed
Aug 30, 2022
haleyberkoe
reviewed
Aug 30, 2022
|
|
||
| One of the noteworthy properties of gossip is that a lot of data is duplicated across messages. For example, each channel announcement and update contains the genesis block hash. Similarly, each channel announcement contains both nodes’ public keys, exacerbating data redundancy for well-connected nodes. So, to reduce bandwidth requirements, we decided to see if we could strip data to create a more efficient way of conveying the same information. | ||
|
|
||
| In the next few paragraphs, we'll outline a selection of the various improvements/optimizations we came up with. |
There was a problem hiding this comment.
Suggested change
| In the next few paragraphs, we'll outline a selection of the various improvements/optimizations we came up with. | |
| In the next few paragraphs, we'll outline a selection of the various optimizations we came up with. |
haleyberkoe
reviewed
Aug 30, 2022
Co-authored-by: Haley Berkoe <94868372+haleyberkoe@users.noreply.github.com>
Co-authored-by: Haley Berkoe <94868372+haleyberkoe@users.noreply.github.com>
Co-authored-by: Haley Berkoe <94868372+haleyberkoe@users.noreply.github.com>
haleyberkoe
reviewed
Aug 30, 2022
haleyberkoe
reviewed
Aug 30, 2022
Co-authored-by: Haley Berkoe <94868372+haleyberkoe@users.noreply.github.com>
Co-authored-by: Haley Berkoe <94868372+haleyberkoe@users.noreply.github.com>
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.
Preview