Dash Core 0.14.0.0 Release Announcement
We are happy to announce the release of 0.14.0.0. This release includes binaries, which can be downloaded above.
About this Release
Dash Core 0.14.0.0 is the first major release of the Dash Core 0.14.x.x series.
This major release contains new features, improvements and bugfixes and we consider this a stable release.
DIP0004 - Coinbase Payload v2
Coinbase Payload v2 introduces new field
merkleRootQuorums which represents the merkle root of all the hashes of the final quorum commitments of all active LLMQ sets. This allows SPV clients to verify active LLMQ sets and use this information to further verify ChainLocks and LLMQ-based InstantSend messages. Coinbase Payload v2 relies on DIP0008 (bit 4) activation.
DIP0008 - ChainLocks
This version introduces ChainLocks, a technology for near-instant confirmation of blocks and finding near-instant consensus on the longest valid/accepted chain. ChainLocks leverages LLMQ Signing Requests/Sessions to accomplish this. ChainLocks relies on DIP0008 (bit 4) activation and
DIP0010 - LLMQ-based InstantSend
InstantSend is a feature to allow instant confirmations of payments. It works by locking transaction inputs through masternode quorums. It has been present in Dash for a few years and been proven to work. Nevertheless, there are some limits which could theoretically be removed in the old system but doing so would have created risks in terms of scalability and security.
We introduce LLMQ-based InstantSend which is designed to be much more scalable without sacrificing security and which allows all transactions to be treated as InstantSend transactions. The old system differentiated transactions as InstantSend transactions by using the P2P message “ix” instead of “tx”. Since this distinction is not required in the new system, the P2P message “ix” will be removed after DIP0008 deployment (for now, transactions sent via "ix" message will be relayed further via "tx" message).
qdcommit and their corresponding inventory types (7, 10, 14, 15, 19, 22) are no longer suported.
version is extended with a 256 bit field - a challenge sent to a masternode. Masternode which received such a challenge must reply with new p2p message
mnauth directly after
mnauth message must include a signed challenge that was previously sent via
Due to changes in coinbase payload this version requires for miners to signal their readiness via BIP9-like mechanism - by setting bit 4 of the block version to 1. Note that if your mining software simply uses
coinbase_payload field from
getblocktemplate RPC and doesn't construct coinbase payload manually then there should be no changes to your mining software required. We however encourage pools and solo-miners to check their software compatibility on testnet to ensure flawless migration.
The wallet will try to create and consume denoms a bit more accurately now. It will also only create a limited number of inputs for each denominated amount to prevent bloating itself with mostly the smallest denoms. You can control this number of inputs via new
-privatesenddenoms cmd-line option (default is 300).
Legacy InstantSend is going to be superseded by the newly implemented LLMQ-based one once DIP0008 (bit 4) is active and
SPORK_20_INSTANTSEND_LLMQ_BASED spork is ON.
There are two new sporks introduced in this version -
SPORK_17_QUORUM_DKG_ENABLED was introduced in v0.13 but was kept OFF. It will be turned on once 80% masternodes are upgraded to v0.14 which will enable DKG and DKG-based PoSe.
Wallet can now show QR codes for addresses in the address book, receiving addresses and addresses identified in transactions list (right click -> "Show QR-code").
RPC, ZMQ and command-line changes
This release introduced various changes to these subsystems, please see detailed release notes for more info.
You can find detailed release notes at https://github.com/dashpay/dash/blob/v0.14.0.0/doc/release-notes.md. The release notes also contain instructions and links to further documentation for masternode operators and miners.