neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
b12426c517
neobytes/doc/release-notes/dash/release-notes-0.14.0.5.md
UdjinM6 617c588488
v0.15 release notes draft (#3283) 
* Archive 0.14.0.5 release notes

* v0.15 release notes draft

* Apply suggestions from code review

Thanks @thephez!

Co-Authored-By: thephez <thephez@users.noreply.github.com>

* Apply suggestions from code review

Co-Authored-By: thephez <thephez@users.noreply.github.com>

* Fixes and additions to release notes

* Add "Crash reports and stack traces" section

* Few clarifications

Co-authored-by: thephez <thephez@users.noreply.github.com>
Co-authored-by: Alexander Block <ablock84@gmail.com>
2020-01-14 22:46:02 +03:00

8.3 KiB
Raw Blame History

Dash Core version 0.14.0.5

Release is now available from:

https://www.dash.org/downloads/#wallets

This is a new minor version release, bringing various bugfixes and improvements. It is highly recommended to upgrade to this release as it contains a critical fix for a possible DoS vector.

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). If you upgrade after DIP0003 activation and you were 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.

When upgrading from a version prior to 0.14.0.3, the first startup of Dash Core will run a migration process which can take a few minutes to finish. After the migration, a downgrade to an older version is only possible with a reindex (or reindex-chainstate).

Downgrade warning

Downgrade to a version < 0.14.0.3

Downgrading to a version smaller than 0.14.0.3 is not supported anymore due to changes in the "evodb" database format. If you need to use an older version, you have to perform a reindex or re-sync the whole chain.

Notable changes

Fix for a DoS vector

This release fixes a serious DoS vector which allows to cause memory exhaustion until the point of out-of-memory related crashes. We highly recommend upgrading all nodes. Thanks to Bitcoin ABC developers for finding and reporting this issue to us.

Better handling of non-locked transactions in mined blocks

We observed multiple cases of ChainLocks failing on mainnet. We tracked this down to a situation where PrivateSend mixing transactions were first rejected by parts of the network (0.14.0.4 nodes) while other parts (<=0.14.0.3) accepted the transaction into the mempool. This caused InstantSend locking to fail for these transactions, while non-upgraded miners still included the transactions into blocks after 10 minutes. This caused blocks to not get ChainLocked for at least 10 minutes. This release improves an already existent fallback mechanism (retroactive InstantSend locking) to also work for transaction which are already partially known in the network. This should cause ChainLocks to succeed in such situations.

0.14.0.5 Change log

See detailed set of changes.

  • 20d4a27778 Make sure mempool txes are properly processed by CChainLocksHandler despite node restarts (#3230)
  • dc07a0c5e1 [v0.14.0.x] Bump version and prepare release notes (#3228)
  • 401da32090 More fixes in llmq-is-retroactive tests
  • 33721eaa11 Make llmq-is-retroactive test compatible with 0.14.0.x
  • 85bd162a3e Make wait_for_xxx methods compatible with 0.14.0.x
  • 22cfddaf12 Allow re-signing of IS locks when performing retroactive signing (#3219)
  • a8b8891a1d Add wait_for_xxx methods as found in develop
  • 8dae12cc60 More/better logging for InstantSend
  • fdd19cf667 Tests: Fix the way nodes are connected to each other in setup_network/start_masternodes (#3221)
  • 41f0e9d028 More fixes related to extra_args
  • 5213118601 Tests: Allow specifying different cmd-line params for each masternode (#3222)
  • 2fef21fd80 Don't join thread in CQuorum::~CQuorum when called from within the thread (#3223)
  • e69c6c3207 Merge #12392: Fix ignoring tx data requests when fPauseSend is set on a peer (#3225)

Credits

Thanks to everyone who directly contributed to this release:

  • Alexander Block (codablock)
  • UdjinM6

As well as everyone that submitted issues and reviewed pull requests.

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: