sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-27 21:12:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
62963e9111
dash/doc/instantsend.md
Will Wray 82a4643135 Doc: fix broken formatting in markdown #headers (#1462) 
* Doc: fix broken formatting in markdown #headers

Insert a space in markdown headers between the #'s and the header text.
(It appears that the space is required since a github update a year ago
https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0)

* Update REST-interface.md

* Update guide-startmany.md

* Update instantsend.md

* Update keepass.md

* Update release-process.md
2017-05-05 14:28:08 +03:00

2.6 KiB
Raw Blame History

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:

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, it’s important however to understand the underlying mechanism.

By default, the Dash Core daemon will launch using the following constant:

static const int DEFAULT_INSTANTSEND_DEPTH = 5;

This value can be overridden by passing the following argument to the Dash Core daemon:

-instantsenddepth=<n>

The key thing to understand is that this value indicates the number of "confirmations" a successful Transaction Lock represents. When Wallet RPC commands are performed (such as listsinceblock) this attribute is taken into account when returning information about the transaction. The value in confirmations field you see through RPC is showing the number of "Blockchain Confirmations" + "InstantSend Depth" (assuming the funds were sent via InstantSend).

There is also a field named bcconfirmations. The value in this field represents the total number of "Blockchain Confirmations" for a given transaction without taking into account whether it was InstantSend or not.

Examples

  • InstantSend transaction just occurred:
    • confirmations: 5
    • bcconfirmations: 0
  • InstantSend transaction received one confirmation from blockchain:
    • confirmations: 6
    • bcconfirmations: 1
  • non-InstantSend transaction just occurred:
    • confirmations: 0
    • bcconfirmations: 0
  • non-InstantSend transaction received one confirmation from blockchain:
    • confirmations: 1
    • bcconfirmations: 1