[feature]: lnrpc.ChannelGraphRequest: Introducing iterative query parameters. #7895
Description
At the moment, it's not possible to reduce the graph through the lnrpc.ChannelGraphRequest. This means that the responses keep getting larger, and for evaluations of the graph, one always has to parse all the nodes and edges.
We can introduce a new optional parameter: --min_last_update: Both lnrpc.LightningNode and lnrpc.ChannelEdge have a last_update field. It would make sense to filter based on that
It would allow for iterative querying of the graph, similar to Payments and Forwards. Additionally, the current maximum last_update should then also be included in lnrpc.ChannelGraph.
Does this make sense? I can't gauge how stable last_update is. Could it happen that after a request, changes are added to the graph that get a last_update which is less than the current maximum?
Edit: For iterative querying we should also introduce --max_last_update
Edit2: I also observed data garbage: last_update in 2030.