{"id":70705,"date":"2019-12-14T23:14:00","date_gmt":"2019-12-14T23:14:00","guid":{"rendered":"https:\/\/www.dash.org\/uncategorized\/product-update-december-14-2019\/"},"modified":"2021-09-23T14:59:45","modified_gmt":"2021-09-23T14:59:45","slug":"product-update-december-14-2019","status":"publish","type":"post","link":"https:\/\/www.dash.org\/blog\/product-update-december-14-2019\/","title":{"rendered":"Product Update \u2014 December 14, 2019"},"content":{"rendered":"

Hello Dash Community!<\/p>\n

In all the excitement getting ready for this past weekend\u2019s Open House, we realized we skipped our weekly product update last week. I\u2019ve combined the past two weeks here for you.<\/p>\n

It was great meeting several of you at the Open House and sharing ideas on the future of Dash. If you weren\u2019t able to join us, please make sure you check out the stream at dash.org\/live!<\/p>\n

Here\u2019s what\u2019s been going on the past couple weeks at Dash Core Group.<\/p>\n


\n

Week of December 12, 2019<\/h2>\n

\ud83d\ude80 Release DashCore v0.14.0.5, which will fix some ChainLocks issues observed on mainnet and a recently identified DoS attack vector. All nodes are encouraged to update. Download the new version at dash.org\/downloads.<\/p>\n

\ud83d\udd8b Implemented re-signing of InstantSend locks, which only happens when a non-locked transaction appears in a new block. This is required to make retroactive signing work when parts of the network have already seen the transaction in the mempool, and other parts only see it first in a block.<\/p>\n