stacks-network/stacks-core 3.3.0.0.6

Release 3.3.0.0.6

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-signer compatible with this release is 3.3.0.0.6.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.3.0.0.6.0.

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-core:tag. The existing dockerhub repository will remain as a mirror.

Added

• Setup for epoch 3.4 and Clarity version 5. Epoch 3.4 is currently set to activate at Bitcoin height 3,400,000 (very far in the future) until an activation height is selected. Clarity will activate with epoch 3.4.
• Implemented the updated behavior for secp256r1-verify, effective in Clarity 5, in which the message-hash is no longer hashed again. See SIP-035 for details.
• Increased allowed stack depth from 64 to 128, effective in epoch 3.4
• Prepare for epoch 3.4's improved transaction inclusion, allowing transactions with certain errors to be included in blocks which would cause them to be rejected in earlier epochs.
• Added marf_compress as a node configuration parameter to enable MARF compression feature (#6811)
• Effective in epoch 3.4 contract-call?s can accept a constant as the contract to be called

Fixed

• Improved the cost-tracking for from-consensus-buff?, effective in epoch 3.4, so that when an empty buffer is passed, users will see a none result, rather than a confusing runtime error.
• Resolved several cases where a mock-miner would stop mining
• /v2/pox endpoint now returns the pox_ustx_threshold stored in the reward set instead of a live computed value, which incorrectly accounts for STX locked during the prepare phase, after the reward set has been set.
• Signer protocol version negotiation now properly handles downgrades based on majority consensus, not just upgrades
• The sortition DB now tracks canonical Stacks tip by its burn view, allowing it to recover from a chain freeze if the Bitcoin block upon which the ongoing tenure is based is orphened before the last tenure block is processed.