```{eval-rst} .. meta:: :title: Removed RPCs :description: A list of RPCs that have recently been removed from Dash Core. ``` # Removed RPCs ## EstimateFee >❗️**Warning:** **_Removed in Dash Core 0.17.0._** The `estimatefee` RPC estimates the transaction fee per kilobyte that needs to be paid for a transaction to begin confirmation within a certain number of blocks. _Parameter #1---how many blocks the transaction may wait before being included_ Name | Type | Presence | Description --- | --- | --- | --- Blocks | number (int) | Required
(exactly 1) | The maximum number of blocks a transaction should have to wait before it is predicted to be included in a block. Has to be between 2 and 25 blocks _Result---the fee the transaction needs to pay per kilobyte_ >❗️ Inability to estimate > > If the node doesn't have enough information to make an estimate, the value `-1` will be returned. Name | Type | Presence | Description --- | --- | --- | --- `result` | number (Dash) | Required
(exactly 1) | The estimated fee the transaction should pay in order to be included within the specified number of blocks. _Examples from Dash Core 0.12.2_ ``` bash dash-cli estimatefee 6 ``` Result: ``` json 0.00044345 ``` Requesting data the node can't calculate (out of range): ``` bash dash-cli estimatefee 100 ``` Result: ``` json -1 ``` _See also_ * [SetTxFee](../api/remote-procedure-calls-wallet.md#settxfee): sets the transaction fee per kilobyte paid by transactions created by this wallet. ## GetPoolInfo The `getpoolinfo` RPC returns an object containing CoinJoin pool related information. _Parameters: none_ _Result---information about the CoinJoin pool_ Name | Type | Presence | Description --- | --- | --- | --- `result` | object | Required
(exactly 1) | Information about the pool →
`state` | string | Required
(exactly 1) | Pool state. Will be one of the following:
• `IDLE`
• `QUEUE`
• `ACCEPTING_ENTRIES`
• `SIGNING`
• `ERROR`
• `SUCCESS`
• `UNKNOWN`
→
`mixing_mode` | string | Required
(exactly 1) | One of the following:
• `normal`
• `multi-session`
→
`queue` | number (int) | Required
(exactly 1) | Queue size →
`entries` | number (int) | Required
(exactly 1) | The number of entries →
`status` | string | Required
(exactly 1) | A more detailed description of the current state →
`outpoint` | string (hex) | Optional
(exactly 1) | Previous output →
`addr` | string | Optional
(exactly 1) | Address →
`keys_left` | number (int) | Optional
(exactly 1) | The number of keys left in the local wallet →
`warnings` | number (int) | Optional
(exactly 1) | Warnings related to local wallet _Example from Dash Core 0.12.2_ ``` bash dash-cli -testnet getpoolinfo ``` Result: ``` json { "state": "IDLE", "mixing_mode": "normal", "queue": 0, "entries": 0, "status": "PrivateSend is idle.", "keys_left": 617, "warnings": "" } ``` ``` json { "state": "QUEUE", "mixing_mode": "normal", "queue": 1, "entries": 0, "status": "Submitted to masternode, waiting in queue .", "outpoint": "e3a6b7878a7e9413898bb379b323c521676f9d460db17ec3bf42d9ac0c9a432f-1", "addr": "217.182.229.146:19999", "keys_left": 571, "warnings": "" } ``` ``` json { "state": "ERROR", "mixing_mode": "normal", "queue": 0, "entries": 0, "status": "PrivateSend request incomplete: Session timed out. Will retry...", "keys_left": 571, "warnings": "" } ``` _See also:_ ## GetReceivedByAccount >❗️**Warning:** **_Removed in Dash Core 18.0.0_** > 📘 > > Requires [wallet](../resources/glossary.md#wallet) support (**unavailable on masternodes**) The `getreceivedbyaccount` RPC returns the total amount received by addresses in a particular account from transactions with the specified number of confirmations. It does not count coinbase transactions. _Parameter #1---the account name_ Name | Type | Presence | Description --- | --- | --- | --- Account | string | Required
(exactly 1) | The name of the account containing the addresses to get. For the default account, use an empty string (\\")" _Parameter #2---the minimum number of confirmations_ Name | Type | Presence | Description --- | --- | --- | --- Confirmations | number (int) | Optional
(0 or 1) | The minimum number of confirmations an externally-generated transaction must have before it is counted towards the balance. Transactions generated by this node are counted immediately. Typically, externally-generated transactions are payments to this wallet and transactions generated by this node are payments to other wallets. Use `0` to count unconfirmed transactions. Default is `1` _Parameter #3---whether to include transactions locked via InstantSend_ Name | Type | Presence | Description --- | --- | --- | --- addlocked | bool | Optional
(exactly 1) | Add the balance from InstantSend locked transactions (default=false) _Result---the number of dash received_ Name | Type | Presence | Description --- | --- | --- | --- `result` | number (dash) | Required
(exactly 1) | The number of dash received by the account. May be `0` _Example from Dash Core 0.12.2_ Get the dash received by the "doc test" account with six or more confirmations: ``` bash dash-cli -testnet getreceivedbyaccount "doc test" 6 ``` Result: ``` json 0.30000000 ``` _See also_ * [GetReceivedByAddress](../api/remote-procedure-calls-wallet.md#getreceivedbyaddress): returns the total amount received by the specified address in transactions with the specified number of confirmations. It does not count coinbase transactions. * [GetAddressesByAccount](../api/remote-procedure-calls-wallet-deprecated.md#getaddressesbyaccount): returns a list of every address assigned to a particular account. * [ListAccounts](../api/remote-procedure-calls-removed.md#listaccounts): lists accounts and their balances. ## GObject Vote-conf >❗️**Warning:** **Removed in Dash Core 20.0.0** The `gobject vote-conf` RPC votes on a governance object by masternode configured in dash.conf. *Parameter #1---governance hash* | Name | Type | Presence | Description | | ----------------- | ------------ | ----------------------- | ----------------------------- | | `governance-hash` | string (hex) | Required
(exactly 1) | Hash of the governance object | *Parameter #2---vote signal* | Name | Type | Presence | Description | | -------- | ------ | ----------------------- | -------------------------------------------- | | `signal` | string | Required
(exactly 1) | Vote signal: `funding`, `valid`, or `delete` | *Parameter #3---vote outcome* | Name | Type | Presence | Description | | --------- | ------ | ----------------------- | --------------------------------------- | | `outcome` | string | Required
(exactly 1) | Vote outcome: `yes`, `no`, or `abstain` | *Result---votes for specified governance* | Name | Type | Presence | Description | | ------------------ | ------ | ----------------------- | ----------------------------------------- | | Result | object | Required
(exactly 1) | The governance object votes | | →
`overall` | string | Required
(1 or more) | Reports number of vote successes/failures | | →
`detail` | object | Required
(exactly 1) | Vote details | | → →
`dash.conf` | object | Required
(1 or more) | | | → → →
`result` | string | Required
(exactly 1) | Vote result | *Example from Dash Core 0.12.2* ``` bash dash-cli -testnet gobject vote-conf \ 0bf97bce78b3b642c36d4ca8e9265f8f66de8774c220221f57739c1956413e2b funding yes ``` ``` json { "overall": "Voted successfully 1 time(s) and failed 0 time(s).", "detail": { "dash.conf": { "result": "success" } } } ``` ## KeePass >❗️**Warning:** **_Removed in Dash Core 18.0.0_** The `keepass` RPC provides commands for configuring and managing KeePass authentication _Parameter #1---Command mode_ Name | Type | Presence | Description --- | --- | --- | --- `mode` | string | Required (exactly 1) | The command mode to use:
`genkey`,
`init`,
`setpassphrase` _Command Options_ | Mode | Description | | --- | --- | | `genkey` | Generates a base64 encoded 256 bit AES key that can be used for the communication with KeePassHttp. This is only necessary for manual configuration. | `init` | Sets up the association between Dash Core and KeePass by generating an AES key and sending an association message to KeePassHttp. This will trigger KeePass to ask for an Id for the association. Returns the association and the base64 encoded string for the AES key. | `setpassphrase` | Updates the passphrase in KeePassHttp to a new value. This should match the passphrase you intend to use for the wallet. Please note that the standard RPC commands walletpassphrasechange and the wallet encryption from the QT GUI already send the updates to KeePassHttp, so this is only necessary for manual manipulation of the password. **Command Mode - `genkey`** _Result---the new key_ Name | Type | Presence | Description --- | --- | --- | --- Result | string (base64) | Required (exactly 1) | The new key _Example from Dash Core 0.12.2_ Manually generate a key ```bash dash-cli -testnet keepass genkey ``` Result: ```bash Generated Key: dNjo+J8Jb30txbJiKq4s9H6vEgWq/whb1w9bb2cTOFo= ``` **Command Mode - `init`** _Result---initialization response_ Name | Type | Presence | Description --- | --- | --- | --- Result | string | Required (exactly 1) | The success/error status _Example from Dash Core 0.12.2_ Automatically initialize ```bash dash-cli -testnet keepass init ``` Result (wrapped): ```bash Association successful. Id: testwalletassociation - \ Key: MSb+JLygqz7ZH40SyJ1QR62i00IXoa3tmT85MGGI2K0= ``` **Command Mode - `setpassphrase`** _Parameter #2---Passphrase_ Name | Type | Presence | Description --- | --- | --- | --- Passphrase | string | Required (exactly 1) | The passphrase to set _Result---status_ Name | Type | Presence | Description --- | --- | --- | --- Result | string | Required (exactly 1) | The success/error status _Example from Dash Core 0.12.2_ Set KeePass passphrase ```bash dash-cli -testnet keepass setpassphrase 1BWi20Xyk76uWumxJQy4 ``` Result: ```bash setlogin: Updated credentials. ``` _See also: none_ ## ListAccounts >❗️**Warning:** **_Removed in Dash Core 18.0.0_** > 📘 > > Requires [wallet](../resources/glossary.md#wallet) support (**unavailable on masternodes**) The `listaccounts` RPC lists accounts and their balances. _Parameter #1---the minimum number of confirmations a transaction must have_ Name | Type | Presence | Description --- | --- | --- | --- Confirmations | number (int) | Optional
(0 or 1) | The minimum number of confirmations an externally-generated transaction must have before it is counted towards the balance. Transactions generated by this node are counted immediately. Typically, externally-generated transactions are payments to this wallet and transactions generated by this node are payments to other wallets. Use `0` to count unconfirmed transactions. Default is `1` _Parameter #2--- whether to include transactions locked via InstantSend_ Name | Type | Presence | Description --- | --- | --- | --- addlocked | bool | Optional
(exactly 1) | Add the balance from InstantSend locked transactions _Parameter #3---whether to include watch-only addresses in results_ Name | Type | Presence | Description --- | --- | --- | --- Include Watch-Only | bool | Optional
(0 or 1) | If set to `true`, include watch-only addresses in details and calculations as if they were regular addresses belonging to the wallet. If set to `false` (the default), treat watch-only addresses as if they didn't belong to this wallet _Result---a list of accounts and their balances_ Name | Type | Presence | Description --- | --- | --- | --- `result` | object | Required
(exactly 1) | A JSON array containing key/value pairs with account names and values. Must include, at the very least, the default account (\\")" →
Account : Balance | string : number (dash) | Required
(1 or more) | The name of an account as a string paired with the balance of the account as a number of dash. The number of dash may be negative if the account has spent more dash than it received. Accounts with zero balances and zero transactions will be displayed _Example from Dash Core 0.13.0_ Display account balances with one confirmation and watch-only addresses included. Add the balance of InstantSend locked transactions also. ``` bash dash-cli -testnet listaccounts 1 true true ``` Result: ``` json { "": -2941.30029732, "Watching": 8.50000000, "MN": 2000.25442744, "PS": 37.02970000, "Recv1": 3843.48167912, } ``` _See also_ * [GetAccount](../api/remote-procedure-calls-wallet-deprecated.md#getaccount): returns the name of the account associated with the given address. * [GetAddressesByAccount](../api/remote-procedure-calls-wallet-deprecated.md#getaddressesbyaccount): returns a list of every address assigned to a particular account. * [ListReceivedByAccount](../api/remote-procedure-calls-removed.md#listreceivedbyaccount): lists the total number of dash received by each account. * [ListReceivedByLabel](../api/remote-procedure-calls-wallet.md#listreceivedbylabel): lists the total number of dash received by each label. ## ListReceivedByAccount >❗️**Warning:** **_Removed in Dash Core 18.0.0_** > 📘 > > Requires [wallet](../resources/glossary.md#wallet) support (**unavailable on masternodes**) The `listreceivedbyaccount` RPC lists the total number of dash received by each account. _Parameter #1---the minimum number of confirmations a transaction must have to be counted_ Name | Type | Presence | Description --- | --- | --- | --- Confirmations | number (int) | Optional
(0 or 1) | The minimum number of confirmations an externally-generated transaction must have before it is counted towards the balance. Transactions generated by this node are counted immediately. Typically, externally-generated transactions are payments to this wallet and transactions generated by this node are payments to other wallets. Use `0` to count unconfirmed transactions. Default is `1` _Parameter #2---whether to include transactions locked via InstantSend_ Name | Type | Presence | Description --- | --- | --- | --- addlocked | bool | Optional
(exactly 1) | Add the balance from InstantSend locked transactions _Parameter #3---whether to include empty accounts_ Name | Type | Presence | Description --- | --- | --- | --- Include Empty | bool | Optional
(0 or 1) | Set to `true` to display accounts which have never received a payment. Set to `false` (the default) to only include accounts which have received a payment. Any account which has received a payment will be displayed even if its current balance is `0` _Parameter #4---whether to include watch-only addresses in results_ Name | Type | Presence | Description --- | --- | --- | --- Include Watch-Only | bool | Optional
(0 or 1) | If set to `true`, include watch-only addresses in details and calculations as if they were regular addresses belonging to the wallet. If set to `false` (the default), treat watch-only addresses as if they didn't belong to this wallet _Result---account names, balances, and minimum confirmations_ Name | Type | Presence | Description --- | --- | --- | --- `result` | array | Required
(exactly 1) | An array containing objects each describing an account. At the very least, the default account (\\") will be included" →
Account | object | Required
(1 or more) | An object describing an account → →
`involvesWatchonly` | bool | Optional
(0 or 1) | Set to `true` if the balance of this account includes a watch-only address which has received a spendable payment (that is, a payment with at least the specified number of confirmations and which is not an immature coinbase). Otherwise not returned → →
`account` | string | Required
(exactly 1) | The name of the account → →
`amount` | number (dash) | Required
(exactly 1) | The total amount received by this account in dash → →
`confirmations` | number (int) | Required
(exactly 1) | The number of confirmations received by the last transaction received by this account. May be `0` → →
`label` | string | Optional
(0 or 1) | A comment for the address/transaction _Example from Dash Core 0.13.0_ Get the balances for all non-empty accounts, including transactions which have been confirmed at least six times and InstantSend locked transactions: ``` bash dash-cli -testnet listreceivedbyaccount 6 true false true ``` Result (edited to only show the first two results): ``` json [ { "account" : "", "amount" : 0.19960000, "confirmations" : 53601 }, { "account" : "doc test", "amount" : 0.30000000, "confirmations" : 8991 } ] ``` _See also_ * [ListReceivedByAddress](../api/remote-procedure-calls-wallet.md#listreceivedbyaddress): lists the total number of dash received by each address. * [ListReceivedByLabel](../api/remote-procedure-calls-wallet.md#listreceivedbylabel): lists the total number of dash received by each label. * [GetReceivedByAccount](../api/remote-procedure-calls-removed.md#getreceivedbyaccount): returns the total amount received by addresses in a particular account from transactions with the specified number of confirmations. It does not count coinbase transactions. * [GetReceivedByAddress](../api/remote-procedure-calls-wallet.md#getreceivedbyaddress): returns the total amount received by the specified address in transactions with the specified number of confirmations. It does not count coinbase transactions. ## Move >❗️**Warning:** **_Removed in Dash Core 18.0.0_** > 📘 > > Requires [wallet](../resources/glossary.md#wallet) support (**unavailable on masternodes**) The `move` RPC moves a specified amount from one account in your wallet to another using an off-block-chain transaction. > 🚧 > > **Warning:** it's possible to move more funds than are in an account, giving the sending account a negative balance and giving the receiving account a balance that may exceed the number of dash in the wallet (or the number of dash in existence). _Parameter #1---from account_ Name | Type | Presence | Description --- | --- | --- | --- From Account | string | Required
(exactly 1) | The name of the account to move the funds from _Parameter #2---to account_ Name | Type | Presence | Description --- | --- | --- | --- To Account | string | Required
(exactly 1) | The name of the account to move the funds to _Parameter #3---amount to move_ Name | Type | Presence | Description --- | --- | --- | --- Amount | number (dash) | Required
(exactly 1) | The amount of dash to move _Parameter #4---an unused parameter_ Name | Type | Presence | Description --- | --- | --- | --- _Unused_ | number (int) | Optional
(0 or 1) | This parameter is no longer used. If parameter #5 needs to be specified, this can be any integer _Parameter #5---a comment_ Name | Type | Presence | Description --- | --- | --- | --- Comment | string | Optional
(0 or 1) | A comment to assign to this move payment *Result---`true` on success* Name | Type | Presence | Description --- | --- | --- | --- `result` | bool | Required
(exactly 1) | Set to `true` if the move was successful _Example from Dash Core 0.12.2_ Move 1 dash from "doc test" to "test1", giving the transaction the comment "Example move": ``` bash dash-cli -testnet move "doc test" "test1" 0.1 0 "Example move" ``` Result: ``` json true ``` _See also_ * [ListAccounts](../api/remote-procedure-calls-removed.md#listaccounts): lists accounts and their balances. * [SendToAddress](../api/remote-procedure-calls-wallet.md#sendtoaddress): spends an amount to a given address. ## SendFrom >❗️**Warning:** **_Removed in Dash Core 18.0.0_** > 📘 > > Requires [wallet](../resources/glossary.md#wallet) support (**unavailable on masternodes**). Requires an unlocked wallet or an unencrypted wallet. The `sendfrom` RPC spends an amount from a local account to a dash address. _Parameter #1---from account_ Name | Type | Presence | Description --- | --- | --- | --- From Account | string | Required
(exactly 1) | The name of the account from which the dash should be spent. Use an empty string (\\") for the default account" _Parameter #2---to address_ Name | Type | Presence | Description --- | --- | --- | --- To Address | string | Required
(exactly 1) | A P2PKH or P2SH address to which the dash should be sent _Parameter #3---amount to spend_ Name | Type | Presence | Description --- | --- | --- | --- Amount | number (dash) | Required
(exactly 1) | The amount to spend in dash. Dash Core will ensure the account has sufficient dash to pay this amount (but the transaction fee paid is not included in the calculation, so an account can spend a total of its balance plus the transaction fee) _Parameter #4---minimum confirmations_ Name | Type | Presence | Description --- | --- | --- | --- Confirmations | number (int) | Optional
(0 or 1) | The minimum number of confirmations an incoming transaction must have for its outputs to be credited to this account's balance. Outgoing transactions are always counted, as are move transactions made with the [`move` RPC](../api/remote-procedure-calls-removed.md#move). If an account doesn't have a balance high enough to pay for this transaction, the payment will be rejected. Use `0` to spend unconfirmed incoming payments. Default is `1` > 🚧 > > **Warning:** if account1 receives an unconfirmed payment and transfers it to account2 with the [`move` RPC](../api/remote-procedure-calls-removed.md#move), account2 will be able to spend those dash even if this parameter is set to `1` or higher. _Parameter #5---whether to add the balance from transactions locked via InstantSend_ Name | Type | Presence | Description --- | --- | --- | --- addlocked | bool | Optional
(0 or 1) | If set to `true`, add the balance from InstantSend locked transactions. If set to `false` (the default), InstantSend locked transaction balances are not included. _Parameter #6---a comment_ Name | Type | Presence | Description --- | --- | --- | --- Comment | string | Optional
(0 or 1) | A locally-stored (not broadcast) comment assigned to this transaction. Default is no comment _Parameter #7---a comment about who the payment was sent to_ Name | Type | Presence | Description --- | --- | --- | --- Comment To | string | Optional
(0 or 1) | A locally-stored (not broadcast) comment assigned to this transaction. Meant to be used for describing who the payment was sent to. Default is no comment _Result---a TXID of the sent transaction_ Name | Type | Presence | Description --- | --- | --- | --- `result` | string | Required
(exactly 1) | The TXID of the sent transaction, encoded as hex in RPC byte order _Example from Dash Core 0.12.2_ Spend 0.1 dash from the account "test" to the address indicated below using only UTXOs with at least six confirmations, giving the transaction the comment "Example spend" and labeling the spender "Example.com": ``` bash dash-cli -testnet sendfrom "test" \ yhJays6zGUFKq1KS5V5WLbyk3cwCXyGrKd \ 0.1 \ 6 \ false \ "Example spend" \ "Example.com" ``` Result: ``` text cd64b9d55c63bf247f2eca32f978e340622107b607a46c422dabcdc20c0571fe ``` _See also_ * [SendToAddress](../api/remote-procedure-calls-wallet.md#sendtoaddress): spends an amount to a given address. * [SendMany](../api/remote-procedure-calls-wallet.md#sendmany): creates and broadcasts a transaction which sends outputs to multiple addresses. ## SignRawTransaction >❗️**Warning:** **_Removed in Dash Core 18.0.0_** The `signrawtransaction` RPC signs a transaction in the serialized transaction format using private keys stored in the wallet or provided in the call. _Parameter #1---the transaction to sign_ Name | Type | Presence | Description --- | --- | --- | --- Transaction | string (hex) | Required
(exactly 1) | The transaction to sign as a serialized transaction _Parameter #2---unspent transaction output details_ Name | Type | Presence | Description --- | --- | --- | --- Dependencies | array | Optional
(0 or 1) | The previous outputs being spent by this transaction →
Output | object | Optional
(0 or more) | An output being spent → →
`txid` | string (hex) | Required
(exactly 1) | The TXID of the transaction the output appeared in. The TXID must be encoded in hex in RPC byte order → →
`vout` | number (int) | Required
(exactly 1) | The index number of the output (vout) as it appeared in its transaction, with the first output being 0 → →
`scriptPubKey` | string (hex) | Required
(exactly 1) | The output's pubkey script encoded as hex → →
`redeemScript` | string (hex) | Optional
(0 or 1) | If the pubkey script was a script hash, this must be the corresponding redeem script → →
`amount` | numeric | Required
(exactly 1) | The amount of Dash spent _Parameter #3---private keys for signing_ Name | Type | Presence | Description --- | --- | --- | --- Private Keys | array | Optional
(0 or 1) | An array holding private keys. If any keys are provided, only they will be used to sign the transaction (even if the wallet has other matching keys). If this array is empty or not used, and wallet support is enabled, keys from the wallet will be used →
Key | string (base58) | Required
(1 or more) | A private key in base58check format to use to create a signature for this transaction _Parameter #4---signature hash type_ Name | Type | Presence | Description --- | --- | --- | --- SigHash | string | Optional
(0 or 1) | The type of signature hash to use for all of the signatures performed. (You must use separate calls to the [`signrawtransaction` RPC](../api/remote-procedure-calls-removed.md#signrawtransaction) if you want to use different signature hash types for different signatures. The allowed values are: `ALL`, `NONE`, `SINGLE`, `ALL|ANYONECANPAY`, `NONE|ANYONECANPAY`, and `SINGLE|ANYONECANPAY` _Result---the transaction with any signatures made_ Name | Type | Presence | Description --- | --- | --- | --- `result` | object | Required
(exactly 1) | The results of the signature →
`hex` | string (hex) | Required
(exactly 1) | The resulting serialized transaction encoded as hex with any signatures made inserted. If no signatures were made, this will be the same transaction provided in parameter #1 →
`complete` | bool | Required
(exactly 1) | The value `true` if transaction is fully signed; the value `false` if more signatures are required _Example from Dash Core 0.12.2_ Sign the hex generated in the example section for the `createrawtransaction` RPC: ``` bash dash-cli -testnet signrawtransaction 01000000016b490886c0198b028c6c5cb14\ 5c4eb3b1055a224a7a105aadeff41b69ec91e060100000000ffffffff0200205fa012000\ 0001976a914485485425fa99504ec1638ac4213f3cfc9f32ef388acc0a8f9be010000001\ 976a914811eacc14db8ebb5b64486dc43400c0226b428a488ac00000000 ``` Result: ``` json { "hex": "01000000016b490886c0198b028c6c5cb145c4eb3b1055a224a7a105aadeff41b69ec91e060100000069463043022033a61c56fa0867ed67b76b023204a9dc0ee6b0d63305dc5f65fe94335445ff2f021f712f55399d5238fc7146497c431fc4182a1de0b96fc22716e0845f561d542e012102eacba539d92eb88d4e73bb32749d79f53f6e8d7947ac40a71bd4b26c13b6ec29ffffffff0200205fa0120000001976a914485485425fa99504ec1638ac4213f3cfc9f32ef388acc0a8f9be010000001976a914811eacc14db8ebb5b64486dc43400c0226b428a488ac00000000", "complete": true } ``` _See also_ * [CombineRawTransaction](../api/remote-procedure-calls-raw-transactions.md#combinerawtransaction): combine multiple partially signed transactions into one transaction. * [CreateRawTransaction](../api/remote-procedure-calls-raw-transactions.md#createrawtransaction): creates an unsigned serialized transaction that spends a previous output to a new output with a P2PKH or P2SH address. The transaction is not stored in the wallet or transmitted to the network. * [DecodeRawTransaction](../api/remote-procedure-calls-raw-transactions.md#decoderawtransaction): decodes a serialized transaction hex string into a JSON object describing the transaction. * [SendRawTransaction](../api/remote-procedure-calls-raw-transactions.md#sendrawtransaction): validates a transaction and broadcasts it to the peer-to-peer network. * [SignRawTransactionWithKey](../api/remote-procedure-calls-raw-transactions.md#signrawtransactionwithkey): signs inputs for a transaction in the serialized transaction format using private keys provided in the call. ## Generate >❗️**Warning:** **_Removed in Dash Core 18.1.0_** The `generate` RPC mines blocks immediately (before the RPC call returns). _Parameter #1---the number of blocks to generate_ Name | Type | Presence | Description --- | --- | --- | --- `numblocks` | number (int) | Required
(exactly 1) | The number of blocks to generate. The RPC call will not return until all blocks have been generated. _Parameter #2---the number of iterations_ Name | Type | Presence | Description --- | --- | --- | --- `maxtries` | number (int) | Required
(exactly 1) | The number of iterations to try (default = 1000000). _Result---the generated block header hashes_ Name | Type | Presence | Description --- | --- | --- | --- `result` | array | Required
(exactly 1) | An array containing the block header hashes of the generated blocks (may be empty if used with `generate 0`) →
Header Hashes | string (hex) | Required
(1 or more) | The hashes of the headers of the blocks generated in regtest mode, as hex in RPC byte order _Example from Dash Core 0.12.2_ Using regtest mode, generate 2 blocks: ```bash dash-cli -regtest generate 2 ``` Result: ```json [ "55a4c47da8151c0823eec22c41ebc6d690a0288302179625bae9eb6f36808266", "3f07b9aa4e3bcd5518610945c4a6b32699acac71b1762605ff79ba553111fc79" ] ``` _See also_ * [GenerateToAddress](../api/remote-procedure-calls-generating.md#generatetoaddress): mines blocks immediately to a specified address. * [GetBlockTemplate](../api/remote-procedure-calls-mining.md#getblocktemplate): gets a block template or proposal for use with mining software. * [GetMiningInfo](../api/remote-procedure-calls-mining.md#getmininginfo): returns various mining-related information.