This release contains several bugfixes and improvements in the stacks-node and stacks-signer binaries, ensuring more consistent block production.
Notably, there are several performance improvements in this release which improve block processing (sync) time considerably.
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.9.0, available at: https://github.com/stacks-network/stacks-core/releases/tag/signer-3.1.0.0.9.0.
Added
- Added field
vm_error
to EventObserver transaction outputs - Added new
ValidateRejectCode
values to the/v3/block_proposal
endpoint - Added
StateMachineUpdateContent::V1
to support a vector ofStacksTransaction
expected to be replayed in subsequent Stacks blocks - Include a reason string in the transaction receipt when a transaction is rolled back due to a post-condition. This should help users in understanding what went wrong.
Changed
- Reduce the default
block_rejection_timeout_steps
configuration so that miners will retry faster when blocks fail to reach 70% approved or 30% rejected. - Added index for
next_ready_nakamoto_block()
which improves block processing performance. - Added a new field,
parent_burn_block_hash
, to the payload that is included in the/new_burn_block
event observer payload.
Fixed
- Fix regression in mock-mining, allowing the mock miner to continue mining blocks throughout a tenure instead of failing after mining the tenure change block.