stacks-network/stacks-core 3.3.0.0.0

Release 3.3.0.0.0

on GitHub

This release implements the 3.3 Stacks consensus rules which activates at Bitcoin block 923,222. For more details see SIP-033.

This is a required upgrade

• Activation is estimated for November 11th, 2025 around 1600 UTC, or Bitcoin block 923,222.
• Upgrading after Bitcoin block 923,222 will require a genesis sync.

This release is compatible with chainstate directories from 3.x.x.x.x.

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

Added

• Added support for new Clarity 4 builtin, secp256r1-verify? (not activated until epoch 3.3)
• New block_proposal_validation_timeout_secs configuration option in the connection options section, allowing to set the maximum duration a node will spend validating a proposed block.
• Activation height selected and set for epoch 3.3 at Bitcoin block 923,222

Changed

• Renamed Clarity 4's new block-time to stacks-block-time
• Improve cost-tracking for type-checking function arguments in epoch 3.3 (see #6425)
• Replaced libsecp256k1 with k256 and p256 from RustCrypto and removed separate Wasm implementations.
• Added limits in the type-checker for the number of parameters in functions (maximum 256), and the number of methods in traits (maximum 256). These limits are enforced starting in Epoch 3.3.