mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 20:12:57 +01:00
Merge #5910: docs: add release notes for 20.1.0
a4edab66a3 docs: add release notes for 20.1.0 (pasta)
Pull request description:
## Issue being fixed or feature implemented
Added release notes for 20.1.0
## What was done?
Wrote release notes from WIP release-notes; trimmed some fat from release notes
## How Has This Been Tested?
Ran linters
## Breaking Changes
None; docs only
## Checklist:
_Go over all the following points, and put an `x` in all the boxes that apply._
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e tests
- [ ] I have made corresponding changes to the documentation
- [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
Top commit has no ACKs.
Tree-SHA512: 47efb01e839f9357f6af372806350ac3cc3f6f18a7437afa670306050cb93c4a5ce7fd91256ae39c3febaabb9b078824e75d85792da37c063e74f8e13f0e465cThis commit is contained in:
pasta
commit
032c8fa395
@ -1,6 +0,0 @@
|
|||||||
Configuration option changes
|
|
||||||
----------------------------
|
|
||||||
|
|
||||||
- The `startupnotify` option is used to specify a command to
|
|
||||||
execute when Dash Core has finished with its startup
|
|
||||||
sequence. (#5728)
|
|
||||||
@ -1,9 +0,0 @@
|
|||||||
RPC changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
Exposed transaction version numbers are now treated as unsigned 16-bit integers
|
|
||||||
instead of signed 16-bit integers. This matches their treatment in consensus
|
|
||||||
logic. Versions greater than 3 continue to be non-standard (matching previous
|
|
||||||
behavior of smaller than 1 or greater than 3 being non-standard). Note that
|
|
||||||
this includes the joinpsbt command, which combines partially-signed
|
|
||||||
transactions by selecting the highest version number.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- `fundrawtransaction` and `walletcreatefundedpsbt` when used with the `lockUnspents`
|
|
||||||
argument now lock manually selected coins, in addition to automatically selected
|
|
||||||
coins. Note that locked coins are never used in automatic coin selection, but
|
|
||||||
can still be manually selected.
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
Command-line options
|
|
||||||
-----------------------------
|
|
||||||
|
|
||||||
The same ZeroMQ notification (e.g. `-zmqpubhashtx=address`) can now be specified multiple times to publish the same notification to different ZeroMQ sockets.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
Notification changes
|
|
||||||
--------------------
|
|
||||||
|
|
||||||
`-walletnotify` notifications are now sent for wallet transactions that are
|
|
||||||
removed from the mempool because they conflict with a new block. These
|
|
||||||
notifications were sent previously before the v18.1 release, but had been
|
|
||||||
broken since that release.
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
Updated RPC
|
|
||||||
--------
|
|
||||||
|
|
||||||
The `getpeerinfo` RPC now returns a `connection_type` field. This indicates the type of connection established with the peer. It will return one of six options. For more information, see the `getpeerinfo` help documentation.
|
|
||||||
@ -1,6 +0,0 @@
|
|||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- The `getpeerinfo` RPC now has additional `last_block` and `last_transaction`
|
|
||||||
fields that return the UNIX epoch time of the last block and the last valid
|
|
||||||
transaction received from each peer. (#19731)
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
Updated RPC
|
|
||||||
--------
|
|
||||||
|
|
||||||
- `getblockchaininfo` now returns a new `time` field, that provides the chain tip time.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
Build System
|
|
||||||
------------
|
|
||||||
|
|
||||||
The --enable-upnp-default and --enable-natpmp-default options
|
|
||||||
have been removed. If you want to use port mapping, you can
|
|
||||||
configure it using a .conf file, or by passing the relevant
|
|
||||||
options at runtime.
|
|
||||||
@ -1,5 +0,0 @@
|
|||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- `protx info`: It's now possible to get historical data at a specific block by providing its blockhash
|
|
||||||
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
RPC changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
RPC `gettxchainlocks` will also return the status `mempool` indicating whether the transaction is in the mempool or not.
|
|
||||||
@ -1,5 +0,0 @@
|
|||||||
Added RPC
|
|
||||||
--------
|
|
||||||
|
|
||||||
- `submitchainlock` RPC allows the submission of a ChainLock signature.
|
|
||||||
Note: This RPC is whitelisted for the Platform RPC user.
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
RPC changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
In `getspecialtxes` `instantlock` and `chainlock` fields were always `false`. They should show actual values now.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
Docker Build System
|
|
||||||
-------------------
|
|
||||||
|
|
||||||
Modified the Dockerfile to exclude the `dash-qt` graphical wallet interface from the set of binaries copied to
|
|
||||||
`/usr/local/bin` during the Docker image build process. This change streamlines the Docker image, making it more
|
|
||||||
suitable for server environments and headless applications, where the graphical user interface of `dash-qt` is not
|
|
||||||
required. The update enhances the Docker image's efficiency by reducing its size and minimizing unnecessary components.
|
|
||||||
@ -1,14 +0,0 @@
|
|||||||
Added RPC
|
|
||||||
--------
|
|
||||||
|
|
||||||
- `getassetunlockstatuses` RPC allows fetching of Asset Unlock txs by their withdrawal index.
|
|
||||||
The RPC accepts an array of indexes and an optional block height.
|
|
||||||
The possible outcomes per each index are:
|
|
||||||
- `chainlocked`: If the Asset Unlock index is mined on a ChainLocked block or up to the given block height.
|
|
||||||
- `mined`: If no ChainLock information is available for the mined Asset Unlock index.
|
|
||||||
- `mempooled`: If the Asset Unlock index is in the mempool.
|
|
||||||
- `unknown`: If none of the above are valid.
|
|
||||||
|
|
||||||
Note: If a specific block height is passed on request, then only `chainlocked` and `unknown` outcomes are possible.
|
|
||||||
|
|
||||||
Note: This RPC is whitelisted for the Platform RPC user.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
RPC Changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
### `submitchainlock` RPC method updates
|
|
||||||
- **Return Value Addition**: The method now returns the height of the current best ChainLock, allowing clients to easily compare the provided ChainLock height with the current best one.
|
|
||||||
- **Error Handling**: Added a check for the provided block height. If the block height is not greater than the height of the current best ChainLock, the method will return the best ChainLock's height without attempting to process a new ChainLock.
|
|
||||||
- **Code Optimization**: Refactored the retrieval of the `LLMQContext` and the best ChainLock's height to occur before the signature validation. This change streamlines the logic and potentially reduces redundant computations when the provided block height is already known to be not the best.
|
|
||||||
@ -1,7 +0,0 @@
|
|||||||
# Notable changes
|
|
||||||
|
|
||||||
## HD Wallets Enabled by Default
|
|
||||||
|
|
||||||
In this release, we are taking a significant step towards enhancing the Dash wallet's usability by enabling Hierarchical Deterministic (HD) wallets by default. This change aligns the behavior of `dashd` and `dash-qt` with the previously optional `-usehd=1` flag, making HD wallets the standard for all users.
|
|
||||||
|
|
||||||
While HD wallets are now enabled by default to improve user experience, Dash Core still allows for the creation of non-HD wallets by using the `-usehd=0` flag. However, users should be aware that this option is intended for legacy support and will be removed in future releases. Importantly, even with an HD wallet, users can still import non-HD private keys, ensuring flexibility in managing their funds.
|
|
||||||
@ -1,13 +0,0 @@
|
|||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- The `testmempoolaccept` RPC returns `vsize` and a `fee` object with the `base` fee
|
|
||||||
if the transaction passes validation.
|
|
||||||
- The `testmempoolaccept` RPC now accepts multiple transactions (still experimental at the moment,
|
|
||||||
API may be unstable). This is intended for testing transaction packages with dependency
|
|
||||||
relationships; it is not recommended for batch-validating independent transactions. In addition to
|
|
||||||
mempool policy, package policies apply: the list cannot contain more than 25 transactions or have a
|
|
||||||
total size exceeding 101K virtual bytes, and cannot conflict with (spend the same inputs as) each other or
|
|
||||||
the mempool. There are some known limitations to the accuracy of the test accept: it's possible for
|
|
||||||
`testmempoolaccept` to return "allowed"=True for a group of transactions, but "too-long-mempool-chain"
|
|
||||||
if they are actually submitted.
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
RPC changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
New RPC getrawtransactionmulti that can return batch up to 100 rawtransaction at one request.
|
|
||||||
@ -1,6 +0,0 @@
|
|||||||
Added RPC
|
|
||||||
--------
|
|
||||||
|
|
||||||
- `quorum dkginfo` RPC returns information about DKGs:
|
|
||||||
- `active_dkgs`: Total number of active DKG sessions this node is participating in right now.
|
|
||||||
- `next_dkg`: The number of blocks until the next potential DKG session.
|
|
||||||
@ -1,8 +0,0 @@
|
|||||||
Wallet
|
|
||||||
------
|
|
||||||
|
|
||||||
|
|
||||||
- The wallet can create a transaction without change even when the keypool is
|
|
||||||
empty. Previously it failed. (#17219)
|
|
||||||
|
|
||||||
|
|
||||||
@ -1,12 +1,8 @@
|
|||||||
# Dash Core version v20.0.4
|
# Dash Core version v20.1.0
|
||||||
|
|
||||||
Release is now available from:
|
This is a new minor version release, including various new features, improvements, and bug fixes.
|
||||||
|
|
||||||
<https://www.dash.org/downloads/#wallets>
|
This release is optional but recommended for all nodes.
|
||||||
|
|
||||||
This is a new patch version release, bringing small bug fixes and build system enhancements.
|
|
||||||
|
|
||||||
This release is optional for all nodes.
|
|
||||||
|
|
||||||
Please report bugs using the issue tracker at GitHub:
|
Please report bugs using the issue tracker at GitHub:
|
||||||
|
|
||||||
@ -20,10 +16,7 @@ Please report bugs using the issue tracker at GitHub:
|
|||||||
If you are running an older version, shut it down. Wait until it has completely
|
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
|
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
|
installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or
|
||||||
dashd/dash-qt (on Linux). If you upgrade after DIP0003 activation and you were
|
dashd/dash-qt (on Linux).
|
||||||
using version < 0.13 you will have to reindex (start with -reindex-chainstate
|
|
||||||
or -reindex) to make sure your wallet has all the new data synced. Upgrading
|
|
||||||
from version 0.13 should not require any additional actions.
|
|
||||||
|
|
||||||
## Downgrade warning
|
## Downgrade warning
|
||||||
|
|
||||||
@ -35,29 +28,96 @@ reindex or re-sync the whole chain.
|
|||||||
|
|
||||||
# Notable changes
|
# Notable changes
|
||||||
|
|
||||||
## Build changes
|
## HD Wallets Enabled by Default
|
||||||
|
|
||||||
The miner has been disabled for Windows binaries built via Guix. This resolves
|
In this release, we are taking a significant step towards enhancing the Dash wallet's usability by enabling Hierarchical
|
||||||
an issue that was preventing users from installing v20.0.3 due to false
|
Deterministic (HD) wallets by default. This change aligns the behavior of `dashd` and `dash-qt` with the previously
|
||||||
positive alerts from Microsoft Defender and other antivirus providers.
|
optional `-usehd=1` flag, making HD wallets the standard for all users.
|
||||||
|
|
||||||
Use a self-signed Windows code signing certificate instead of expired one. The
|
While HD wallets are now enabled by default to improve user experience, Dash Core still allows for the creation of
|
||||||
expired certificate being used previously caused most antivirus software to trigger.
|
non-HD wallets by using the `-usehd=0` flag. However, users should be aware that this option is intended for legacy
|
||||||
The new self-signed certificate results in a greatly improved installation experience.
|
support and will be removed in future releases. Importantly, even with an HD wallet, users can still import non-HD
|
||||||
|
private keys, ensuring flexibility in managing their funds.
|
||||||
|
|
||||||
Updated expired gpg keys for builders. Note that the actual keys themselves are the same.
|
## Windows release signing
|
||||||
The updated keys changed their expiration dates and added additional information such as
|
|
||||||
new email addresses.
|
|
||||||
|
|
||||||
## Governance
|
Windows releases are signed by a new certificate that replaces the expired one used previously.
|
||||||
|
|
||||||
Triggers from the past are now ignored when voting.
|
## Removal of Non-Deterministic InstantSend
|
||||||
|
|
||||||
## Asset lock and unlock transactions
|
Legacy InstantSend was deprecated with the activation of Deterministic InstantSend, but we kept the underlying logic for some time to ensure a smooth transition. v20.1 finally removes all Legacy InstantSend logic and will no longer support sending and receiving islock p2p messages and inv p2p messages with id 30. Such messages will be seen as unknown by v20.1 nodes. The protocol version was incremented to 70231 to indicate a change in network protocol. Please note that the -llmqinstantsend and -llmqtestinstantsend command line options have also been removed as part of this change.
|
||||||
|
|
||||||
Use the correct quorum for signing withdrawal (asset unlock) txes on RegTest.
|
## RPC changes
|
||||||
|
|
||||||
# v20.0.4 Change log
|
- `protx info`: It's now possible to get historical data at a specific block by providing its blockhash.
|
||||||
|
- `gettxchainlocks`: will now return the status `mempool` indicating whether the transaction is in the mempool.
|
||||||
|
or not.
|
||||||
|
- Exposed transaction version numbers are now treated as unsigned 16-bit integers instead of signed 16-bit integers.
|
||||||
|
This matches their treatment in consensus logic. Versions greater than 3 continue to be non-standard (matching previous
|
||||||
|
behavior of smaller than 1 or greater than 3 being non-standard). Note that this includes the joinpsbt command, which
|
||||||
|
combines partially-signed transactions by selecting the highest version number.
|
||||||
|
- `getpeerinfo`: now returns a `connection_type` field. This indicates the type of connection established with
|
||||||
|
the peer. It will return one of six options. For more information, see the `getpeerinfo` help documentation.
|
||||||
|
- `getpeerinfo`: now has additional `last_block` and `last_transaction` fields that return the UNIX epoch time
|
||||||
|
of the last block and the last valid transaction received from each peer.
|
||||||
|
- `getblockchaininfo`: now returns a new `time` field that provides the chain tip time.
|
||||||
|
- `fundrawtransaction` and `walletcreatefundedpsbt`: when used with the `lockUnspents` argument now lock manually
|
||||||
|
selected coins, in addition to automatically selected coins. Note that locked coins are never used in automatic coin
|
||||||
|
selection, but can still be manually selected.
|
||||||
|
- `testmempoolaccept`: returns `vsize` and a `fee` object with the `base` fee if the transaction passes
|
||||||
|
validation. The `testmempoolaccept` RPC now accepts multiple transactions (still experimental at the moment, API may be
|
||||||
|
unstable).
|
||||||
|
|
||||||
|
## Added RPCs
|
||||||
|
|
||||||
|
- `submitchainlock`: allows the submission of a ChainLock signature. Note: This RPC is whitelisted for the Platform
|
||||||
|
RPC user.
|
||||||
|
- `getassetunlockstatuses`: allows fetching of Asset Unlock txs by their withdrawal index. The RPC accepts an array
|
||||||
|
of indexes and an optional block height. The possible outcomes per each index are: `chainlocked`, `mined`, `mempooled`,
|
||||||
|
`unknown`. Note: If a specific block height is passed on request, then only `chainlocked` and `unknown` outcomes are
|
||||||
|
possible. This RPC is whitelisted for the Platform RPC user.
|
||||||
|
- `quorum dkginfo`: returns information about DKGs: `active_dkgs` and `next_dkg`.
|
||||||
|
- `getrawtransactionmulti`: allows requesting a batch of up to 100 raw transactions per request.
|
||||||
|
|
||||||
|
## Docker Build System
|
||||||
|
|
||||||
|
Modified the Dockerfile to exclude the `dash-qt` graphical wallet interface from the set of binaries copied to
|
||||||
|
`/usr/local/bin` during the Docker image build process. This change streamlines the Docker image, making it more
|
||||||
|
suitable for server environments and headless applications, where the graphical user interface of `dash-qt` is not
|
||||||
|
required. The update enhances the Docker image's efficiency by reducing its size and minimizing unnecessary components.
|
||||||
|
|
||||||
|
## Command-line options
|
||||||
|
|
||||||
|
- The same ZeroMQ notification (e.g. `-zmqpubhashtx=address`) can now be specified multiple times to publish the same
|
||||||
|
notification to different ZeroMQ sockets.
|
||||||
|
- `-startupnotify=<cmd>`: Execute command on startup.
|
||||||
|
|
||||||
|
|
||||||
|
## Notification changes
|
||||||
|
|
||||||
|
- `-walletnotify` notifications are now sent for wallet transactions that are removed from the mempool because they
|
||||||
|
conflict with a new block. These notifications were sent previously, but have been broken since
|
||||||
|
the v18.1 release.
|
||||||
|
- The `startupnotify` option is used to specify a command to execute when Dash Core has finished with its startup
|
||||||
|
sequence.
|
||||||
|
|
||||||
|
## Build System
|
||||||
|
|
||||||
|
The `--enable-upnp-default` and `--enable-natpmp-default` options have been removed. If you want to use port mapping,
|
||||||
|
you can configure it using a `.conf` file, or by passing the relevant options at runtime.
|
||||||
|
|
||||||
|
## Wallet
|
||||||
|
|
||||||
|
- The wallet can create a transaction without change even when the keypool is empty. Previously it failed.
|
||||||
|
- New Discreet mode for hiding balances in Dash-Qt
|
||||||
|
- Added a "Close all wallet" menu item for Dash-Qt
|
||||||
|
|
||||||
|
## Backports from Bitcoin Core
|
||||||
|
|
||||||
|
This release introduces many updates from Bitcoin v0.20-v25.0. Breaking changes are documented here; however, for
|
||||||
|
additional detail on what’s included in Bitcoin, please refer to their release notes.
|
||||||
|
|
||||||
|
# v20.1.0 Change log
|
||||||
|
|
||||||
See detailed [set of changes][set-of-changes].
|
See detailed [set of changes][set-of-changes].
|
||||||
|
|
||||||
@ -65,35 +125,23 @@ See detailed [set of changes][set-of-changes].
|
|||||||
|
|
||||||
Thanks to everyone who directly contributed to this release:
|
Thanks to everyone who directly contributed to this release:
|
||||||
|
|
||||||
- Konstantin Akimov (knst)
|
- Alessandro Rezzi
|
||||||
|
- Kittywhiskers Van Gogh
|
||||||
|
- Konstantin Akimov
|
||||||
|
- Odysseas Gabrielides
|
||||||
- PastaPastaPasta
|
- PastaPastaPasta
|
||||||
|
- thephez
|
||||||
- UdjinM6
|
- UdjinM6
|
||||||
|
- Vijay Manikpuri
|
||||||
|
|
||||||
As well as everyone that submitted issues, reviewed pull requests and helped
|
As well as everyone that submitted issues, reviewed pull requests and helped
|
||||||
debug the release candidates.
|
debug the release candidates.
|
||||||
|
|
||||||
# Older releases
|
# Older releases
|
||||||
|
|
||||||
Dash was previously known as Darkcoin.
|
|
||||||
|
|
||||||
Darkcoin tree 0.8.x was a fork of Litecoin tree 0.8, original name was XCoin
|
|
||||||
which was first released on Jan/18/2014.
|
|
||||||
|
|
||||||
Darkcoin tree 0.9.x was the open source implementation of masternodes based on
|
|
||||||
the 0.8.x tree and was first released on Mar/13/2014.
|
|
||||||
|
|
||||||
Darkcoin tree 0.10.x used to be the closed source implementation of Darksend
|
|
||||||
which was released open source on Sep/25/2014.
|
|
||||||
|
|
||||||
Dash Core tree 0.11.x was a fork of Bitcoin Core tree 0.9,
|
|
||||||
Darkcoin was rebranded to Dash.
|
|
||||||
|
|
||||||
Dash Core tree 0.12.0.x was a fork of Bitcoin Core tree 0.10.
|
|
||||||
|
|
||||||
Dash Core tree 0.12.1.x was a fork of Bitcoin Core tree 0.12.
|
|
||||||
|
|
||||||
These release are considered obsolete. Old release notes can be found here:
|
These release are considered obsolete. Old release notes can be found here:
|
||||||
|
|
||||||
|
- [v20.0.4](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.4.md) released Jan/13/2024
|
||||||
- [v20.0.3](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.3.md) released December/26/2023
|
- [v20.0.3](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.3.md) released December/26/2023
|
||||||
- [v20.0.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.2.md) released December/06/2023
|
- [v20.0.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.2.md) released December/06/2023
|
||||||
- [v20.0.1](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.1.md) released November/18/2023
|
- [v20.0.1](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.1.md) released November/18/2023
|
||||||
@ -140,4 +188,4 @@ These release are considered obsolete. Old release notes can be found here:
|
|||||||
- [v0.10.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.10.0.md) released Sep/25/2014
|
- [v0.10.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.10.0.md) released Sep/25/2014
|
||||||
- [v0.9.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.9.0.md) released Mar/13/2014
|
- [v0.9.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.9.0.md) released Mar/13/2014
|
||||||
|
|
||||||
[set-of-changes]: https://github.com/dashpay/dash/compare/v20.0.3...dashpay:v20.0.4
|
[set-of-changes]: https://github.com/dashpay/dash/compare/v20.0.4...dashpay:v20.1.0
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user