Skip to content
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

Reliability improvements: require anchor block to have maximum BTC weight #2625

Closed
jcnelson opened this issue Apr 26, 2021 · 0 comments
Closed
Assignees
Labels
consensus-critical ship now This is a blocker for the next release (either non-breaking or breaking change) stacks-2.1

Comments

@jcnelson
Copy link
Member

As part of fully addressing #1805, we'll update the consensus rules in Stacks 2.1 to require that the PoX anchor block must also be the anchor block candidate that has been confirmed by the most BTC spent in the prepare phase. This change allows clients to always identify PoX anchor blocks without processing Stacks chain state (i.e. clients that don't process Stacks chain state won't get any false positives by making this assumption).

@jcnelson jcnelson self-assigned this Apr 26, 2021
@project-bot project-bot bot added this to New Issues in Stacks Blockchain Board Apr 26, 2021
@jcnelson jcnelson removed their assignment Apr 26, 2021
@jcnelson jcnelson added this to To do in Stacks 2.1 May 17, 2021
@jcnelson jcnelson self-assigned this Aug 3, 2022
@jcnelson jcnelson added the ship now This is a blocker for the next release (either non-breaking or breaking change) label Nov 7, 2022
@jcnelson jcnelson mentioned this issue Nov 16, 2022
@jcnelson jcnelson moved this from To do to Review in progress in Stacks 2.1 Nov 16, 2022
Stacks Blockchain Board automation moved this from New Issues to Done Nov 28, 2022
Stacks 2.1 automation moved this from Review in progress to Done Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consensus-critical ship now This is a blocker for the next release (either non-breaking or breaking change) stacks-2.1
Development

No branches or pull requests

1 participant