doc: include RNG documentation #98

lrubiorod · 2021-11-03T10:57:36Z

It is included inside of data request section but it could be moved

Close #97

aesedepece · 2021-11-05T14:39:14Z

docs/protocol/data-requests/rng.md

+Witnet requests are currently used to retrieve information from public external APIs to Witnet network and
+other blockchains that are connected with it. Moreover, using the structure about Witnet network, another 
+functionality as Random Number Generator (aka RNG) is possible, providing a real random number created by
+several witnesses in a decentralized way.


No need to beat around the bush. Let's go straight to the point of RNG. This paragraph can be dropped altogether.

aesedepece · 2021-11-05T14:39:37Z

docs/protocol/data-requests/rng.md

+## Witnet RNG request
+The Witnet RNG request shares the same structure as a normal request with the 3 stages (retrieval, 
+aggregation and tally) and it will be solved by the same witnesses that are currently working in the Witnet
+mainnet. To retrieve this new functionality those are the changes:


Suggested change

mainnet. To retrieve this new functionality those are the changes:

mainnet.

aesedepece · 2021-11-05T14:41:41Z

docs/protocol/data-requests/rng.md

+are not necessary, so the `url` will be empty and the `script` won't be read so we can specify the code
+for an empty array. We only use an only retrieval for this kind of requests.


Suggested change

are not necessary, so the `url` will be empty and the `script` won't be read so we can specify the code

for an empty array. We only use an only retrieval for this kind of requests.

are not necessary: the `url` field must be empty and the `script` field will be ignored, so we can specify the CBOR code for an empty array ([128]`). A single source is used in the retrieval section of this kind of requests.

aesedepece · 2021-11-05T14:58:56Z

docs/protocol/data-requests/rng.md

+Aggregation is not necessary due to RNG requests has only one retrieval. To unwrap the `RadonArray` with
+only one element we will use the `Mode` as a `RadonReducer` without filters.


Suggested change

Aggregation is not necessary due to RNG requests has only one retrieval. To unwrap the `RadonArray` with

only one element we will use the `Mode` as a `RadonReducer` without filters.

Aggregation is not necessary due to the fact that RNG requests have only one retrieval. To unwrap the `RadonArray` into a single element, we will use the `Mode` as a `RadonReducer` without filters.

aesedepece · 2021-11-05T14:59:51Z

docs/protocol/data-requests/rng.md

+For the tally stage a new `RadonReducer` is required, `HashConcatenate`. This reducer takes the
+`RadonBytes` sent by witnesses, concatenate them in a single vector of bytes and hash them with Sha2_256.
+As the aggregation stage, no filters are required. 


Suggested change

For the tally stage a new `RadonReducer` is required, `HashConcatenate`. This reducer takes the

`RadonBytes` sent by witnesses, concatenate them in a single vector of bytes and hash them with Sha2_256.

As the aggregation stage, no filters are required.

For the tally stage, a new `RadonReducer` is required, `HashConcatenate`. This reducer takes the

`RadonBytes` revealed by the witnesses, concatenate them into a single vector of bytes and hash them with SHA256. In the same way as in the aggregation stage, no filters are required.

aesedepece · 2021-11-05T15:02:04Z

docs/protocol/data-requests/rng.md

+## Conclusions
+The random number generated by Witnet protocol is the result of a Hash function which its seed comes from
+the random bytes provided by several different witnesses selected randomly in the Witnet mainnet. In this
+way, randomness comes from the decentralization nature of Witnet protocol.


Suggested change

## Conclusions

The random number generated by Witnet protocol is the result of a Hash function which its seed comes from

the random bytes provided by several different witnesses selected randomly in the Witnet mainnet. In this

way, randomness comes from the decentralization nature of Witnet protocol.

## Conclusions

The random numbers (actually, random bytes) generated by the Witnet protocol are the result of applying a hash function on a crowdsourced seed coming from the random bytes provided by several different witnesses, as selected randomly by the Witnet protocol. That is, the randomness property of these are powered by the decentralized nature of the Witnet network.

Tommytrg · 2021-11-12T09:37:40Z

docs/protocol/data-requests/rng.md

+# Random Number Generation
+
+## Witnet RNG request
+The Witnet RNG request shares the same structure as a normal request with the 3 stages (retrieval, aggregation and 


What do you think about use a more specific word such as HTTP-GET or even standard?

Suggested change

The Witnet RNG request shares the same structure as a normal request with the 3 stages (retrieval, aggregation and

The Witnet RNG request shares the same structure as an HTTP-GET request with the 3 stages (retrieval, aggregation and

Tommytrg · 2021-11-12T09:41:39Z

docs/protocol/data-requests/rng.md

+### Retrieval
+As a source for RNG requests, we specify a new `RADType` called `Rng`. This new source will trigger the creation of a
+random vector of 32 bytes, instead of reading data from an API source. The rest of fields are not necessary: the `url` 
+field must be empty and the `script` field will be ignored, so we can specify the CBOR code for an empty array 


Suggested change

field must be empty and the `script` field will be ignored, so we can specify the CBOR code for an empty array

field must be empty and the `script` field will be ignored so we can specify the CBOR code for an empty array

Tommytrg · 2021-11-12T09:42:19Z

docs/protocol/data-requests/rng.md

+
+### Retrieval
+As a source for RNG requests, we specify a new `RADType` called `Rng`. This new source will trigger the creation of a
+random vector of 32 bytes, instead of reading data from an API source. The rest of fields are not necessary: the `url` 


Suggested change

random vector of 32 bytes, instead of reading data from an API source. The rest of fields are not necessary: the `url`

random vector of 32 bytes, instead of reading data from an API source. The rest of the fields are unnecessary: the `url`

Tommytrg · 2021-11-12T09:45:22Z

docs/protocol/data-requests/rng.md

+
+### Tally
+For the tally stage, a new `RadonReducer` is required, `HashConcatenate`. This reducer takes the `RadonBytes` revealed 
+by the witnesses, concatenate them into a single vector of bytes and hash them with SHA256. In the same way as in the 


Suggested change

by the witnesses, concatenate them into a single vector of bytes and hash them with SHA256. In the same way as in the

by the witnesses, concatenates them into a single vector of bytes and hash them with SHA256. In the same way, as in the

Tommytrg · 2021-11-12T09:46:40Z

docs/protocol/data-requests/rng.md

+## Conclusions
+The random numbers (actually, random bytes) generated by the Witnet protocol are the result of applying a hash 
+function on a crowdsourced seed coming from the random bytes provided by several different witnesses, as selected 
+randomly by the Witnet protocol. That is, the randomness property of these are powered by the decentralized nature 


Suggested change

randomly by the Witnet protocol. That is, the randomness property of these are powered by the decentralized nature

randomly by the Witnet protocol. That is, the randomness property of these is powered by the decentralized nature

aesedepece requested changes Nov 5, 2021

View reviewed changes

lrubiorod force-pushed the add_rng branch from 8f922cc to df78aef Compare November 10, 2021 15:33

Tommytrg reviewed Nov 12, 2021

View reviewed changes

doc: include RNG documentation

c79809a

lrubiorod force-pushed the add_rng branch from df78aef to c79809a Compare November 12, 2021 10:14

aesedepece approved these changes Nov 12, 2021

View reviewed changes

lrubiorod merged commit c79809a into witnet:master Nov 12, 2021

gitbook-com bot pushed a commit that referenced this pull request Jun 22, 2022

GitBook: [#98] Annex Finance & Mai.finance price feed requests

81a2dfa

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

doc: include RNG documentation #98

doc: include RNG documentation #98

Uh oh!

lrubiorod commented Nov 3, 2021 •

edited

Loading

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

aesedepece Nov 5, 2021

Uh oh!

Tommytrg Nov 12, 2021

Uh oh!

Tommytrg Nov 12, 2021

Uh oh!

Tommytrg Nov 12, 2021

Uh oh!

Tommytrg Nov 12, 2021

Uh oh!

Tommytrg Nov 12, 2021

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	mainnet. To retrieve this new functionality those are the changes:
	mainnet.

		are not necessary, so the `url` will be empty and the `script` won't be read so we can specify the code
		for an empty array. We only use an only retrieval for this kind of requests.

	are not necessary, so the `url` will be empty and the `script` won't be read so we can specify the code
	for an empty array. We only use an only retrieval for this kind of requests.
	are not necessary: the `url` field must be empty and the `script` field will be ignored, so we can specify the CBOR code for an empty array ([128]`). A single source is used in the retrieval section of this kind of requests.

		Aggregation is not necessary due to RNG requests has only one retrieval. To unwrap the `RadonArray` with
		only one element we will use the `Mode` as a `RadonReducer` without filters.

	Aggregation is not necessary due to RNG requests has only one retrieval. To unwrap the `RadonArray` with
	only one element we will use the `Mode` as a `RadonReducer` without filters.
	Aggregation is not necessary due to the fact that RNG requests have only one retrieval. To unwrap the `RadonArray` into a single element, we will use the `Mode` as a `RadonReducer` without filters.

	The Witnet RNG request shares the same structure as a normal request with the 3 stages (retrieval, aggregation and
	The Witnet RNG request shares the same structure as an HTTP-GET request with the 3 stages (retrieval, aggregation and

	field must be empty and the `script` field will be ignored, so we can specify the CBOR code for an empty array
	field must be empty and the `script` field will be ignored so we can specify the CBOR code for an empty array

	random vector of 32 bytes, instead of reading data from an API source. The rest of fields are not necessary: the `url`
	random vector of 32 bytes, instead of reading data from an API source. The rest of the fields are unnecessary: the `url`

	by the witnesses, concatenate them into a single vector of bytes and hash them with SHA256. In the same way as in the
	by the witnesses, concatenates them into a single vector of bytes and hash them with SHA256. In the same way, as in the

	randomly by the Witnet protocol. That is, the randomness property of these are powered by the decentralized nature
	randomly by the Witnet protocol. That is, the randomness property of these is powered by the decentralized nature

doc: include RNG documentation #98

doc: include RNG documentation #98

Uh oh!

Conversation

lrubiorod commented Nov 3, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lrubiorod commented Nov 3, 2021 •

edited

Loading