joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-28 02:06:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

InstantSend - Add LLMQ-IS info to ChainLock section

Browse source
This commit is contained in:
thephez 2019-04-29 11:07:18 -04:00
parent 94229ddce6
commit 9dd3d2ffd7
No known key found for this signature in database
GPG key ID: BBC8A06DBE236099
1 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

9
_includes/devdoc/guide_dash_features.md
View file

@ -182,9 +182,9 @@ Dash's ChainLock feature leverages [LLMQ Signing Requests/Sessions](#llmq-signin
to reduce uncertainty when receiving funds and remove the possibility of 51% to reduce uncertainty when receiving funds and remove the possibility of 51%
mining attacks. mining attacks.
For each block, an LLMQ of a few hundred masternodes is selected and each For each block, an LLMQ of a few hundred masternodes (300-400) is selected and each
participating member signs the first block that it sees extending the active participating member signs the first block that it sees extending the active
chain at the current height. If enough members (e.g. >= 60%) see the same block chain at the current height. If enough members (at least 240) see the same block
as the first block, they will be able to create a `clsig` message and propagate as the first block, they will be able to create a `clsig` message and propagate
it to all nodes in the network. it to all nodes in the network.
@ -193,6 +193,11 @@ any descendants) at the same height that do not match the block specified in the
`clsig` message. This makes the decision on the active chain quick, easy and `clsig` message. This makes the decision on the active chain quick, easy and
unambiguous. It also makes reorganizations below this block impossible. unambiguous. It also makes reorganizations below this block impossible.
When LLMQ-based InstantSend is enabled, a ChainLock is only attempted once all
transactions in the block are locked via InstantSend. If a block contains
unlocked transactions, retroactive InstantSend locks are established prior to
a ChainLock.
Please read [DIP8 ChainLocks](https://github.com/dashpay/dips/blob/master/dip-0008.md) Please read [DIP8 ChainLocks](https://github.com/dashpay/dips/blob/master/dip-0008.md)
for additional details. for additional details.