Release 2.0.11.0.0-rc4

Merge branch 'master' into develop

Release 2.0.10.0.1

This is a high-priority hotfix release to address a bug in the deserialization logic. The chainstate directory of 2.0.10.0.1 is compatible with 2.0.10. This release also begins the usage of the versioning scheme outlined in the README.md.

Release 2.0.11-rc2

Merge pull request #2570 from blockstack/fix/book-deadlock

Boot looping

Release fix-2407-net

on second thought, bound the depth of the anti-entropy protocol to wh…

Release feat-light-pox-scan

feat: do light versus full inventory rescans in pox syncs

Release 2.0.11-rc1

[2.0.11-rc1]

The chainstate directory has been restructured in this release. It is not
compatible with prior chainstate directories.

Added

• /drop_mempool_tx endpoint to notify event observers when a mempool
  transaction has been removed the mempool.
• "reward_slot_holders" field to the new_burn_block event
• CTRL-C handler for safe shutdown of stacks-node
• Log transactions in local db table via setting env STACKS_TRANSACTION_LOG=1
• New prometheus metrics for mempool transaction processing times and
  outstanding mempool transactions
• New RPC endpoint with path v2/traits/contractAddr/contractName/traitContractName /traitContractAddr/traitName to determine whether a given trait is implemented
  within the specified contract (either explicitly or implicitly).

Changed

• Improved chainstate directory layout
• Improved node boot up time
• Better handling of flash blocks
• The /v2/pox RPC endpoint was updated to include more useful
  information about the current and next PoX cycles. For details, see
  docs/rpc-endpoints.md

Fixed

• Fixed faulty logic in the mempool that was still treating the transaction fee
  as a fee rate, which prevented replace-by-fee from working as expected.
• Restored Atlas attachment support
• Fixed microblock miner overcommitment

Release 2.0.11-rc3

Merge pull request #2524 from blockstack/hotfix/2518+2491

Hotfix patch for Fix/2518+2491

Release 2.0.10

This is a low-priority hotfix release to address two bugs in the block downloader. The chainstate directory of 2.0.10 is compatible with 2.0.9. If booting up a node from genesis, or an existing node has stalled in downloading blocks, this hotfix is necessary for your node.

Fixed

• Bug in microblocks inventory vector calculation that included invalidated microblocks as present bit. This bug will impact nodes booting up from genesis, but not affect nodes currently running at the chain tip (#2518).
• Bug in microblocks downloader logic that would cause the stacks-node to fail to wake-up to process newly arrived microblocks in certain instances (#2491).

Release 2.0.9

This is a low-priority hotfix release that patches a TOCTTOU bug in how the node handles blocks uploaded to it by 3rd parties, which if executed may lead to a denial-of-service (node crash) in the node while it is bootstrapping. People who run public nodes should upgrade to this release on their next node restart. Private nodes, such as those running behind a NAT or are otherwise unreachable from the Internet, are not affected.

Release 2.0.8

Upgrade priority: high for miners; medium for everyone else.

This hotfix repairs a denial-of-service vulnerability in the way the Stacks node processes smart contracts. A buggy or malicious smart contract transaction can cause the node to crash while processing it. Node operators should upgrade to this release as soon as possible.

If your node crashes due to this bug, you will need to restart with a new working directory. The denial-of-service bug, if executed, will corrupt the chainstate database. If you restart your node yourself, then you do not need to re-sync.

---

This is a hotfix release for improved handling of static analysis storage and
improved at-block behavior. The chainstate directory of 2.0.8 is compatible with
the 2.0.7 chainstate.

Fixed

• Improved static analysis storage
• at-block behavior in clarity-cli and unit tests (no changes in stacks-node
  behavior).