Release 2.4.0.0.0

This is a consensus-breaking release to revert consensus to PoX, and is the second fork proposed in SIP-022.

• SIP-022
• SIP-024

Fixed

• PoX is re-enabled and stacking resumes starting at Bitcoin block 791551
• Peer network id is updated to 0x18000009
• Adds the type sanitization described in SIP-024

This release is compatible with chainstate directories from 2.1.0.0.x and 2.3.0.0.x

Release 2.3.0.0.2

This is a high-priority hotfix release to address a bug in the stacks-node miner logic which could impact miner availability.

This release is compatible with chainstate directories from 2.3.0.0.x and 2.1.0.0.x

Release 2.3.0.0.1

chore: updating changelog

Release 2.3.0.0.0

2.3.0.0.0
Tx and read-only calls to functions with traits as parameters are rejected with unchecked TypeValueError.
Additional context and rationale can be found in SIP-023.

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

Release 2.2.0.0.1

2.2.0.0.1

This is a consensus-breaking release to address a bug and DoS vector in pox-2's stack-increase function. Additional context and rationale can be found in SIP-022.

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

Upgrade timing estimate: https://stacks-network.github.io/when-rewards/2.2/

Release 2.1.0.0.3

fix: neon_node unprocessed_block behavior

Release 2.1.0.0.2

This software update is a hotfix to resolve improper unlock handling in mempool admission. This release's chainstate directory is compatible with chainstate directories from 2.1.0.0.1.

Fixed

• Fix mempool admission logic's improper handling of PoX unlocks. This would cause users to get spurious NotEnoughFunds rejections when trying to submit their transactions (#3623)

Release 2.1.0.0.1

This release is a hotfix for various stacks-node behavior in 2.1.0.0.0. This version is compatible with 2.1.0.0.0 chainstate directories, so it does not require a resync to upgrade from 2.1.0.0.0.

Fixed

• Fix crash related to mempool bloom filter processing
• Handle the case where a bitcoin node returns zero headers (#3588)
• The default value for always_use_affirmation_maps is now set to false,
  instead of true. This was preventing testnet nodes from reaching the chain
  tip with the default configuration.
• Reduce default poll time of the chain-liveness thread which reduces the
  possibility that a miner thread will get interrupted (#3610).

Release 2.1.0.0.0

Merge pull request #3567 from stacks-network/develop

Stacks 2.1

Release 2.1.0.0.0-rc4

Merge pull request #3517 from stacks-network/btc-tx-more-info

Event observer: additional info for burn operations