-
Notifications
You must be signed in to change notification settings - Fork 409
RGS Update had same timestamp as last processed update
shouldn't be an error
#1746
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
Comments
I will take this up, Doubt: If we remove this check, we might apply and broadcast a few duplicate gossips. (non-rgs case) Concern is when we receive same msg from multiple nodes. |
The timestamp here is the one set by the RGS server (roughly "when the snapshot was generated"), not one connected to network messages themselves, so there's no relevant BOLT requirements here. |
See lightningdevkit/rapid-gossip-sync-server#17 but this just shouldn't be an error, we should probably try to apply anyway, though.
The text was updated successfully, but these errors were encountered: