From 144340bf0fadd12dedab680b82d11b38374b7e7c Mon Sep 17 00:00:00 2001 From: Arik Sosman Date: Sat, 23 Nov 2024 11:33:16 -0500 Subject: [PATCH] Expand on RGS caching requirements --- lightning-rapid-gossip-sync/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/lightning-rapid-gossip-sync/README.md b/lightning-rapid-gossip-sync/README.md index 57df7caff69..e0a3512627e 100644 --- a/lightning-rapid-gossip-sync/README.md +++ b/lightning-rapid-gossip-sync/README.md @@ -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`, 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