From 960a98d96e662db161ed547e2bfcac6a3a2a5009 Mon Sep 17 00:00:00 2001 From: thephez Date: Mon, 13 May 2019 12:15:30 -0400 Subject: [PATCH] Minor review update --- _includes/devdoc/guide_dash_features.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_includes/devdoc/guide_dash_features.md b/_includes/devdoc/guide_dash_features.md index 7b26174c..aa1c9922 100644 --- a/_includes/devdoc/guide_dash_features.md +++ b/_includes/devdoc/guide_dash_features.md @@ -123,8 +123,7 @@ output of the locking process is relayed to the entire Dash network. LLMQ-based InstantSend also removes a number of previously required limitations and simplifies the process by decreasing the number of P2P messages clients must process. Rather than tracking individual masternode votes for each transaction -input, all required locking information is found within the single `islock` message -for a transaction. +input, all required locking information is found within the single `islock` message. During the evaluation and transition from standard InstantSend to LLMQ-based InstantSend, Sporks 2 (`SPORK_2_INSTANTSEND_ENABLED`) and 20 (`SPORK_20_INSTANTSEND_LLMQ_BASED`)