Skip to content

Latest commit

 

History

History
162 lines (128 loc) · 10.5 KB

release-notes.md

File metadata and controls

162 lines (128 loc) · 10.5 KB

Dash Core version v22.1.0

This is a new minor version release, bringing new features, and various bugfixes. This release is optional for all nodes, although recommended.

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 < v22.0.0

Downgrading to a version older than v22.0.0 may not be supported, and will likely require a reindex.

Release Notes

Build Changes

The macOS distribution is no longer packaged in a disk image (DMG) and is now packaged in a ZIP archive. The macOS distribution is once again notarized.

BIP324 / v2 P2P Protocol

Version 2 of the Dash P2P protocol / BIP324, which enables encryption of the P2P protocol, has been enabled by default in this version. This was initially introduced in Dash Core v22.0.0 as an experimental feature and has now been enabled by default. This change is backward compatible, and connections to peers which do not support the v2 protocol will revert to using the v1 protocol.

Network Changes

System ports, or ports that are lower than 1024 are now considered to be "bad" ports. As a result, other peers will avoid connecting to nodes that are listening on these ports. This change is to prevent potential DDoS attacks against services running on these ports. A number of other ports commonly used for authenticated services are also considered "bad" ports. You can view the list of bad ports here.

Tests

  • Command line arguments -dip8params and -bip147height are removed in favor of -testactivationheight. (dash#6325)
  • Several hard forks now activate earlier on regtest.

New RPCs

  • getislocks
    • Retrieves the InstantSend lock data for the given transaction IDs (txids). Returns the lock information in both a human-friendly JSON format and a binary hex-encoded zmq-compatible format.

Updated RPCs

  • The top-level fee fields fee, modifiedfee, ancestorfees and descendantfees returned by RPCs getmempoolentry,getrawmempool(verbose=true), getmempoolancestors(verbose=true) and getmempooldescendants(verbose=true) are deprecated and will be removed in the next major version (use -deprecated=fees if needed in this version). The same fee fields can be accessed through the fees object in the result. WARNING: deprecated fields ancestorfees and descendantfees are denominated in duffs, whereas all fields in the fees object are denominated in DASH.
  • A new hex field has been added to the getbestchainlock RPC, which returns the ChainLock information in zmq-compatible, hex-encoded binary format.
  • lockunspent now optionally takes a third parameter, persistent, which causes the lock to be written persistently to the wallet database. This allows UTXOs to remain locked even after node restarts or crashes.

GUI changes

  • UTXOs locked via the GUI are now stored persistently in the wallet database and are not lost on node shutdown or crash.
  • Improved GUI responsiveness for large wallets. (dash#6457)

v22.1.0 Change log

See detailed set of changes.

Credits

Thanks to everyone who directly contributed to this release:

  • Kittywhiskers Van Gogh
  • Konstantin Akimov
  • PastaPastaPasta
  • UdjinM6
  • Vijaydasmp

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: