Skip to content

Commit 2c72c07

Browse files
UdjinM6UdjinM6
authored
Merge pull request #2842 from UdjinM6/mergemaster133develop
Merge master v0.13.3 into develop
2 parents 6982d98 + fa6db6d commit 2c72c07

File tree

2 files changed

+208
-68
lines changed

2 files changed

+208
-68
lines changed

‎doc/release-notes.md

+36-68
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Dash Core version 0.13.2.0
1+
Dash Core version 0.13.3.0
22
==========================
33

44
Release is now available from:
@@ -25,9 +25,9 @@ dashd/dash-qt (on Linux). If you upgrade after DIP0003 activation you will
2525
have to reindex (start with -reindex-chainstate or -reindex) to make sure
2626
your wallet has all the new data synced (only if you were using version < 0.13).
2727

28-
Note that there is no protocol bump in this version and thus active masternodes
29-
updating from v0.13.0.0 or v0.13.1.0 do not require any additional actions (no need to issue
30-
`masternode start` command).
28+
As spork15 has been activated on mainnet, there is no need for `masternode start`
29+
anymore. Upgrading a masternode now only involves replacing binaries and restarting
30+
the node.
3131

3232
Downgrade warning
3333
-----------------
@@ -37,95 +37,62 @@ Downgrade warning
3737
Downgrading to a version smaller than 0.13 is not supported anymore as DIP2/DIP3 has activated
3838
on mainnet and testnet.
3939

40-
### Downgrade to 0.13.0.0 or 0.13.1.0
40+
### Downgrade to a version < 0.13.3.0
4141

42-
Downgrading to 0.13.0.0 is fully supported but is not recommended unless you have some serious issues with 0.13.2.0.
42+
Downgrading to previous 0.13 releases is fully supported but is not recommended unless you have some serious issues with 0.13.3.0.
4343

4444
Notable changes
4545
===============
4646

47-
Providing "masternodeblsprivkey" is now mandatory when the node is launched as a masternode ("masternode=1")
48-
------------------------------------------------------------------------
49-
In previous versions, "masternodeblsprivkey" was not mandatory as these versions had to function with and without DIP3
50-
activation. Now that DIP3 has activated on mainnet and testnet, we can make "masternodeblsprivkey" mandatory when
51-
configuring and running a masternode. Please note that your masternode will fail to start when "masternodeblsprivkey"
52-
is not specified. This also means that 0.13.2.0 will only work with masternodes which have already registered their
53-
DIP3 masternode. This enforcement was added to catch misconfigurations of masternodes which would otherwise stay
54-
unnoticed until spork 15 activation and thus surprise and hurt masternode owners.
55-
56-
Fix for consistency issues after sudden stopping of node
57-
--------------------------------------------------------
58-
Previous versions resulted in inconsistency between the chainstate and evodb when the node crashed or otherwise suddenly
59-
stopped (e.g. power failure). This should be fixed in 0.13.2.0.
60-
61-
Fix for litemode nodes to not reject specific DIP3 transactions
62-
---------------------------------------------------------------
63-
Previous versions might cause litemode nodes to reject the mainnet chain after spork 15 activation. This is due to a
64-
consensus rule being less strict in one specific case when spork 15 is active. Litemode nodes can not know about the
65-
change in consensus rules as they have no knowledge about sporks. In 0.13.2.0, when litemode is enabled, we default to the
66-
behaviour of activated spork15 in this specific case, which fixes the issue. The restriction will be completely removed
67-
in the next major release.
68-
69-
Fix incorrect behavior for "protx diff" and the P2P message "GETMNLISTDIFF"
70-
---------------------------------------------------------------------------
71-
Both were responding with errors when "0" was used as base block hash. DIP4 defines "0" to be equivalent with the
72-
genesis block, so that it's easy for peers to request the full masternode list.
73-
This is mostly important for SPV nodes (e.g. mobile wallets) which need the masternode list. Right now, all nodes in
74-
the network will respond with an error when "0" is provided in "GETMNLISTDIFF". Until enough masternodes have upgraded
75-
to 0.13.2.0, SPV nodes should use the full genesis hash to circumvent the error.
76-
77-
Exclusion of LLMQ quorum commitments from partial blocks
78-
--------------------------------------------------------
79-
SPV nodes are generally not interested in non-financial special transactions in blocks, so we're omitting them now when
80-
sending partial/filtered blocks to SPV clients. This currently only filters LLMQ quorum commitments, which also caused
81-
some SPV implementations to ban nodes as they were not able to process these. DIP3 transactions (ProRegTx, ProUpRegTx, ...)
82-
are not affected and are still included in partial/filtered blocks as these might also move funds.
83-
84-
RPC changes
85-
-----------
86-
`masternode list json` and `protx list` will now include the collateral address of masternodes.
47+
Number of false-positives from anti virus software should be reduced
48+
--------------------------------------------------------------------
49+
We have removed all mining code from Windows and Mac binaries, which should avoid most of the false-positive alerts
50+
from anti virus software. Linux builds are not affected. The mining code found in `dash-qt` and `dashd` are only meant
51+
for regression/integration tests and devnets, so there is no harm in removing this code from non-linux builds.
52+
53+
Fixed an issue with invalid merkle blocks causing SPV nodes to ban other nodes
54+
------------------------------------------------------------------------------
55+
A fix that was introduces in the last minor version caused creation of invalid merkle blocks, which in turn cause SPV
56+
nodes to ban 0.13.2 nodes. This can be observed on mobile clients which have troubles maintaining connections. This
57+
release fixes this issue and should allow SPV/mobile clients to sync with upgraded nodes.
58+
59+
Hardened spork15 value to 1047200
60+
---------------------------------
61+
We've hardened the spork15 block height to 1047200, which makes sure that syncing from scratch will always work, no
62+
matter if spork15 is received in-time or not.
8763

8864
Bug fixes/Other improvements
8965
----------------------------
9066
There are few bug fixes in this release:
91-
- Fixed a crash on shutdown
92-
- Fixed a misleading error message in the RPC "protx update_registrar"
93-
- Slightly speed up initial sync by not running DIP3 logic in old blocks
94-
- Add build number (CLIENT_VERSION_BUILD) to MacOS bundle information
67+
- Fixed an issue with transaction sometimes not being fully zapped when `-zapwallettxes` is used
68+
- Fixed an issue with the `protx revoke` RPC and REASON_CHANGE_OF_KEYS
9569

96-
0.13.2.0 Change log
70+
0.13.3.0 Change log
9771
===================
9872

99-
See detailed [set of changes](https://github.com/dashpay/dash/compare/v0.13.1.0...dashpay:v0.13.2.0).
73+
See detailed [set of changes](https://github.com/dashpay/dash/compare/v0.13.2.0...dashpay:v0.13.3.0).
10074

10175
### Backports
10276

103-
- [`548a48918`](https://github.com/dashpay/dash/commit/548a48918) Move IS block filtering into ConnectBlock (#2766)
104-
- [`6374dce99`](https://github.com/dashpay/dash/commit/6374dce99) Fix error message for invalid voting addresses (#2747)
105-
- [`25222b378`](https://github.com/dashpay/dash/commit/25222b378) Make -masternodeblsprivkey mandatory when -masternode is given (#2745)
106-
- [`0364e033a`](https://github.com/dashpay/dash/commit/0364e033a) Implement 2-stage commit for CEvoDB to avoid inconsistencies after crashes (#2744)
107-
- [`a11e2f9eb`](https://github.com/dashpay/dash/commit/a11e2f9eb) Add collateraladdress into masternode/protx list rpc output (#2740)
108-
- [`43612a272`](https://github.com/dashpay/dash/commit/43612a272) Only include selected TX types into CMerkleBlock (#2737)
109-
- [`f868fbc78`](https://github.com/dashpay/dash/commit/f868fbc78) Stop g_connman first before deleting it (#2734)
110-
- [`9e233f391`](https://github.com/dashpay/dash/commit/9e233f391) Fix incorrect usage of begin() when genesis block is requested in "protx diff" (#2699)
111-
- [`e75f971b9`](https://github.com/dashpay/dash/commit/e75f971b9) Do not process blocks in CDeterministicMNManager before dip3 activation (#2698)
112-
- [`1cc47ebcd`](https://github.com/dashpay/dash/commit/1cc47ebcd) Backport #14701: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString (#2687)
77+
- [`575cafc01`](https://github.com/dashpay/dash/commit/575cafc01) Do not skip pushing of vMatch and vHashes in CMerkleBlock (#2826)
78+
- [`8c58799d8`](https://github.com/dashpay/dash/commit/8c58799d8) There can be no two votes which differ by the outcome only (#2819)
79+
- [`66c2f3953`](https://github.com/dashpay/dash/commit/66c2f3953) Fix vote ratecheck (#2813)
80+
- [`b52d0ad19`](https://github.com/dashpay/dash/commit/b52d0ad19) Fix revoke reason check for ProUpRevTx (#2787)
81+
- [`35914e084`](https://github.com/dashpay/dash/commit/35914e084) Skip mempool.dat when wallet is starting in "zap" mode (#2782)
82+
- [`46d875100`](https://github.com/dashpay/dash/commit/46d875100) Disable in-wallet miner for win/macos Travis/Gitian builds (#2778)
11383

11484
### Other
11585

116-
- [`2516a6e19`](https://github.com/dashpay/dash/commit/2516a6e19) Bump version to 0.13.2
117-
- [`9dd16cdbe`](https://github.com/dashpay/dash/commit/9dd16cdbe) Bump minChainWork and AssumeValid to block #1033120 (#2750)
118-
- [`18f087b27`](https://github.com/dashpay/dash/commit/18f087b27) Fix some typos in doc/guide-startmany.md (#2711)
119-
- [`709ab6d3e`](https://github.com/dashpay/dash/commit/709ab6d3e) Minimal fix for litemode vs bad-protx-key-not-same issue (#2694)
86+
- [`25038ff36`](https://github.com/dashpay/dash/commit/25038ff36) Bump version to 0.13.3.0
87+
- [`53b2162e2`](https://github.com/dashpay/dash/commit/53b2162e2) Harden spork15 value to 1047200 when on mainnet (#2830)
12088

12189
Credits
12290
=======
12391

12492
Thanks to everyone who directly contributed to this release:
12593

12694
- Alexander Block (codablock)
127-
- Felix Yan (felixonmars)
128-
- PastaPastaPasta
95+
- gladcow
12996
- UdjinM6
13097

13198
As well as everyone that submitted issues and reviewed pull requests.
@@ -153,6 +120,7 @@ Dash Core tree 0.12.1.x was a fork of Bitcoin Core tree 0.12.
153120

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

123+
- [v0.13.2.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.13.2.0.md) released Mar/15/2019
156124
- [v0.13.1.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.13.1.0.md) released Feb/9/2019
157125
- [v0.13.0.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.13.0.0.md) released Jan/14/2019
158126
- [v0.12.3.4](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.3.4.md) released Dec/14/2018

‎doc/release-notes/dash/release-notes-0.13.2.md

+172
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,172 @@
1+
Dash Core version 0.13.2.0
2+
==========================
3+
4+
Release is now available from:
5+
6+
<https://www.dash.org/downloads/#wallets>
7+
8+
This is a new minor version release, bringing various bugfixes and other improvements.
9+
10+
Please report bugs using the issue tracker at github:
11+
12+
<https://github.com/dashpay/dash/issues>
13+
14+
15+
Upgrading and downgrading
16+
=========================
17+
18+
How to Upgrade
19+
--------------
20+
21+
If you are running an older version, shut it down. Wait until it has completely
22+
shut down (which might take a few minutes for older versions), then run the
23+
installer (on Windows) or just copy over /Applications/Dash-Qt (on Mac) or
24+
dashd/dash-qt (on Linux). If you upgrade after DIP0003 activation you will
25+
have to reindex (start with -reindex-chainstate or -reindex) to make sure
26+
your wallet has all the new data synced (only if you were using version < 0.13).
27+
28+
Note that there is no protocol bump in this version and thus active masternodes
29+
updating from v0.13.0.0 or v0.13.1.0 do not require any additional actions (no need to issue
30+
`masternode start` command).
31+
32+
Downgrade warning
33+
-----------------
34+
35+
### Downgrade to a version < 0.13.0.0
36+
37+
Downgrading to a version smaller than 0.13 is not supported anymore as DIP2/DIP3 has activated
38+
on mainnet and testnet.
39+
40+
### Downgrade to 0.13.0.0 or 0.13.1.0
41+
42+
Downgrading to 0.13.0.0 is fully supported but is not recommended unless you have some serious issues with 0.13.2.0.
43+
44+
Notable changes
45+
===============
46+
47+
Providing "masternodeblsprivkey" is now mandatory when the node is launched as a masternode ("masternode=1")
48+
------------------------------------------------------------------------
49+
In previous versions, "masternodeblsprivkey" was not mandatory as these versions had to function with and without DIP3
50+
activation. Now that DIP3 has activated on mainnet and testnet, we can make "masternodeblsprivkey" mandatory when
51+
configuring and running a masternode. Please note that your masternode will fail to start when "masternodeblsprivkey"
52+
is not specified. This also means that 0.13.2.0 will only work with masternodes which have already registered their
53+
DIP3 masternode. This enforcement was added to catch misconfigurations of masternodes which would otherwise stay
54+
unnoticed until spork 15 activation and thus surprise and hurt masternode owners.
55+
56+
Fix for consistency issues after sudden stopping of node
57+
--------------------------------------------------------
58+
Previous versions resulted in inconsistency between the chainstate and evodb when the node crashed or otherwise suddenly
59+
stopped (e.g. power failure). This should be fixed in 0.13.2.0.
60+
61+
Fix for litemode nodes to not reject specific DIP3 transactions
62+
---------------------------------------------------------------
63+
Previous versions might cause litemode nodes to reject the mainnet chain after spork 15 activation. This is due to a
64+
consensus rule being less strict in one specific case when spork 15 is active. Litemode nodes can not know about the
65+
change in consensus rules as they have no knowledge about sporks. In 0.13.2.0, when litemode is enabled, we default to the
66+
behaviour of activated spork15 in this specific case, which fixes the issue. The restriction will be completely removed
67+
in the next major release.
68+
69+
Fix incorrect behavior for "protx diff" and the P2P message "GETMNLISTDIFF"
70+
---------------------------------------------------------------------------
71+
Both were responding with errors when "0" was used as base block hash. DIP4 defines "0" to be equivalent with the
72+
genesis block, so that it's easy for peers to request the full masternode list.
73+
This is mostly important for SPV nodes (e.g. mobile wallets) which need the masternode list. Right now, all nodes in
74+
the network will respond with an error when "0" is provided in "GETMNLISTDIFF". Until enough masternodes have upgraded
75+
to 0.13.2.0, SPV nodes should use the full genesis hash to circumvent the error.
76+
77+
Exclusion of LLMQ quorum commitments from partial blocks
78+
--------------------------------------------------------
79+
SPV nodes are generally not interested in non-financial special transactions in blocks, so we're omitting them now when
80+
sending partial/filtered blocks to SPV clients. This currently only filters LLMQ quorum commitments, which also caused
81+
some SPV implementations to ban nodes as they were not able to process these. DIP3 transactions (ProRegTx, ProUpRegTx, ...)
82+
are not affected and are still included in partial/filtered blocks as these might also move funds.
83+
84+
RPC changes
85+
-----------
86+
`masternode list json` and `protx list` will now include the collateral address of masternodes.
87+
88+
Bug fixes/Other improvements
89+
----------------------------
90+
There are few bug fixes in this release:
91+
- Fixed a crash on shutdown
92+
- Fixed a misleading error message in the RPC "protx update_registrar"
93+
- Slightly speed up initial sync by not running DIP3 logic in old blocks
94+
- Add build number (CLIENT_VERSION_BUILD) to MacOS bundle information
95+
96+
0.13.2.0 Change log
97+
===================
98+
99+
See detailed [set of changes](https://github.com/dashpay/dash/compare/v0.13.1.0...dashpay:v0.13.2.0).
100+
101+
### Backports
102+
103+
- [`548a48918`](https://github.com/dashpay/dash/commit/548a48918) Move IS block filtering into ConnectBlock (#2766)
104+
- [`6374dce99`](https://github.com/dashpay/dash/commit/6374dce99) Fix error message for invalid voting addresses (#2747)
105+
- [`25222b378`](https://github.com/dashpay/dash/commit/25222b378) Make -masternodeblsprivkey mandatory when -masternode is given (#2745)
106+
- [`0364e033a`](https://github.com/dashpay/dash/commit/0364e033a) Implement 2-stage commit for CEvoDB to avoid inconsistencies after crashes (#2744)
107+
- [`a11e2f9eb`](https://github.com/dashpay/dash/commit/a11e2f9eb) Add collateraladdress into masternode/protx list rpc output (#2740)
108+
- [`43612a272`](https://github.com/dashpay/dash/commit/43612a272) Only include selected TX types into CMerkleBlock (#2737)
109+
- [`f868fbc78`](https://github.com/dashpay/dash/commit/f868fbc78) Stop g_connman first before deleting it (#2734)
110+
- [`9e233f391`](https://github.com/dashpay/dash/commit/9e233f391) Fix incorrect usage of begin() when genesis block is requested in "protx diff" (#2699)
111+
- [`e75f971b9`](https://github.com/dashpay/dash/commit/e75f971b9) Do not process blocks in CDeterministicMNManager before dip3 activation (#2698)
112+
- [`1cc47ebcd`](https://github.com/dashpay/dash/commit/1cc47ebcd) Backport #14701: build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString (#2687)
113+
114+
### Other
115+
116+
- [`2516a6e19`](https://github.com/dashpay/dash/commit/2516a6e19) Bump version to 0.13.2
117+
- [`9dd16cdbe`](https://github.com/dashpay/dash/commit/9dd16cdbe) Bump minChainWork and AssumeValid to block #1033120 (#2750)
118+
- [`18f087b27`](https://github.com/dashpay/dash/commit/18f087b27) Fix some typos in doc/guide-startmany.md (#2711)
119+
- [`709ab6d3e`](https://github.com/dashpay/dash/commit/709ab6d3e) Minimal fix for litemode vs bad-protx-key-not-same issue (#2694)
120+
121+
Credits
122+
=======
123+
124+
Thanks to everyone who directly contributed to this release:
125+
126+
- Alexander Block (codablock)
127+
- Felix Yan (felixonmars)
128+
- PastaPastaPasta
129+
- UdjinM6
130+
131+
As well as everyone that submitted issues and reviewed pull requests.
132+
133+
Older releases
134+
==============
135+
136+
Dash was previously known as Darkcoin.
137+
138+
Darkcoin tree 0.8.x was a fork of Litecoin tree 0.8, original name was XCoin
139+
which was first released on Jan/18/2014.
140+
141+
Darkcoin tree 0.9.x was the open source implementation of masternodes based on
142+
the 0.8.x tree and was first released on Mar/13/2014.
143+
144+
Darkcoin tree 0.10.x used to be the closed source implementation of Darksend
145+
which was released open source on Sep/25/2014.
146+
147+
Dash Core tree 0.11.x was a fork of Bitcoin Core tree 0.9,
148+
Darkcoin was rebranded to Dash.
149+
150+
Dash Core tree 0.12.0.x was a fork of Bitcoin Core tree 0.10.
151+
152+
Dash Core tree 0.12.1.x was a fork of Bitcoin Core tree 0.12.
153+
154+
These release are considered obsolete. Old release notes can be found here:
155+
156+
- [v0.13.1.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.13.1.0.md) released Feb/9/2019
157+
- [v0.13.0.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.13.0.0.md) released Jan/14/2019
158+
- [v0.12.3.4](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.3.4.md) released Dec/14/2018
159+
- [v0.12.3.3](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.3.3.md) released Sep/19/2018
160+
- [v0.12.3.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.3.2.md) released Jul/09/2018
161+
- [v0.12.3.1](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.3.1.md) released Jul/03/2018
162+
- [v0.12.2.3](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.2.3.md) released Jan/12/2018
163+
- [v0.12.2.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.2.2.md) released Dec/17/2017
164+
- [v0.12.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.2.md) released Nov/08/2017
165+
- [v0.12.1](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.1.md) released Feb/06/2017
166+
- [v0.12.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.0.md) released Aug/15/2015
167+
- [v0.11.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.11.2.md) released Mar/04/2015
168+
- [v0.11.1](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.11.1.md) released Feb/10/2015
169+
- [v0.11.0](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.11.0.md) released Jan/15/2015
170+
- [v0.10.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.10.0.md) released Sep/25/2014
171+
- [v0.9.x](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.9.0.md) released Mar/13/2014
172+

0 commit comments

Comments
 (0)