-
Notifications
You must be signed in to change notification settings - Fork 5
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
MTG-750 Calculating bubblegum and account checksums #291
base: main
Are you sure you want to change the base?
Conversation
0c84d5c
to
ba9fa93
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Only one small question at the moment
hasher = Hasher::default(); | ||
} | ||
hasher.hash(&k); | ||
hasher.hash(&v); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we save value as well? Why not only key or value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@n00m4d
I assume that theoretically (not sure how high the probability is) we might have a situation, when on different peers there are bubblegum changes with same pubkey+slot+seq, but different signatures.
It you believe that this is impossible, then I can remove the signature from the bubblegum change entity (and from the hashing).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm, not sure either. Ok let's leave it for now 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh and also while was looking at fork cleaner got a thought that maybe we should sync with sequence consistency checker before calculating epoch hash, not to calculate epoch hash if we have gaps in tree sequences.
f3636c6
to
b504cad
Compare
b504cad
to
23cb90a
Compare
7cd234a
to
8595abb
Compare
This is a preliminary code review that doesn't intend to be me merged into the main branch, but aims to reveal problems before the development in completed.
In scope of review, I would like to present:
See the technical design:
https://github.com/adm-metaex/doc/wiki/Data-consistency-for-peer%E2%80%90to%E2%80%90peer-indexers