From aa804d2e23d1916161219288b17e69db8abcb4cd Mon Sep 17 00:00:00 2001 From: Nathan Marley Date: Tue, 28 May 2019 09:38:12 -0300 Subject: [PATCH] Fix rendering of code block and use fenced blocks (#50) The fences aren't actually necessary, but make it easier (IMO) to delineate the code block and not worry about number of leading spaces. --- dip-0010.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/dip-0010.md b/dip-0010.md index dad957e..8899bbb 100644 --- a/dip-0010.md +++ b/dip-0010.md @@ -84,7 +84,9 @@ When a transaction is eligible for InstantSend, each masternode should try to initiate a signing request for each of the transaction’s inputs. The request id is: - hash("inlock", prevTxHash, prevTxOut) +``` +hash("inlock", prevTxHash, prevTxOut) +``` `"inlock"` is a static string, prepended with the length (6, as a compact int, which is a single byte) of the string. The message hash of the signing request @@ -110,8 +112,9 @@ message. Finalization is simply another signing request, performed on a (potentially) different LLMQ than used before. The request id of the new signing request is: - hash("islock", inputCount, prevTxHash1, prevTxOut1, prevTxHash2, -prevTxOut2, ...) +``` +hash("islock", inputCount, prevTxHash1, prevTxOut1, prevTxHash2, prevTxOut2, ...) +``` `"islock"` is a static string, prepended with the length (6, as a compact int, which is a single byte) of the string. `inputCount` is a compact int,