stacks-network/stacks-core signer-3.3.0.0.6.0

Release signer-3.3.0.0.6.0

on GitHub

This release contains several bugfixes and improvements to the stacks-node and stacks-signer binaries, ensuring more consistent block production.
This release is compatible with chainstate directories from 3.3.x.x.x.

The version of stacks-node compatible with this release is 3.3.0.0.6, available at: https://github.com/stacks-network/stacks-core/releases/tag/3.3.0.0.6.

Notes:
Due to the changes in this release, if a node operator is running both stacks-node and stacks-signer binaries, updating either of them will require updating both of them.

Starting from this release, docker images shall be published by default to the ghcr registry using the format ghcr.io/stacks-network/stacks-signer:tag. The existing dockerhub repository will remain as a mirror.

Added

• Add support for tracking pending block responses for up to 3 unique untracked blocks per signer address. This improves handling of late block proposals by allowing the signer to process previously seen responses for blocks that were not being tracked.
• Added approved_time column to the blocks database table

Changed

• Database schema updated to version 19
• Removed signed_over column from the blocks database table
• Improved signer behaviour to ensure block proposal responses are sent more consistently, even for blocks that have already been globally accepted by the network. This increases reliability and reduces missed responses in edge cases.