From 94ad41555fd7c6741337ccf2f11e0cdeaf4b74c8 Mon Sep 17 00:00:00 2001 From: Yigit Sever Date: Sat, 17 Apr 2021 20:11:28 +0300 Subject: Update docs --- site/public/block-docs/index.html | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) (limited to 'site/public/block-docs/index.html') diff --git a/site/public/block-docs/index.html b/site/public/block-docs/index.html index 3c2c3df..8edc5a0 100644 --- a/site/public/block-docs/index.html +++ b/site/public/block-docs/index.html @@ -94,6 +94,11 @@ +
+ Mining +
+ +
Hash
@@ -110,7 +115,7 @@

A block that was proposed to commit Transactions in transaction_list to the ledger with a nonce that made hash valid; 6 zeroes at the left hand side of the hash (24 bytes).

-

We are mining using blake2s algorithm, which produces 256 bit hashes. Hash/second is roughly 20x10^3 on my machine, a new block can be mined in around 4-6 minutes.

+

We are mining using blake2s algorithm, which produces 256 bit hashes. Hash/second is roughly 20x103 on my machine, a new block can be mined in around 4-6 minutes.

Requests

GET

A HTTP GET request to /block endpoint will return the latest mined block.

@@ -122,8 +127,16 @@ hash (24 bytes).

nonce: unsigned 32-bit integer timestamp: ISO 8601 <date>T<time> hash: String -

Hash

-

tha field in jwt documentation in fact stands for "The Hash", in the case of a post request for a block, you need to use hash field of the block.

+

Mining

+

The mining process for the hash involves;

+ +

If the resulting hash is valid, then you can create a Block JSON object with the found nonce and hash.

+

Hash

+

tha field in jwt documentation in fact stands for "The Hash", in the case of a post request for a block, you need to use hash field of the block.

ISO 8601 Reference

-- cgit v1.2.3-70-g09d2