Skip to content

v18.2.0-beta.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@PastaPastaPasta PastaPastaPasta released this 18 Oct 23:42
· 2865 commits to master since this release
v18.2.0-beta.1
This tag was signed with the committer’s verified signature.
PastaPastaPasta
GPG key ID: 52527BEDABE87984
Learn about vigilant mode.
ad88fab
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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

Changelog since 18.1.0: v18.1.0...v18.2.0-beta.1

This release was signed by keybase.io/pasta.

Notable Changes

BREAKING: Wallet

Automatic wallet loading (bitcoin#15454)

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 for wallets specified in a launch parameter (bitcoin#20186)

Dash Core will no longer automatically create new wallets on startup via -wallet. 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.

New RPCs

  • analyzepsbt examines a PSBT and provides information about what
    the PSBT contains and the next steps that need to be taken in order
    to complete the transaction. For each input of a PSBT, analyzepsbt
    provides information about what information is missing for that
    input, including whether a UTXO needs to be provided, what pubkeys
    still need to be provided, which scripts need to be provided, and
    what signatures are still needed. Every input will also list which
    role is needed to complete that input, and analyzepsbt will also
    list the next role in general needed to complete the PSBT.
    analyzepsbt will also provide the estimated fee rate and estimated
    virtual size of the completed transaction if it has enough
    information to do so. (#5017)
  • balances RPC introduced by 078094b
Assets 18