This hotfix release fixes a problem where previous reward cycle signers were trying to process block validation response messages that do not apply to the current cycle.
This release is compatible with chainstate directories from 3.x.x.x.x.
All signers are strongly encouraged to upgrade to this hotfix release as soon as possible
This version of the stacks-signer compatible the stacks-node release 3.1.0.0.2, available at: https://github.com/stacks-network/stacks-core/releases/tag/3.1.0.0.2.
What's Changed
- Prevent old reward cycle signers from processing block validation response messages that do not apply to blocks from their cycle.
Full Changelog: release/signer-3.1.0.0.2.0...release/signer-3.1.0.0.2.1
What's Changed
- Adding changelog for 3.1.0.0.2.x by @wileyj in #5571
- merge Release/3.1.0.0.2 to master by @wileyj in #5572
- fix: set epoch to 3.1 in Clarity DB by @obycode in #5561
- Do not process block validation responses for the wrong reward cycle by @jferrant in #5612
Full Changelog: signer-3.1.0.0.2.0...signer-3.1.0.0.2.1