Initialize peer stats with past events#3272
Merged
Conversation
t-bast
force-pushed
the
peer-scorer-load-payment-events
branch
3 times, most recently
from
647fa30 to
47d0835
Compare
We initialize peer statistics by reading past events from the `AuditDb`. We read events in chunks to avoid overloading the DB or the RAM. We only return peer statistics to callers once we've finished reading past data from the DB. Note that on-chain statistics need to be computed whenever statistics are requested, because they require merging data from two distincts events (transaction published and transaction confirmed), which requires keeping state between those events and thus requires the DB (because the node may restart after publishing a transaction and before it confirms).
t-bast
force-pushed
the
peer-scorer-load-payment-events
branch
from
47d0835 to
91ca4c3
Compare
pm47
reviewed
Mar 30, 2026
pm47
approved these changes
Mar 31, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We initialize peer statistics by reading past events from the
AuditDb. We read events in chunks to avoid overloading the DB or the RAM. We only return peer statistics to callers once we've finished reading past data from the DB.Note that on-chain statistics need to be computed whenever statistics are requested, because they require merging data from two distincts events (transaction published and transaction confirmed), which requires keeping state between those events and thus requires the DB (because the node may restart after publishing a transaction and before it confirms).