Releases: stacks-network/stacks-core
Releases · stacks-network/stacks-core
Release 2.05.0.1.0-rc2
Merge pull request #3005 from blockstack/fix/pox-valid-index fix: significantly increase the speed of most RPC endpoints
Release 2.05.0.1.0-pre-release
Merge pull request #2998 from blockstack/fix/cost-dir fix: Create a separate directory for `estimates` tables
Release 2.05.0.1.0-rc0
Merge pull request #2972 from blockstack/feat/hook-up-estimator feat: Improved Fee Rate Computation
Release 2.05.0.0.0
This software update is a consensus changing release and the implementation of the proposed cost changes in SIP-012. This release's chainstate directory is compatible with chainstate directories from 2.0.11.4.0. However, this release is only compatible with chainstate directories before the 2.05 consensus changes activate (Bitcoin height 713,000). If you run a 2.00 stacks-node beyond this point, and wish to run a 2.05 node afterwards, you must start from a new chainstate directory.
Added
- At height 713,000 a new
costs-2
contract will be launched by the Stacks boot address.
Changed
- Stacks blocks whose parents are mined >= 713,000 will use default costs from the new
costs-2
contract. - Stacks blocks whose parents are mined >= 713,000 will use the real serialized length of Clarity values as the cost inputs to several methods that previously used the maximum possible size for the associated types.
- Stacks blocks whose parents are mined >= 713,000 will use the new block limit defined in SIP-012.
Fixed
- Miners are now more aggressive in calculating their block limits when confirming microblocks (#2916)
Release 2.05.0.0.0-rc1
Merge pull request #2940 from blockstack/feat/test-mainnet testing: Unit tests for cost contracts on mainnet
Release next-costs-2
Merge pull request #2930 from blockstack/fix/existing-state Fix: insert epochs on migration in SortitionDB::connect
Release next-costs-1
Merge pull request #2920 from blockstack/fix/2904 2.05: make it so a block whose anchored parent is in a different epoch cannot confirm a microblock stream
Release serde-toml-1
panicking earlier
Release print-limits-1
added some logs
Release 2.0.11.4.0
This software update is a point-release to change the transaction
selection logic in the default miner to prioritize by an estimated fee
rate instead of raw fee. This release's chainstate directory is
compatible with chainstate directories from 2.0.11.3.0.
Added
- FeeEstimator and CostEstimator interfaces. These can be controlled
via node configuration options. See theREADME.md
for more
information on the configuration. - New fee rate estimation endpoint
/v2/fees/transaction
(#2872). See
docs/rpc/openapi.yaml
for more information.