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.
Description
Add a few fixes and improvement to be released as 2.2.1
The publish_stacking_order formula wasn't working on some edge case
The new formula is slightly simpler (still a bit complicated but well..) and it works in all cases
Handle the
reward_cycle_length
property in PoxInfo and revert the regression onreward_phase_block_length
In the devnet UI, avoid multiple
>
in case a nakamoto block is mined at the same block height as the beginning of a new pox cycle (eg – [12]> – [11]> – <[10] –
)use a fixed tag for the
hirosystems/stacks-blockchain-api
docker image (because:nakamoto
is updated frequently)