-
Notifications
You must be signed in to change notification settings - Fork 667
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
Pass the correct burnchain tip to run_sign_v0 instead of the block election snapshot #5307
base: develop
Are you sure you want to change the base?
Conversation
Signed-off-by: Jacinta Ferrant <[email protected]>
… into fix/tenure-extend-burnchain-tip-check
…b.com/stacks-network/stacks-core into fix/tenure-extend-burnchain-tip-check
Signed-off-by: Jacinta Ferrant <[email protected]>
…lock snapshot Signed-off-by: Jacinta Ferrant <[email protected]>
… into fix/tenure-extend-burnchain-tip-check
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 makes sense, LGTM!
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.
This looks great! Just noticed one misleading comment.
Signed-off-by: Jacinta Ferrant <[email protected]>
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
Tenure extends were not being properly handled as the burnchain tip was not actually being passed through the run_sign_v0 function. Rather it was using the block election snapshot because block.header.consensus_hash is the consensus hash of the election snapshot.