-
Notifications
You must be signed in to change notification settings - Fork 11k
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
Remove consensus hash #17709
base: main
Are you sure you want to change the base?
Remove consensus hash #17709
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
…mit prologue contains the consensus commit hash
4cdeed8
to
90d78eb
Compare
@@ -231,7 +241,6 @@ impl ConsensusStatsAPI for ConsensusStatsV1 { | |||
#[derive(Serialize, Deserialize, Clone, Debug, Default, PartialEq, Eq)] | |||
pub struct ExecutionIndicesWithStats { | |||
pub index: ExecutionIndices, | |||
pub hash: u64, |
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.
Should we keep this for db compatibility as well?
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.
ah, didn't notice they were both in the db
Right now the checkpoint fork message does not give very clear indication of which consensus subdag has the fork. We actually just used this log message to debug a crash recovery issue. Maybe wait a bit until we have better logging inside consensus for forks? |
sounds good! |
Apart from the enhanced logging I would suggest for us to implement the consensus_digest for Mysticeti before we remove the hash anyways. I just realised actually that we never did. |
The sui-side hash is no longer necessary now that the commit prologue contains the consensus commit hash. If consensus forks, we will immediately observe a checkpoint fork.