Skip to content

Expand on RGS caching requirements #3421

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 25, 2024
Merged

Expand on RGS caching requirements #3421

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions lightning-rapid-gossip-sync/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ request from the server instance. The methods `sync_network_graph_with_file_path
`update_network_graph_no_std` all return a `Result<u32, GraphSyncError>`, and that `u32` success value
is the timestamp meant to be used for the next server request.

Note that running those methods also updates the timestamp stored in the `NetworkGraph` object, whence it can be easily
retrieved by calling `get_last_rapid_gossip_sync_timestamp`, so using RGS does not impose any additional caching
requirements beyond those already used for storing the network graph.

## Mechanism

The (presumed) server sends a compressed gossip response containing gossip data. The gossip data is
Expand Down
Loading