mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 12:32:48 +01:00
0a6f47323b
* remove instandsenddepth option * remove CInstantSend::GetConfirmations * Explicit IXlocks processing in the code using GetDepthInMainChain * remove dummy confirmations for IX locks * remove unused constant * Track IS status in TransactionStatus * Highlight IS in tx list * Customize confirmation icons for IS txes * Fix issues: - bring back removed comment; - simplify 2 complex condition to ose `IsTrusted()` function only; - rename `IsLockedIX` function to 'IsLockedByInstantSend`; * Revert condition with IsTrusted() * code style fix * remove dummy confirmations from instantsend.md * fix instantsend.md
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
## InstantSend Technical Information
|
|
|
|
InstantSend has been integrated into the Core Daemon in two ways:
|
|
* "push" notifications (ZMQ and `-instantsendnotify` cmd-line/config option);
|
|
* RPC commands.
|
|
|
|
#### ZMQ
|
|
|
|
When a "Transaction Lock" occurs the hash of the related transaction is broadcasted through ZMQ using both the `zmqpubrawtxlock` and `zmqpubhashtxlock` channels.
|
|
|
|
* `zmqpubrawtxlock`: publishes the raw transaction when locked via InstantSend
|
|
* `zmqpubhashtxlock`: publishes the transaction hash when locked via InstantSend
|
|
|
|
This mechanism has been integrated into Bitcore-Node-Dash which allows for notification to be broadcast through Insight API in one of two ways:
|
|
* WebSocket: [https://github.com/dashpay/insight-api-dash#web-socket-api](https://github.com/dashpay/insight-api-dash#web-socket-api)
|
|
* API: [https://github.com/dashpay/insight-api-dash#instantsend-transactions](https://github.com/dashpay/insight-api-dash#instantsend-transactions)
|
|
|
|
#### Command line option
|
|
|
|
When a wallet InstantSend transaction is successfully locked a shell command provided in this option is executed (`%s` in `<cmd>` is replaced by TxID):
|
|
|
|
```
|
|
-instantsendnotify=<cmd>
|
|
```
|
|
|
|
#### RPC
|
|
|
|
Details pertaining to an observed "Transaction Lock" can also be retrieved through RPC. There is a boolean field named `instantlock` which indicates whether a given transaction is locked via InstantSend. This field is present in the output of some wallet RPC commands e.g. `listsinceblock`, `gettransaction` etc. as well as in the output of some mempool RPC commands e.g. `getmempoolentry` and a couple of others like `getrawmempool` (for `verbose=true` only).
|