Release 3.3.0.0.5

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.3.0.0.5.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.3.0.0.5.0.

Added

• New endpoint /v3/blocks/simulate/{block_id} allows to simulate the execution of a specific block with a brand new set of transactions
• Improved block validation in stacks-inspect.

Fixed

• Correct calculation of burn-view change status using the new tip with metadata endpoint.

Changed

• Removed validate-naka-block option in stacks-inspect, merging it with validate-block so that users do not need to differentiate between the two.

Release signer-3.3.0.0.5.0

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

Changed

• Reduced default tenure-extend idle timer from 120 seconds to 60 seconds

Release 3.3.0.0.4

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.3.0.0.4.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.3.0.0.4.0.

Added

• New /v3/tenures/tip_metadata endpoint for returning some metadata along with the normal tenure tip information.

Fixed

• Correct calculation of burn-view change status using the new tip with metadata endpoint.

Release signer-3.3.0.0.4.0

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

Added

• New /v3/tenures/tip_metadata endpoint for returning some metadata along with the normal tenure tip information.

Fixed

• Correct calculation of burn-view change status using the new tip with metadata endpoint.

Release 3.3.0.0.3

This release contains several minor improvements to the stacks-node and is fully compatible with existing chainstate.

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

Added

• In the /v3/transaction/{txid} RPC endpoint, added block_height and is_canonical to the response.

Release signer-3.3.0.0.3.0

This release contains several minor improvements to the stacks-node and is fully compatible with existing chainstate.

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

Release 3.3.0.0.2

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.3.0.0.2.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.3.0.0.2.0.

Note: For users running both stacks-node and stacks-signer binaries, ensure that both are upgraded and that the stacks-node service is upgraded before the stacks-signer service.

Release signer-3.3.0.0.2.0

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

Note: For users running both stacks-node and stacks-signer binaries, ensure that both are upgraded and that the stacks-node service is upgraded before the stacks-signer service.

Release 3.3.0.0.1

This release improves stacks-core performance by adding two database indexes which significantly reduce disk reads.
Depending on your hardware, index creation takes between 2-15 minutes per index (there are two).

We strongly recommend all signer operators to manually create indexes before applying this upgrade to avoid any downtime.

Apply the indexes as follows:
Note:

• The following commands require running from your config working_dir directory. ex: cd /stacks where working_dir = "/stacks"
• You may need to install the sqlite binary. On Debian based systems: sudo apt-get install sqlite3

$ echo "CREATE INDEX IF NOT EXISTS naka_block_headers_by_burn_hash ON nakamoto_block_headers(burn_header_hash);" | sqlite3 ./mainnet/chainstate/vm/index.sqlite

$ echo "CREATE INDEX IF NOT EXISTS naka_block_headers_by_burn_ht ON nakamoto_block_headers(burn_header_height);" | sqlite3 ./mainnet/chainstate/vm/index.sqlite

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.1.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.3.0.0.1.0.

Added

• Add indexes to nakamoto_block_headers to fix a performance regression. Node may take a few minutes to restart during the upgrade while the new indexes are created.

Release signer-3.3.0.0.1.0

This release improves stacks-core performance by adding two database indexes which significantly reduce disk reads.
Depending on your hardware, index creation takes between 2-15 minutes per index (there are two).

We strongly recommend all signer operators to manually create indexes before applying this upgrade to avoid any downtime.

Apply the indexes as follows:
Note:

• The following commands require running from your config working_dir directory. ex: cd /stacks where working_dir = "/stacks"
• You may need to install the sqlite binary. On Debian based systems: sudo apt-get install sqlite3

$ echo "CREATE INDEX IF NOT EXISTS naka_block_headers_by_burn_hash ON nakamoto_block_headers(burn_header_hash);" | sqlite3 ./mainnet/chainstate/vm/index.sqlite

$ echo "CREATE INDEX IF NOT EXISTS naka_block_headers_by_burn_ht ON nakamoto_block_headers(burn_header_height);" | sqlite3 ./mainnet/chainstate/vm/index.sqlite

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

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