stacks-network/stacks-core 3.1.0.0.13

Release 3.1.0.0.13

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.x.x.x.x.

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

Added

• Added a new RPC endpoint /v3/health to query the node's health status. The endpoint returns a 200 status code with relevant synchronization information (including the node's current Stacks tip height, the maximum Stacks tip height among its neighbors, and the difference between these two). A user can use the difference_from_max_peer value to decide what is a good threshold for them before considering the node out of sync. The endpoint returns a 500 status code if the query cannot retrieve viable data.
  - Improve prometheus metrics to gain more insights into the current state of the mempool
  - stacks_node_miner_stop_reason_total: Counts the number of times the miner stopped mining due to various reasons.
• Always report the number of transactions mined in the last attempt, even if there were 0
• Added a new option --hex-file <file_path> to blockstack-cli contract-call command, that allows to pass a serialized Clarity value by file.
• Added a new option --postcondition-mode [allow, deny] to blockstack-cli publish command, to set the post-condition mode to allow or deny on the transaction (default is deny)

Changed

• Changed default mempool walk strategy to NextNonceWithHighestFeeRate

Fixed

• Fixed an issue that prevented the correct usage of anchor mode options (--microblock-only, --block-only) when using blockstack-cli publish command.
• Fix several bugs in the mock-miner that caused it to fail to mine blocks in certain conditions