Get desktop application:
View/edit binary Protocol Buffers messages
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
Queries
(message has no fields)
(message has no fields)
(message has no fields)
(message has no fields)
Optionally specify the starting block from which to begin including all transactions. Either the starting block hash or height may be specified, but not both. If a block height is specified and is negative, the absolute value becomes the number of last blocks to include. That is, given a current chain height of 1000 and a starting block height of -3, transaction notifications will be created for blocks 998, 999, and 1000. If both options are excluded, transaction results are created for transactions since the genesis block.
Optionally specify the last block that transaction results may appear in. Either the ending block hash or height may be specified, but not both. If both are excluded, transaction results are created for all transactions through the best block, and include all unmined transactions.
Include at least this many of the newest transactions if they exist. Cannot be used when the ending block hash is specified. TODO: remove until spec adds it back in some way.
Notifications
(message has no fields)
Sorted by increasing height. This is a repeated field so many new blocks in a new best chain can be notified at once during a reorganize.
If there was a chain reorganize, there may have been blocks with wallet transactions that are no longer in the best chain. These are those block's hashes.
Any new unmined transactions are included here. These unmined transactions refer to the current best chain, so transactions from detached blocks may be moved to mempool and included here if they are not mined or double spent in the new chain. Additonally, if no new blocks were attached but a relevant unmined transaction is seen by the wallet, it will be reported here.
Instead of notifying all of the removed unmined transactions, just send all of the current hashes.
(message has no fields)
Control
(message has no fields)
(message has no fields)
(message has no fields)
If no indexes are specified, signatures scripts will be added for every input. If any input indexes are specified, only those inputs will be signed. Rather than returning an incompletely signed transaction if any of the inputs to be signed can not be, the RPC immediately errors.
(message has no fields)
Used in:
Used in:
,Used in:
Used in:
Used in:
Used in:
Used in:
, ,May be earlier than a block timestamp, but never later.
Used in:
Used in: