Blockstack

Latest version: v22.0.0.0

Safety actively analyzes 621469 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

2.0.11.2.0

NOTE: This change resets the `testnet`. Users running a testnet node will need
to reset their chain states.

Added

- `clarity-cli` will now also print a serialized version of the resulting
output from `eval` and `execute` commands. This serialization is in
hexademical string format and supports integration with other tools. (2684)
- The creation of a Bitcoin wallet with BTC version `> 0.19` is now supported
on a private testnet. (2647)
- `lcov`-compatible coverage reporting has been added to `clarity-cli` for
Clarity contract testing. (2592)
- The `README.md` file has new documentation about the release process. (2726)

Changed

- This change resets the testnet. (2742)
- Caching has been added to speed up `/v2/info` responses. (2746)

Fixed

- PoX syncing will only look back to the reward cycle prior to divergence,
instead of looking back over all history. This will speed up running a
follower node. (2746)
- The UTXO staleness check is re-ordered so that it occurs before the RBF-limit
check. This way, if stale UTXOs reached the "RBF limit" a miner will recover
by resetting the UTXO cache. (2694)
- Microblock events were being sent to the event observer when microblock data
was received by a peer, but were not emitted if the node mined the
microblocks itself. This made something like the private-testnet setup
incapable of emitting microblock events. Microblock events are now sent
even when self-mined. (2653)
- A bug is fixed in the mocknet/helium miner that would lead to a panic if a
burn block occurred without a sortition in it. (2711)
- Two bugs that caused problems syncing with the bitcoin chain during a
bitcoin reorg have been fixed (2771, 2780).
- Documentation is fixed in cases where string and buffer types are allowed
but not covered in the documentation. (2676)

2.0.11.1.0

This software update is our monthly release. It introduces fixes and features for both developers and miners.
This release's chainstate directory is compatible with chainstate directories from 2.0.11.0.0.

Added

- `/new_microblock` endpoint to notify event observers when a valid microblock
has been received (2571).
- Added new features to `clarity-cli` (2597)
- Exposing new mining-related metrics in prometheus (2664)
- Miner's computed relative miner score as a percentage
- Miner's computed commitment, the min of their previous commitment and their median commitment
- Miner's current median commitment
- Add `key-for-seed` command to the `stacks-node` binary - outputs the associated secret key hex string
and WIF formatted secret key for a given "seed" value (2658).

Changed

- Improved mempool walk order (2514).
- Renamed database `tx_tracking.db` to `tx_tracking.sqlite` (2666).

Fixed

- Alter the miner to prioritize spending the most recent UTXO when building a transaction,
instead of the largest UTXO. In the event of a tie, it uses the smallest UTXO first (2661).
- Fix trait rpc lookups for implicitly implemented traits (2602).
- Fix `v2/pox` endpoint, broken on Mocknet (2634).
- Align cost limits on mocknet, testnet and mainnet (2660).
- Log peer addresses in the HTTP server (2667)
- Mine microblocks if there are no recent unprocessed Stacks blocks

2.0.11.0.0

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).
- 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.

2.0.10.0.1

This is a low-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](README.md).

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).

2.0.9

This is a hotfix release for improved handling of arriving Stacks blocks through
both the RPC interface and the P2P ineterface. The chainstate directory of
2.0.9 is compatible with the 2.0.8 chainstate.

Fixed

- TOCTTOU bug fixed in the chain processing logic that, which now ensures that
an arriving Stacks block is processed at most once.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.