diff options
| -rw-r--r-- | content/block_docs.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/content/block_docs.md b/content/block_docs.md index 3c47231..963db68 100644 --- a/content/block_docs.md +++ b/content/block_docs.md | |||
| @@ -49,6 +49,10 @@ The _mining_ process for the hash involves; | |||
| 49 | - Serializing it | 49 | - Serializing it |
| 50 | - **NOTE:** Serialized JSON must comply with the rules explained in hash section of [transaction](@/transaction_docs.md) page. | 50 | - **NOTE:** Serialized JSON must comply with the rules explained in hash section of [transaction](@/transaction_docs.md) page. |
| 51 | - The order of keys should be as follows: `transaction_list`, `nonce`, `timestamp`. | 51 | - The order of keys should be as follows: `transaction_list`, `nonce`, `timestamp`. |
| 52 | - Example: | ||
| 53 | ```json | ||
| 54 | {"transaction_list":["a1a3","cde4","60e7","4e04"],"nonce":5342433,"timestamp":"2022-04-23T23:49:24.622651"} | ||
| 55 | ``` | ||
| 52 | - Calculating blake2s hash of the serialized string | 56 | - Calculating blake2s hash of the serialized string |
| 53 | - Checking if the hash is valid | 57 | - Checking if the hash is valid |
| 54 | - The hash is considered valid if its hexadecimal representation starts with an arbitrary number of zeros. | 58 | - The hash is considered valid if its hexadecimal representation starts with an arbitrary number of zeros. |