{"id":106154,"date":"2023-04-10T13:17:44","date_gmt":"2023-04-10T13:17:44","guid":{"rendered":"https:\/\/wp.dash.org\/?p=106154"},"modified":"2023-04-17T17:28:08","modified_gmt":"2023-04-17T17:28:08","slug":"dashcore-v19-0-product-brief","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/blog\/dashcore-v19-0-product-brief\/","title":{"rendered":"DashCore v19.0 Product Brief"},"content":{"rendered":"
DashCore v19.0 is a major release and will be a mandatory upgrade for all masternodes, miners, and users. Version 19.0 introduces a number of features and improvements to Dash, including the BLS scheme migration, high-performance masternode implementation, wallet improvements, and numerous enhancements through Bitcoin backports. Below are a few key highlights of this release. Comprehensive details will be found in the release notes.<\/span><\/p>\n In preparation for the release of Dash Platform to mainnet, a new masternode has been added. High-performance masternodes<\/a> will be responsible for hosting Dash Platform services (once they are on mainnet) and existing features like <\/span>ChainLocks<\/span><\/a> and <\/span>InstantSend<\/span><\/a>.<\/span><\/p>\n Activation of the DashCore v19.0 hard fork will enable registration of the new 4000 DASH collateral masternodes. Until Dash Platform is released to mainnet, high-performance masternodes will provide the same services as regular masternodes with one small exception. Regular masternodes will no longer participate in the Platform-specific LLMQ after the hard fork since they will not be responsible for hosting Dash Platform.<\/span><\/p>\n Note: In DashCore v19.0 the relative rewards and voting power are equivalent between regular and high-performance masternodes. Masternodes effectively receive one payout and one governance vote per 1000 DASH collateral. So, there is no difference in reward amount for running four regular masternodes or one high-performance masternode. In v19.0, high-performance masternodes simply receive payments in four consecutive blocks when they are selected for payout. Some frequently asked questions may be found at <\/span>https:\/\/www.dash.org\/hpmn-faq\/<\/span><\/a>.<\/span><\/em><\/p>\n DashCore\u2019s default BLS scheme<\/a>\u00a0has been changed to better align with standards and improve security. This is the continuation of an effort that started in a previous release. Upon activation of DashCore v19\u2019s hard fork, the network will transition to using the BLS basic scheme rather than the previously used \u201clegacy\u201d scheme. As a result, BLS public keys and signatures in network messages, special transactions, etc. will be serialized using the new scheme.<\/span><\/p>\n Several wallet modifications have been included in this release. Dash Core will no longer automatically create new wallets on startup. It will load existing wallets specified by `-wallet` options on the command line or in `dash.conf` or `settings.json` files. And by default it will also load a top-level unnamed (“”) wallet. However, if specified wallets don’t exist, Dash Core will now just log warnings instead of creating new wallets with new keys and addresses like previous releases did.<\/span><\/p>\n New wallets can be created through the GUI (which has a more prominent create wallet option), through the `dash-wallet create` command, or the `createwallet` RPC.<\/span><\/p>\n Transactions that appear \u201cstuck\u201d will now be re-sent after one hour on average rather than the extended 24 hour delay that was previously in place. The lack of congestion on the Dash network allowed reducing the timeframe without performance concerns.<\/span><\/p>\nRelease Highlights<\/span><\/h2>\n
High-Performance Masternodes<\/span><\/h3>\n
BLS scheme migration<\/span><\/h3>\n
Wallet improvements<\/span><\/h2>\n
CoinJoin update<\/span><\/h3>\n