v19.0.0-beta.1

This is a beta and is not meant for production. It is only meant for testnet / devnet deployments.

This release was signed by keybase.io/pasta.

Notable changes since v18.2.0: TBD

Release notes will be released in the near future.

P2P and network changes

Removal of reject network messages from Dash Core (BIP61)

The command line option to enable BIP61 (-enablebip61) has been removed.

This feature has been disabled by default since Dash Core version 0.19.0.
Nodes on the network can not generally be trusted to send valid ("reject")
messages, so this should only ever be used when connected to a trusted node.
Please use the recommended alternatives if you rely on this deprecated feature:

• Testing or debugging of implementations of the Dash P2P network protocol
  should be done by inspecting the log messages that are produced by a recent
  version of Dash Core. Dash Core logs debug messages
  (-debug=<category>) to a stream (-printtoconsole) or to a file
  (-debuglogfile=<debug.log>).

• Testing the validity of a block can be achieved by specific RPCs:

  • submitblock
  • getblocktemplate with 'mode' set to 'proposal' for blocks with
    potentially invalid POW

• Testing the validity of a transaction can be achieved by specific RPCs:

  • sendrawtransaction
  • testmempoolaccept

• Wallets should not use the absence of "reject" messages to indicate a
  transaction has propagated the network, nor should wallets use "reject"
  messages to set transaction fees. Wallets should rather use fee estimation
  to determine transaction fees and set replace-by-fee if desired. Thus, they
  could wait until the transaction has confirmed (taking into account the fee
  target they set (compare the RPC estimatesmartfee)) or listen for the
  transaction announcement by other network peers to check for propagation.

Wallet

Dash Core will no longer create an unnamed "" wallet by default when no wallet is specified on the command line or in the configuration files.
For backwards compatibility, if an unnamed "" wallet already exists and would have been loaded previously, then it will still be loaded.
Users without an unnamed "" wallet and without any other wallets to be loaded on startup will be prompted to either choose a wallet to load, or to create a new wallet.

Automatic wallet creation removed

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.

New wallets can be created through the GUI (which has a more prominent create
wallet option), through the dash-cli createwallet or dash-wallet create commands, or the createwallet RPC.

Updated RPCs

• masternodelist New mode recent was added in order to hide banned masternodes for more than one SuperblockCycle. If the mode recent is used, then the reply mode is JSON (can be additionally filtered)