Skip to content

release-notes.md

Latest commit

 

History

History
161 lines (127 loc) · 8.39 KB

release-notes.md

File metadata and controls

161 lines (127 loc) · 8.39 KB
Raw

Dash Core version v23.1.8

This is a new patch version release, fixing three remotely reachable crashes and bringing further hardening of the peer-to-peer message handlers along with networking, RPC and build fixes. Upgrading is strongly recommended for all nodes, and required for masternodes.

Please report bugs using the issue tracker at GitHub:

https://github.com/dashpay/dash/issues

Upgrading and downgrading

How to Upgrade

If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or dashd/dash-qt (on Linux).

Downgrade warning

Downgrade to a version < v23.0.0

Downgrading to a version older than v23.0.0 is not supported, and will require a reindex.

Release Notes

Critical fixes

This release fixes three crashes that a remote party could trigger. None of them affect consensus rules or put funds at risk, but each one can take a node offline, so all operators should upgrade promptly.

  • Fixed a crash while removing provider transactions that a masternode's operator-key change invalidates. Those transactions are collected before any of them are removed, so when one was an in-mempool descendant of another it was already erased along with its ancestor, and the stale entry was then dereferenced. Such entries are now skipped. This is reachable whenever a block carries a provider registrar update or revocation for a masternode that has chained service updates pending in the mempool.
  • Fixed a crash caused by an unvalidated LLMQ type in a qsigshare message. A masternode that received a signature share naming an LLMQ type its chain does not register would index a per-type quorum cache that is only populated for known types, aborting the process. Unregistered types are now rejected before the lookup, and the affected cache lookups no longer create missing entries.
  • Fixed a crash caused by a quorum commitment naming a block with no parent, such as the genesis block. The parentless block index reached a non-null precondition and terminated the process instead of failing validation, which no exception handler could contain. Commitments with a parentless quorum base block are now rejected, and the LLMQ activation check treats a null predecessor as "not enabled" rather than a contract violation.

Security

This release continues the hardening of peer-to-peer message handlers against denial-of-service from remote peers. These issues do not affect consensus and do not put funds at risk, but they could be used to crash or degrade nodes - masternodes in particular - so upgrading is recommended.

  • LLMQ / signing: the queues of not-yet-verified recovered signatures and signature shares are now bounded, and the vectors carried by the QSIGSHARE, QSIGSESANN, QSIGSHARESINV, QGETSIGSHARES and QBSIGSHARES messages are bounded before any allocation or decoding takes place. The number of signing share sessions a single peer may announce is also capped, so a peer can no longer grow that per-peer state without limit (dash#7351).
  • LLMQ / DKG: the number of encrypted contribution blobs in a DKG contribution is now checked against the quorum's lower bound as well as its upper bound.
  • LLMQ / quorum data: the verification vector and encrypted contribution vectors in QDATA responses are validated against their expected sizes before any BLS decoding is performed.
  • Transaction relay: an oversized notfound message is now penalised rather than silently ignored (dash#7348).
  • ChainLocks: the cache of seen ChainLock signatures is now bounded.
  • Governance: per-object vote sync requests are now throttled per peer, and governance object and vote responses are only accepted from a peer if that peer announced them or they were requested from it, using the net-layer per-peer request tracker. Governance vote signatures are bounded when read from the network and must use one of the two legitimate encodings.
  • CoinJoin: the vectors carried by CoinJoin mixing messages are bounded before allocation, and a non-participant can no longer abort another session's signing phase. An invalid dstx message now carries a misbehaviour score instead of being dropped for free (dash#7347).
  • Bloom filters: filterload and filteradd payloads are bounded before allocation.
  • Sporks: spork signatures are bounded during deserialization, and malformed spork messages now attribute misbehaviour to the sending peer.
  • Compact block relay: batched hardening backported from upstream Bitcoin Core (dash#7398), including detection of mutated blocks as a defence-in-depth measure.

RPC

  • protx listdiff no longer reports an always-zero platformP2PPort / platformHTTPPort for masternodes registered with extended addresses; the live Platform ports are reported instead.

GUI

  • The PoSe score column is no longer hidden together with banned masternodes in the masternode list.
  • Fixed an abort when scaling widgets whose font was set in pixels rather than points (for example by a stylesheet's font-size: Npx); such fonts are now converted to a point size instead of being assumed to have one (dash#7465).

Build and CI

  • Fixed a CMake compatibility error when building the freetype dependency with newer CMake (dash#7372).
  • Stabilized the -par / -parbls help text (and the generated man pages) so they no longer embed the core count of the build machine.
  • Updated GitHub Actions pins for the Node 24 runtime.
  • Fixed the circular-dependencies lint script under Python 3.15.

Tests

  • Governance inventory cache coverage moved from a functional test to unit tests, and governance vote test fixtures are now wire-valid.

v23.1.8 Change log

See detailed set of changes.

Credits

Thanks to everyone who directly contributed to this release:

  • Konstantin Akimov
  • PastaClaw
  • PastaPastaPasta
  • UdjinM6

As well as everyone that submitted issues, reviewed pull requests and helped debug the release candidates.

Older releases

These releases are considered obsolete. Old release notes can be found here: