This release contains 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.4.x.x.x.
The version of stacks-node compatible with this release is 3.4.0.0.3, available here: https://github.com/stacks-network/stacks-core/releases/tag/3.4.0.0.3.
This release is recommended for all Stacks node operators.
This release includes the following changes:
https://github.com/stacks-network/stacks-core/blob/signer-3.4.0.0.3.0/stacks-signer/CHANGELOG.md
Added
- Added the
block_proposal_max_tx_execution_time_secsconnection option (defaulting to 30 seconds), which caps the time a single transaction is allowed to run during block proposal validation. A transaction that exceeds this per-transaction cap on its own is reported as aProblematicTransaction. If the overall block proposal validation budget (block_proposal_validation_timeout_secs) is exhausted before a transaction is processed, the block is rejected withInvalidBlockand no specific transaction is flagged, so a transaction is no longer marked problematic just because earlier transactions consumed the validation budget.
Docker images have been published to GitHub Container Registry:
stacks-signer
- Debian (glibc): https://github.com/stacks-network/stacks-signer/pkgs/container/stacks-signer/885352180?tag=3.4.0.0.3.0
docker pull ghcr.io/stacks-network/stacks-signer:3.4.0.0.3.0@sha256:483055ccc4555935e945d50a89242310832f8c4d977a05452b33b0921a914c3f- Alpine (musl): https://github.com/stacks-network/stacks-signer/pkgs/container/stacks-signer/885352452?tag=3.4.0.0.3.0-alpine
docker pull ghcr.io/stacks-network/stacks-signer:3.4.0.0.3.0-alpine@sha256:9d21f1d1c568e252685e7a29f5d47a6613ea54c810cf161cafb15d262b48a0ed