github stacks-network/stacks-core 2.05.0.1.0
Release 2.05.0.1.0

latest releases: 2.5.0.0.7, 2.5.0.0.8-rc1, signer-2.5.0.0.5.2...
2 years ago

This software update is a point-release with a large set of changes. This release's chainstate directory is compatible with chainstate directories from 2.05.0.0.0.

Added

  • A new fee estimator intended to produce fewer over-estimates, by having less
    sensitivity to outliers. Its characteristic features are: 1) use a window to
    forget past estimates instead of exponential averaging, 2) use weighted
    percentiles, so that bigger transactions influence the estimates more, 3)
    assess empty space in blocks as having paid the "minimum fee", so that empty
    space is accounted for, 4) use random "fuzz" so that in busy times the fees can
    change dynamically. (#2972)
  • Implements anti-entropy protocol for querying transactions from other
    nodes' mempools. Before, nodes wouldn't sync mempool contents with one another.
    (#2884)
  • Structured logging in the mining code paths. This will shine light
    on what happens to transactions (successfully added, skipped or errored) that the
    miner considers while buildings blocks. (#2975)
  • Added the mined microblock event, which includes information on transaction
    events that occurred in the course of mining (will provide insight
    on whether a transaction was successfully added to the block,
    skipped, or had a processing error). (#2975)
  • For v2 endpoints, can now specify the tip parameter to latest. If
    tip=latest, the node will try to run the query off of the latest tip. (#2778)
  • Adds the /v2/headers endpoint, which returns a sequence of SIP-003-encoded
    block headers and consensus hashes (see the ExtendedStacksHeader struct that
    this PR adds to represent this data). (#2862)
  • Adds the /v2/data_var endpoint, which returns a contract's data variable
    value and a MARF proof of its existence. (#2862)
  • Fixed a bug in the unconfirmed state processing logic that could lead to a
    denial of service (node crash) for nodes that mine microblocks (#2970)
  • Added prometheus metric that tracks block fullness by logging the percentage of each
    cost dimension that is consumed in a given block (#3025).

Changed

  • Updated the mined block event. It now includes information on transaction
    events that occurred in the course of mining (will provide insight
    on whether a transaction was successfully added to the block,
    skipped, or had a processing error). (#2975)
  • Updated some of the logic in the block assembly for the miner and the follower
    to consolidate similar logic. Added functions setup_block and finish_block.
    (#2946)
  • Makes the p2p state machine more reactive to newly-arrived
    BlocksAvailable and MicroblocksAvailable messages for block and microblock
    streams that this node does not have. If such messages arrive during an inventory
    sync, the p2p state machine will immediately transition from the inventory sync
    work state to the block downloader work state, and immediately proceed to fetch
    the available block or microblock stream. (#2862)
  • Nodes will push recently-obtained blocks and microblock streams to outbound
    neighbors if their cached inventories indicate that they do not yet have them
    (#2986).
  • Nodes will no longer perform full inventory scans on their peers, except
    during boot-up, in a bid to minimize block-download stalls (#2986).
  • Nodes will process sortitions in parallel to downloading the Stacks blocks for
    a reward cycle, instead of doing these tasks sequentially (#2986).
  • The node's runloop will coalesce and expire stale requests to mine blocks on
    top of parent blocks that are no longer the chain tip (#2969).
  • Several database indexes have been updated to avoid table scans, which
    significantly improves most RPC endpoint speed and cuts node spin-up time in
    half (#2989, #3005).
  • Fixed a rare denial-of-service bug whereby a node that processes a very deep
    burnchain reorg can get stuck, and be rendered unable to process further
    sortitions. This has never happened in production, but it can be replicated in
    tests (#2989).
  • Updated what indices are created, and ensures that indices are created even
    after the database is initialized (#3029).

Fixed

  • Updates the lookup key for contracts in the pessimistic cost estimator. Before, contracts
    published by different principals with the same name would have had the same
    key in the cost estimator. (#2984)
  • Fixed a few prometheus metrics to be more accurate compared to /v2 endpoints
    when polling data (#2987)

Don't miss a new stacks-core release

NewReleases is sending notifications on new releases.