December 14, 2019 11:14 pm

Product Update — December 14, 2019

Hello Dash Community!

In all the excitement getting ready for this past weekend’s Open House, we realized we skipped our weekly product update last week. I’ve combined the past two weeks here for you.

It was great meeting several of you at the Open House and sharing ideas on the future of Dash. If you weren’t able to join us, please make sure you check out the stream at!

Here’s what’s been going on the past couple weeks at Dash Core Group.

Week of December 12, 2019

🚀 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

🖋 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.

  • When this happens, the part of the network that sees it via the mempool might run into timeouts for the signing sessions, which causes the session to never be completed even if the other part of the network signs it when it receives the transaction via a block.
  • With this change, the first part of the network will re-sign the transaction when necessary at the time it receives the block so that the InstantSend lock will happen correctly.

🇹🇭 Launched Dash website in Thai.

🚎 Updated data triggers in DPP, which are functions that automatically execute based on data being added, read, deleted, or changed in the DPNS platform application. A precursor to smart contract functionality.

🎨 Implemented several updates on DashWallet iOS and Android as part of the UI redesign, such as the Hide Balance, Invalid PIN entry, Advanced Security (iOS) and Device Lock (Android) screens, among several others.

Week of December 5, 2019

✉️ Made some tweaks to the ‘Send’ popup message in DashQT Wallet, including highlighting when not all recipients of a transaction are displayed, clarified text explaining fee rounding in PrivateSend, display of transaction size and actual fee rate, and the number of inputs a PrivateSend transaction is going to consume with a warning if it exceeds 10 to let users know that it may reduce privacy by making it easier to track these funds back to the original wallet via clustering analysis.

🥅 Implemented state transition signing and verification logic in Dash Platform Protocol (DPP), which will allow for state transitions such as when a user’s contact list is updated.

🤸‍♂️ Updated Dash Platform Protocol (DPP) and Drive to use Identities, rather than Blockchain Users (the previous implementation).

☝️ Fixed a fingerprint bug in DashWallet Android and updated the Network Monitor and Transaction History/Status screens as part of the UI redesign.

About the author

Elizabeth Robuck