Bot releases are hidden (Show)
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
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.
/drop_mempool_tx
endpoint to notify event observers when a mempool"reward_slot_holders"
field to the new_burn_block
eventstacks-node
STACKS_TRANSACTION_LOG=1
/v2/traits/contractAddr/contractName/traitContractName /traitContractAddr/traitName
to determine whether a given trait is implemented/v2/pox
RPC endpoint was updated to include more usefuldocs/rpc-endpoints.md
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
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.
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
The chainstate directory has been restructured in this release. It is not
compatible with prior chainstate directories.
/drop_mempool_tx
endpoint to notify event observers when a mempool"reward_slot_holders"
field to the new_burn_block
eventstacks-node
STACKS_TRANSACTION_LOG=1
v2/traits/contractAddr/contractName/traitContractName /traitContractAddr/traitName
to determine whether a given trait is implemented/v2/pox
RPC endpoint was updated to include more usefuldocs/rpc-endpoints.md
Published by blockstack-devops over 3 years ago
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.
Published by blockstack-devops over 3 years ago
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.
Published by blockstack-devops over 3 years ago
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.
at-block
behavior in clarity-cli
and unit tests (no changes in stacks-node
Published by blockstack-devops over 3 years ago
This is an emergency hotfix that prevents the node from accidentally deleting
valid block data if its descendant microblock stream is invalid for some reason.
Published by blockstack-devops over 3 years ago
The database schema has not changed since 2.0.5, so when spinning up a
2.0.6 node from a 2.0.5 chainstate, you do not need to use a fresh
working directory. Earlier versions' chainstate directories are
incompatible, however.
Published by blockstack-devops over 3 years ago
Note: This release contains a database schema change and therefore a fresh working directory must be used to spin up the node.
During this, miners are recommended to use the new --mine-at-height
command line argument which will instruct the node to not mine until the Stacks chain has synchronized to the provided Stacks block height.
tx_fees_streamed_produced
fees are included in miner coinbasePublished by blockstack-devops over 3 years ago
Published by blockstack-devops over 3 years ago
Note: This release contains a database schema change and therefore a fresh working directory must be used to spin up the node.
During this, miners are recommended to use the new --mine-at-height
command line argument which will instruct the node to not mine until the Stacks chain has synchronized to the provided Stacks block height.
stacks-node --mine-at-height
commandline option, which tells thestacks-node
not to mine until it has synchronized to the given/v2/blocks/upload/{consensus_hash}
that acceptsstacks-node
, and improves network performancewait_time_for_microblocks
: from 60s to 30sGetBlocksInv
p2pLeaderBlockCommit
operations inflight is improved, drasticallyLeaderBlockCommit
is not included in the Bitcoin block it wasLeaderBlockCommit
operations using the UTXOs of the previousrbf_fee_increment
.Published by blockstack-devops almost 4 years ago