You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a4edab6 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: 47efb01e839f9357f6af372806350ac3cc3f6f18a7437afa670306050cb93c4a5ce7fd91256ae39c3febaabb9b078824e75d85792da37c063e74f8e13f0e465c
Copy file name to clipboardexpand all lines: doc/release-notes.md
+94-46
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,8 @@
1
-
# Dash Core version v20.0.4
1
+
# Dash Core version v20.1.0
2
2
3
-
Release is now available from:
3
+
This is a new minor version release, including various new features, improvements, and bug fixes.
4
4
5
-
<https://www.dash.org/downloads/#wallets>
6
-
7
-
This is a new patch version release, bringing small bug fixes and build system enhancements.
8
-
9
-
This release is optional for all nodes.
5
+
This release is optional but recommended for all nodes.
10
6
11
7
Please report bugs using the issue tracker at GitHub:
12
8
@@ -20,10 +16,7 @@ Please report bugs using the issue tracker at GitHub:
20
16
If you are running an older version, shut it down. Wait until it has completely
21
17
shut down (which might take a few minutes for older versions), then run the
22
18
installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or
23
-
dashd/dash-qt (on Linux). If you upgrade after DIP0003 activation and you were
24
-
using version < 0.13 you will have to reindex (start with -reindex-chainstate
25
-
or -reindex) to make sure your wallet has all the new data synced. Upgrading
26
-
from version 0.13 should not require any additional actions.
19
+
dashd/dash-qt (on Linux).
27
20
28
21
## Downgrade warning
29
22
@@ -35,65 +28,120 @@ reindex or re-sync the whole chain.
35
28
36
29
# Notable changes
37
30
38
-
## Build changes
31
+
## HD Wallets Enabled by Default
32
+
33
+
In this release, we are taking a significant step towards enhancing the Dash wallet's usability by enabling Hierarchical
34
+
Deterministic (HD) wallets by default. This change aligns the behavior of `dashd` and `dash-qt` with the previously
35
+
optional `-usehd=1` flag, making HD wallets the standard for all users.
36
+
37
+
While HD wallets are now enabled by default to improve user experience, Dash Core still allows for the creation of
38
+
non-HD wallets by using the `-usehd=0` flag. However, users should be aware that this option is intended for legacy
39
+
support and will be removed in future releases. Importantly, even with an HD wallet, users can still import non-HD
40
+
private keys, ensuring flexibility in managing their funds.
41
+
42
+
## Windows release signing
43
+
44
+
Windows releases are signed by a new certificate that replaces the expired one used previously.
45
+
46
+
## Removal of Non-Deterministic InstantSend
47
+
48
+
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.
49
+
50
+
## RPC changes
51
+
52
+
-`protx info`: It's now possible to get historical data at a specific block by providing its blockhash.
53
+
-`gettxchainlocks`: will now return the status `mempool` indicating whether the transaction is in the mempool.
54
+
or not.
55
+
- Exposed transaction version numbers are now treated as unsigned 16-bit integers instead of signed 16-bit integers.
56
+
This matches their treatment in consensus logic. Versions greater than 3 continue to be non-standard (matching previous
57
+
behavior of smaller than 1 or greater than 3 being non-standard). Note that this includes the joinpsbt command, which
58
+
combines partially-signed transactions by selecting the highest version number.
59
+
-`getpeerinfo`: now returns a `connection_type` field. This indicates the type of connection established with
60
+
the peer. It will return one of six options. For more information, see the `getpeerinfo` help documentation.
61
+
-`getpeerinfo`: now has additional `last_block` and `last_transaction` fields that return the UNIX epoch time
62
+
of the last block and the last valid transaction received from each peer.
63
+
-`getblockchaininfo`: now returns a new `time` field that provides the chain tip time.
64
+
-`fundrawtransaction` and `walletcreatefundedpsbt`: when used with the `lockUnspents` argument now lock manually
65
+
selected coins, in addition to automatically selected coins. Note that locked coins are never used in automatic coin
66
+
selection, but can still be manually selected.
67
+
-`testmempoolaccept`: returns `vsize` and a `fee` object with the `base` fee if the transaction passes
68
+
validation. The `testmempoolaccept` RPC now accepts multiple transactions (still experimental at the moment, API may be
69
+
unstable).
70
+
71
+
## Added RPCs
72
+
73
+
-`submitchainlock`: allows the submission of a ChainLock signature. Note: This RPC is whitelisted for the Platform
74
+
RPC user.
75
+
-`getassetunlockstatuses`: allows fetching of Asset Unlock txs by their withdrawal index. The RPC accepts an array
76
+
of indexes and an optional block height. The possible outcomes per each index are: `chainlocked`, `mined`, `mempooled`,
77
+
`unknown`. Note: If a specific block height is passed on request, then only `chainlocked` and `unknown` outcomes are
78
+
possible. This RPC is whitelisted for the Platform RPC user.
79
+
-`quorum dkginfo`: returns information about DKGs: `active_dkgs` and `next_dkg`.
80
+
-`getrawtransactionmulti`: allows requesting a batch of up to 100 raw transactions per request.
81
+
82
+
## Docker Build System
39
83
40
-
The miner has been disabled for Windows binaries built via Guix. This resolves
41
-
an issue that was preventing users from installing v20.0.3 due to false
42
-
positive alerts from Microsoft Defender and other antivirus providers.
84
+
Modified the Dockerfile to exclude the `dash-qt` graphical wallet interface from the set of binaries copied to
85
+
`/usr/local/bin` during the Docker image build process. This change streamlines the Docker image, making it more
86
+
suitable for server environments and headless applications, where the graphical user interface of `dash-qt` is not
87
+
required. The update enhances the Docker image's efficiency by reducing its size and minimizing unnecessary components.
43
88
44
-
Use a self-signed Windows code signing certificate instead of expired one. The
45
-
expired certificate being used previously caused most antivirus software to trigger.
46
-
The new self-signed certificate results in a greatly improved installation experience.
89
+
## Command-line options
47
90
48
-
Updated expired gpg keys for builders. Note that the actual keys themselves are the same.
49
-
The updated keys changed their expiration dates and added additional information such as
50
-
new email addresses.
91
+
- The same ZeroMQ notification (e.g. `-zmqpubhashtx=address`) can now be specified multiple times to publish the same
92
+
notification to different ZeroMQ sockets.
93
+
-`-startupnotify=<cmd>`: Execute command on startup.
51
94
52
-
## Governance
53
95
54
-
Triggers from the past are now ignored when voting.
96
+
## Notification changes
55
97
56
-
## Asset lock and unlock transactions
98
+
-`-walletnotify` notifications are now sent for wallet transactions that are removed from the mempool because they
99
+
conflict with a new block. These notifications were sent previously, but have been broken since
100
+
the v18.1 release.
101
+
- The `startupnotify` option is used to specify a command to execute when Dash Core has finished with its startup
102
+
sequence.
57
103
58
-
Use the correct quorum for signing withdrawal (asset unlock) txes on RegTest.
104
+
## Build System
59
105
60
-
# v20.0.4 Change log
106
+
The `--enable-upnp-default` and `--enable-natpmp-default` options have been removed. If you want to use port mapping,
107
+
you can configure it using a `.conf` file, or by passing the relevant options at runtime.
108
+
109
+
## Wallet
110
+
111
+
- The wallet can create a transaction without change even when the keypool is empty. Previously it failed.
112
+
- New Discreet mode for hiding balances in Dash-Qt
113
+
- Added a "Close all wallet" menu item for Dash-Qt
114
+
115
+
## Backports from Bitcoin Core
116
+
117
+
This release introduces many updates from Bitcoin v0.20-v25.0. Breaking changes are documented here; however, for
118
+
additional detail on what’s included in Bitcoin, please refer to their release notes.
119
+
120
+
# v20.1.0 Change log
61
121
62
122
See detailed [set of changes][set-of-changes].
63
123
64
124
# Credits
65
125
66
126
Thanks to everyone who directly contributed to this release:
67
127
68
-
- Konstantin Akimov (knst)
128
+
- Alessandro Rezzi
129
+
- Kittywhiskers Van Gogh
130
+
- Konstantin Akimov
131
+
- Odysseas Gabrielides
69
132
- PastaPastaPasta
133
+
- thephez
70
134
- UdjinM6
135
+
- Vijay Manikpuri
71
136
72
137
As well as everyone that submitted issues, reviewed pull requests and helped
73
138
debug the release candidates.
74
139
75
140
# Older releases
76
141
77
-
Dash was previously known as Darkcoin.
78
-
79
-
Darkcoin tree 0.8.x was a fork of Litecoin tree 0.8, original name was XCoin
80
-
which was first released on Jan/18/2014.
81
-
82
-
Darkcoin tree 0.9.x was the open source implementation of masternodes based on
83
-
the 0.8.x tree and was first released on Mar/13/2014.
84
-
85
-
Darkcoin tree 0.10.x used to be the closed source implementation of Darksend
86
-
which was released open source on Sep/25/2014.
87
-
88
-
Dash Core tree 0.11.x was a fork of Bitcoin Core tree 0.9,
89
-
Darkcoin was rebranded to Dash.
90
-
91
-
Dash Core tree 0.12.0.x was a fork of Bitcoin Core tree 0.10.
92
-
93
-
Dash Core tree 0.12.1.x was a fork of Bitcoin Core tree 0.12.
94
-
95
142
These release are considered obsolete. Old release notes can be found here:
96
143
144
+
-[v20.0.4](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.4.md) released Jan/13/2024
97
145
-[v20.0.3](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.3.md) released December/26/2023
98
146
-[v20.0.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-20.0.2.md) released December/06/2023
99
147
-[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:
140
188
-[v0.10.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.10.0.md) released Sep/25/2014
141
189
-[v0.9.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.9.0.md) released Mar/13/2014
0 commit comments