{"id":44119,"date":"2019-12-10T08:31:56","date_gmt":"2019-12-10T08:31:56","guid":{"rendered":"https:\/\/www2019.dash.org\/?p=44119"},"modified":"2021-09-18T11:42:31","modified_gmt":"2021-09-18T11:42:31","slug":"dash-release-0-14-0-5","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/dash-release-0-14-0-5\/","title":{"rendered":"Dash release 0.14.0.5"},"content":{"rendered":"
We are happy to announce the release of 0.14.0.5. This release includes binaries, which can be downloaded at # About this Release<\/p>\n Dash Core 0.14.0.5 is a minor release of the Dash Core 0.14.0.x series.<\/p>\n This is a new minor version release, bringing various bugfixes and improvements. We consider this a stable release. We suggest every node (including masternodes and non-masternode) operator to upgrade to 0.14.0.5 as this release contains a fix for a serious DoS vector.<\/p>\n Notable changes Fix for a DoS vector This release fixes a serious DoS vector which allows to cause memory exhaustion until the point of 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 # Credits<\/p>\n Thanks go out to all Dash Core contributors, everyone who submitted issues, reviewed pull requests or helped translating on [Transifex](https:\/\/www.transifex.com\/projects\/p\/dash\/<\/a>) and also to [Bitcoin Core](https:\/\/github.com\/bitcoin\/bitcoin<\/a>) Developers.“`<\/p>\n
\nhttps:\/\/www.dash.org\/downloads\/<\/a><\/p>\n
\n===============<\/p>\n
\n——————–<\/p>\n
\nout-of-memory related crashes. We highly recommend upgrading all nodes. Thanks to Bitcoin ABC
\ndevelopers for finding and reporting this issue to us.<\/p>\n
\n———————————————————-<\/p>\n
\nPrivateSend mixing transactions were first rejected by parts of the network (0.14.0.4 nodes) while other parts
\n(<=0.14.0.3) accepted the transaction into the mempool. This caused InstantSend locking to fail for these
\ntransactions, while non-upgraded miners still included the transactions into blocks after 10 minutes.
\nThis caused blocks to not get ChainLocked for at least 10 minutes. This release improves an already existent
\nfallback mechanism (retroactive InstantSend locking) to also work for transaction which are already partially
\nknown in the network. This should cause ChainLocks to succeed in such situations.<\/p>\n