EntroBeam

Searchâ€¦

Entropy Chain

The entropy chain is another set belonging to the entropy registry set. It is a set used to determine which entropy to deliver to a user entropy that has not yet been assigned a secure entropy (reveal or settle seed). v1.0.0 has the following attributes:

bytes32 entropyByUsers; //end-user entropy seed

uint256 entropyByBlockNumber; //Seed block.number. Interacts with 'struct_blockCount' and is used to divide the token quota per block.

address SourceAddress; //address of the user who sent the seed.

uint256 leftgas; //Each gas fee to Tx is applied to calculate the median and average values of the entropy chain.

`entropyByUsers`

is the same as `usersEntropy`

of Entropy Registry. `entropyByBlockNumber`

is the block number that the Transaction(TX) succeeded. `SourceAddress`

is the account address of the user or contract that generated the TX. The number assigned to the element number of the Entropy Chain is the number of the Assined_entropy chain (Entropy registry No.).

`leftgas`

These are the gas fees sent by TX to EntroBeam, which EntroBeam aggregates and shuffles to determine which user seeds to mix with the secure entropy. Refer to Revealing Entropy for details.The length of the entropy chain is not fixed. The initial value connects ten transactions, but the length increases as user participation increases. In general, the point to be problematic is that if the length of the entropy chain is

$p$

, the probability of predicting which secure entropy will be generated may appear to be $1/p$

. But it is far from that. Number of user transactions is $n$

, When multiple transactions occur, and reveal entropy values accumulate, users get the number of cases $p^n$

, which exponentially reduces the probability of predicting the secure entropy.Entropy chains are indexed by numbers assigned to the entropy registry. To verify that the *entropy registry* and *entropy chain* have been successfully searched, users should check whether

`usersEntropy`

and `entropyByUsers`

match. It seems like a duplicate state, but it allows for a more clear check.I.g., Entropy Chain.length is 8

The entropy chain has a feature of an array, but the starting element number is 1. zero was initialized when the contract was deployed. However, the entropy chain does not match the entropy registry number because the array order gets jumbling as the transaction progresses increases. Only the internal order of the entropy chain changes, the order of the entropy registry never changes.

`FormationNumber`

variable through Block Explorer.Last modified 4mo ago

Copy link