Releases: stacks-network/stacks-core
Releases · stacks-network/stacks-core
Release 2.0.11.1.0-rc2
Merge pull request #2670 from blockstack/fix/2667 Fix/2667
Release 2.0.11.1.0-rc1
Merge pull request #2631 from friedger/fix/docs_map Update documentation of define-map
Release 2.0.11.0.0
The chainstate directory has been restructured in this release. It is not compatible with prior chainstate directories. Therefore, if you are upgrading from 2.0.10.x.x or earlier versions of stacks-node
, you will need to resync from a fresh chainstate.
Added
/drop_mempool_tx
endpoint to notify event observers when a mempool
transaction has been removed the mempool."reward_slot_holders"
field to thenew_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). - Re-activate the Atlas network for propagating and storing transaction
attachments. This re-enables off-chain BNS name storage. - Re-activate microblock mining.
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.
Release 2.0.11.0.0-rc5
Merge pull request #2590 from blockstack/fix/atlas-replication-retry Fix/atlas replication retry
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 thenew_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