github stacks-network/stacks-core 3.1.0.0.2
Release 3.1.0.0.2

latest release: signer-3.1.0.0.2.0
one day ago

This release introduces all necessary code changes for SIP-029, as well as tenure-extend to happen which enables miners and signers to tenure-extend every 5 minutes (on average).
This release is compatible with chainstate directories from 3.x.x.x.x.

** All node operators are required to upgrade to this release since it also contains the 3.1 hard fork defined in SIP-029. **
** Epoch 3.1 is set to activate at Bitcoin block 875_000, around Mon Dec 16 2024 08:47:39 GMT. **
** Failing to upgrade prior to Bitcoin block 875_000 will require a genesis sync. **

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

Added

  • SIP-029 consensus rules, activating in epoch 3.1 at block 875,000 (see SIP-029 for details)
  • New RPC endpoints
  • /v2/clarity/marf/:marf_key_hash
  • /v2/clarity/metadata/:principal/:contract_name/:clarity_metadata_key
  • When a proposed block is validated by a node, the block can be validated even when the block version is different than the node's default (#5539)
  • A miner will now generate a tenure-extend when at least 70% of the signers have confirmed that they are willing to allow one, via the new timestamp included in block responses. This allows the miner to refresh its budget in between Bitcoin blocks. (#5476)
  • Set the epoch to 3.1 in the Clarity DB upon activation.

Changed

  • Added tenure extend timestamp to signer block responses
  • Added tenure_idle_timeout_secs configuration option for determining when a time-based tenure extend will be accepted

What's Changed

Full Changelog: 3.1.0.0.0...3.1.0.0.2

What's Changed

Full Changelog: 3.1.0.0.0...3.1.0.0.2

What's Changed

Full Changelog: 3.1.0.0.0...3.1.0.0.2

Don't miss a new stacks-core release

NewReleases is sending notifications on new releases.