Removed RPCs
EstimatePriority
Warning: Removed in Dash Core 0.14.0.
The estimatepriority
RPC was removed in Dash Core 0.14.0. This should not to be confused with the prioritisetransaction
RPC which will remain supported for adding fee deltas to transactions.
Parameter #1---how many blocks the transaction may wait before being included as a free high-priority transaction
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 based purely on its priority |
Result---the priority a transaction needs
Name | Type | Presence | Description |
---|---|---|---|
result | number (real) | Required (exactly 1) | The estimated priority the transaction should have in order to be included within the specified number of blocks. If the node doesn't have enough information to make an estimate, the value -1 will be returned |
Examples from Dash Core 0.12.2
dash-cli estimatepriority 6
Result:
718158904.10958910
Requesting data the node can't calculate yet:
dash-cli estimatepriority 100
Result:
-1
See also
- EstimateFee: estimates the transaction fee per kilobyte that needs to be paid for a transaction to begin confirmation within a certain number of blocks.
EstimateSmartPriority
Warning: Removed in Dash Core 0.14.0.
The estimatesmartpriority
RPC was removed in Dash Core 0.14.0. This should not to be confused with the prioritisetransaction
RPC which will remain supported for adding fee deltas to transactions.
Parameter #1---how many blocks the transaction may wait before being included as a free high-priority transaction
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 based purely on its priority |
Result---the priority a transaction needs
Name | Type | Presence | Description |
---|---|---|---|
result | object | Required (exactly 1) | JSON Object containing estimate information |
→priority | number | Required (exactly 1) | The estimated priority the transaction should be in order to be included within the specified number of blocks. If the node doesn't have enough information to make an estimate, the value -1 will be returned |
→blocks | number | Required (exactly 1) | Block number where the estimate was found |
Examples from Dash Core 0.12.2
dash-cli estimatesmartpriority 6
Result:
{
"priority": 718158904
"blocks": 25
}
Requesting data the node can't calculate yet:
dash-cli estimatesmartpriority 100
Result:
{
"priority": -1,
"blocks": 100
}
See also
- EstimatePriority: was removed in Dash Core 0.14.0.
GetHashesPerSec
Requires wallet support.
The
gethashespersec
RPC was removed in Bitcoin Core 0.11.0 and is not part of Dash.
See also
- Generate: mines blocks immediately (before the RPC call returns).
- GetMiningInfo: returns various mining-related information.
GetWork
The
getwork
RPC was removed in Bitcoin Core 0.10.0. and is not part of Dash.
See also
- GetBlockTemplate: gets a block template or proposal for use with mining software.
- SubmitBlock: accepts a block, verifies it is a valid addition to the block chain, and broadcasts it to the network. Extra parameters are ignored by Dash Core but may be used by mining pools or other programs.
GetGenerate
Removed in Dash Core 0.12.3 / Bitcoin Core 0.13.0.
Requires wallet support.
The getgenerate
RPC was removed in Dash Core 0.12.3.
Parameters: none
Result---whether the server is set to generate blocks
Name | Type | Presence | Description |
---|---|---|---|
result | bool | Required (exactly 1) | Set to true if the server is set to generate blocks; set to false if it is not |
Example from Dash Core 0.12.2
dash-cli -regtest getgenerate
Result:
false
See also
- Generate: mines blocks immediately (before the RPC call returns).
- GenerateToAddress: mines blocks immediately to a specified address.
- GetMiningInfo: returns various mining-related information.
- SetGenerate: was removed in Dash Core 0.12.3.
MasternodeBroadcast
Warning: Removed in Dash Core 0.14.0.
The masternodebroadcast
RPC was removed in Dash Core 0.14.0.
Parameter #1---masternode broadcast command
Name | Type | Presence | Description |
---|---|---|---|
command | string (hex) | Required (exactly 1) | The command to use:create-alias create-all decode relay |
MNB create-alias
The masternodebroadcast create-alias
RPC creates single remote masternode broadcast message by assigned alias configured in masternode.conf
.
Parameter #2---masternode alias
Name | Type | Presence | Description |
---|---|---|---|
alias | string | Required (exactly 1) | The masternode alias for creating the broadcast message |
Result---broadcast message
Name | Type | Presence | Description |
---|---|---|---|
Result | object | Required (exactly 1) | Object containing result data |
→alias | string | Required (exactly 1) | Alias of the masternode |
→result | string | Required (exactly 1) | Result of broadcast message create attempt |
→hex | string (hex) | Required (exactly 1) | Masternode broadcast data |
Example from Dash Core 0.12.2
dash-cli -testnet masternodebroadcast create-alias MN01
Result:
{
"alias": "MN01",
"result": "successful",
"hex": "010fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff00000000000000000000ffff2d20ed4c4e1f210267fae84ef6aa6ab3d877b47932915a9b406566c873ea025986fc7e15a15fd2f24104341ab0d26ae967856213df205bf172418422a847f3a63941d8031234a64a143f5570a6010d2b5e1dff163c91316a65667f0ee1bfb0ff38edd0a695bea75de731411f8a9bf1e7818c7352c8a02bd31a4da1bb8d88e91c8a9c7151afc076b6a68f54c9087a981a780e6279e9d7b73940ee7aad65c28e4846573bffa74518443380dfde4d3c145a00000000401201000fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff69fc28f4772eaefd17cd1bab575aac752b5944ee3e7221df204b4d04000000004d3c145a00000000411bef1bdf25a500ae2af4052e8504e2f93ec365d5ed9d42e3c52b84714136060f9766068553c450a4b1c0b3d72740580f097f7e62c098addc55f71f016cfda24d7a0001000100"
}
MNB create-all
The masternodebroadcast create-all
RPC creates remote masternode broadcast messages for all masternodes configured in masternode.conf
.
Result---broadcast message(s)
Name | Type | Presence | Description |
---|---|---|---|
Result | object | Required (exactly 1) | Object containing result data |
→overall | string | Required (exactly 1) | Summary of broadcast message creation success/failure |
→ detail | object | Required (exactly 1) | Object containing status details |
→ → status | object | Required (1 or more) | Object containing status for each each masternode broadcast message creation attempt |
→ → →alias | string | Required (exactly 1) | Alias of the masternode |
→ → →result | string | Required (exactly 1) | Result - successful or failed |
→ → →error | string | Optional | Error message if failed |
→hex | string (hex) | Optional (exactly 1) | Masternode broadcast data (if message(s) created successfully) |
Example from Dash Core 0.12.2
dash-cli -testnet masternodebroadcast create-all
Result:
{
"overall": "Successfully created broadcast messages for 1 masternodes, failed to create 0, total 1",
"detail": {
"status": {
"alias": "MN01",
"result": "successful"
}
},
"hex": "010fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff00000000000000000000ffff2d20ed4c4e1f210267fae84ef6aa6ab3d877b47932915a9b406566c873ea025986fc7e15a15fd2f24104341ab0d26ae967856213df205bf172418422a847f3a63941d8031234a64a143f5570a6010d2b5e1dff163c91316a65667f0ee1bfb0ff38edd0a695bea75de731411f555444bd95d98b8407ff1b8cc595a3d284c30b9bbaca488a949bc53be08ca1021724527f9a15e9307c7391d9ad563dcc9ced6ae621ae7d6fe3e3c3ba81dce795d143145a00000000401201000fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff914dff1cc3dfc0729bb1f4e3f070d65d1fa41072da5290a54d472d0400000000d143145a00000000411c628109c911ef330aaa789bd621f8c7975290d196beef3ecdaa1133302daccdaa3df82b1f16d753fef884ce3a3eb28a7b621233c14496a010bb49f247190651100001000100"
}
MNB decode
The masternodebroadcast decode
RPC decodes a masternode broadcast message (deserializes from a hex string to JSON).
Parameter #2---object data (hex)
Name | Type | Presence | Description |
---|---|---|---|
data-hex | string (hex) | Required (exactly 1) | The data (hex) of the masternode broadcast to decode |
Result---broadcast message(s)
Name | Type | Presence | Description |
---|---|---|---|
Result | object | Required (exactly 1) | Object containing result data |
→outpoint | string (hex) | Required (exactly 1) | Masternode outpoint |
→addr | string | Required (exactly 1) | Masternode IP address and port |
→pubKeyCollateralAddress | string (hex) | Required (1 or more) | Masternode collateral public key address |
→pubKeyMasternode | string (hex) | Required (exactly 1) | Masternode public key |
→vchSig | string (base64) | Required (exactly 1) | Masternode signature |
→sigTime | int64_t | Required (exactly 1) | Signature time as a Unix epoch |
→protocolVersion | int | Required (exactly 1) | Dash protocol version |
→nLastDsq | int64_t | Required (exactly 1) | Dsq count from the last dsq message from this node |
→ lastPing | object | Required (exactly 1) | Ping object (mnp message) |
→ →outpoint | string (hex) | Required (exactly 1) | Masternode outpoint |
→ →blockHash | string (hex) | Required (exactly 1) | Block hash from 12 blocks prior to the current tip |
→ →sigTime | int64_t | Required (exactly 1) | Signature time as a Unix epoch |
→ →vchSig | string (base64) | Required (exactly 1) | Masternode signature |
→overall | string | Required (exactly 1) | Summary of broadcast message creation success/failure |
Example from Dash Core 0.12.2
masternodebroadcast decode 010fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c4\
8778a4fa6bd93fc8f60100000000ffffffff00000000000000000000ffff2d20ed4c4e1f2102\
67fae84ef6aa6ab3d877b47932915a9b406566c873ea025986fc7e15a15fd2f24104341ab0d2\
6ae967856213df205bf172418422a847f3a63941d8031234a64a143f5570a6010d2b5e1dff16\
3c91316a65667f0ee1bfb0ff38edd0a695bea75de731411f8a9bf1e7818c7352c8a02bd31a4d\
a1bb8d88e91c8a9c7151afc076b6a68f54c9087a981a780e6279e9d7b73940ee7aad65c28e48\
46573bffa74518443380dfde4d3c145a00000000401201000fab7e86a6d7c483b836fe862c8a\
23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff69fc28f4772eaefd17cd1b\
ab575aac752b5944ee3e7221df204b4d04000000004d3c145a00000000411bef1bdf25a500ae\
2af4052e8504e2f93ec365d5ed9d42e3c52b84714136060f9766068553c450a4b1c0b3d72740\
580f097f7e62c098addc55f71f016cfda24d7a0001000100
Result:
{
"36b753f9c8d328d405b8a909bbf4fd29c0d37aa48eae98fa1289b90e36e002c4": {
"outpoint": "f6c83fd96bfaa47887c4587cceadeb9af6238a2c86fe36b883c4d7a6867eab0f-1",
"addr": "45.32.237.76:19999",
"pubKeyCollateralAddress": "yY6AmGopsZS31wy1JLHR9P6AC6owFaXwuh",
"pubKeyMasternode": "yj25teTD6yjcNpQC7inq72tDgsivG6xLZM",
"vchSig": "H4qb8eeBjHNSyKAr0xpNobuNiOkcipxxUa/Adramj1TJCHqYGngOYnnp17c5QO56rWXCjkhGVzv/p0UYRDOA394=",
"sigTime": 1511275597,
"protocolVersion": 70208,
"nLastDsq": 0,
"lastPing": {
"outpoint": "f6c83fd96bfaa47887c4587cceadeb9af6238a2c86fe36b883c4d7a6867eab0f-1",
"blockHash": "00000000044d4b20df21723eee44592b75ac5a57ab1bcd17fdae2e77f428fc69",
"sigTime": 1511275597,
"vchSig": "G+8b3yWlAK4q9AUuhQTi+T7DZdXtnULjxSuEcUE2Bg+XZgaFU8RQpLHAs9cnQFgPCX9+YsCYrdxV9x8BbP2iTXo="
}
},
"overall": "Successfully decoded broadcast messages for 1 masternodes, failed to decode 0, total 1"
}
MNB relay
The masternodebroadcast relay
RPC relays a masternode broadcast message to the network.
Parameter #2---object data (hex)
Name | Type | Presence | Description |
---|---|---|---|
data-hex | string (hex) | Required (exactly 1) | The data (hex) of the masternode broadcast to relay |
Result---broadcast message(s)
Name | Type | Presence | Description |
---|---|---|---|
Result | object | Required (exactly 1) | Object containing result data |
→ Hash | string (hex) | Required (1 or more) | Masternode broadcast hash |
→ →outpoint | string (hex) | Required (exactly 1) | Masternode outpoint |
→ →addr | string | Required (exactly 1) | Masternode IP address and port |
→ → Result | string (hex) | Required (exactly 1) | Result - successful or failed |
→ → →error | string | Optional | Error message if failed |
→overall | string | Required (exactly 1) | Summary of broadcast message creation success/failure |
Example from Dash Core 0.12.2
masternodebroadcast relay 010fab7e86a6d7c483b836fe862c8a23f69aebadce7c58c4\
8778a4fa6bd93fc8f60100000000ffffffff00000000000000000000ffff2d20ed4c4e1f2102\
67fae84ef6aa6ab3d877b47932915a9b406566c873ea025986fc7e15a15fd2f24104341ab0d2\
6ae967856213df205bf172418422a847f3a63941d8031234a64a143f5570a6010d2b5e1dff16\
3c91316a65667f0ee1bfb0ff38edd0a695bea75de731411f8a9bf1e7818c7352c8a02bd31a4d\
a1bb8d88e91c8a9c7151afc076b6a68f54c9087a981a780e6279e9d7b73940ee7aad65c28e48\
46573bffa74518443380dfde4d3c145a00000000401201000fab7e86a6d7c483b836fe862c8a\
23f69aebadce7c58c48778a4fa6bd93fc8f60100000000ffffffff69fc28f4772eaefd17cd1b\
ab575aac752b5944ee3e7221df204b4d04000000004d3c145a00000000411bef1bdf25a500ae\
2af4052e8504e2f93ec365d5ed9d42e3c52b84714136060f9766068553c450a4b1c0b3d72740\
580f097f7e62c098addc55f71f016cfda24d7a0001000100
Result:
{
"36b753f9c8d328d405b8a909bbf4fd29c0d37aa48eae98fa1289b90e36e002c4": {
"outpoint": "f6c83fd96bfaa47887c4587cceadeb9af6238a2c86fe36b883c4d7a6867eab0f-1",
"addr": "45.32.237.76:19999",
"36b753f9c8d328d405b8a909bbf4fd29c0d37aa48eae98fa1289b90e36e002c4": "successful"
},
"overall": "Successfully relayed broadcast messages for 1 masternodes, failed to relay 0, total 1"
}
See also: none
SentinelPing
Warning: Removed in Dash Core 0.14.0.
The sentinelping
RPC was removed in Dash Core 0.14.0.
Parameter #1---sentinel version
Name | Type | Presence | Description |
---|---|---|---|
Version | string | Required (exactly 1) | Sentinel version in the form 'x.x.x' |
Result---the message signature
Name | Type | Presence | Description |
---|---|---|---|
Result | bool | Required (exactly 1) | Ping result |
Example from Dash Core 0.12.2
dash-cli -testnet sentinelping
Result:
true
See also: none
SetGenerate
Removed in Dash Core 0.12.3 / Bitcoin Core 0.13.0.
Requires wallet support.
The setgenerate
RPC was removed in Dash Core 0.12.3.
Parameter #1---enable/disable generation
Name | Type | Presence | Description |
---|---|---|---|
generate | boolean | Required (exactly 1) | Set to true to turn on generation, false to turn off. |
Parameter #2---processor limit
Name | Type | Presence | Description |
---|---|---|---|
genproclimit | number (int) | Optional (exactly 1) | Set the processor limit for when generation is on. Can be -1 for unlimited. |
Result---the generated block header hashes
Name | Type | Presence | Description |
---|---|---|---|
result | null | Required (exactly 1) | Always JSON null |
Example from Dash Core 0.12.2
Enable generation using 1 processor:
dash-cli -testnet setgenerate 1
Result:
(Success: no result displayed. Process manager shows 100% CPU usage.)
See also
- Generate: mines blocks immediately (before the RPC call returns).
- GenerateToAddress: mines blocks immediately to a specified address.
- GetMiningInfo: returns various mining-related information.
- GetBlockTemplate: gets a block template or proposal for use with mining software.
Updated almost 5 years ago