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.
This commit is contained in:
Nathan Marley 2019-05-28 09:38:12 -03:00 committed by thephez
parent 26cf7c9f92
commit aa804d2e23

View file

@ -84,7 +84,9 @@ When a transaction is eligible for InstantSend, each masternode should try to
initiate a signing request for each of the transactions inputs. The request initiate a signing request for each of the transactions inputs. The request
id is: id is:
```
hash("inlock", prevTxHash, prevTxOut) hash("inlock", prevTxHash, prevTxOut)
```
`"inlock"` is a static string, prepended with the length (6, as a compact int, `"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 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) Finalization is simply another signing request, performed on a (potentially)
different LLMQ than used before. The request id of the new signing request is: 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, `"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, which is a single byte) of the string. `inputCount` is a compact int,