February 18, 2026

Niguez Randomity Engine – Niguez Randomity Engine

Niguez Randomity Engine – Niguez Randomity Engine

Introduction

Generating a pseudorandom number from the blockchain as an entropic source is a formidable task, especially when the miners influence the block gas limit, block-hash and block time, this may change as the network adheres to Proof of Stake (Casper POS, Serenity). It depicts a stern complication for programmers who endure establishing a trust-less internal deterministic source of entropy for Ethereum blockchain, whose essence inclines to be transparent.

The complication

Since the blockchain is conspicuous, EVM bytecode on the blockchain is evident to all the existing nodes for verification. Nevertheless, reverse-engineering (decompile) bytecode back to perfect original source code in a stack-based architecture is computationally impossible due to name omission of variables, functions and types; particularly if the smart contract is optimised, obfuscated and self-modifying, the decompiler may generate pseudo-code but this is far from the original. This settles one issue and generates another as there is a perception of reluctance and lack of confidence to interact with a closed source smart contract.

The solution

The block variables in their raw form are susceptible to influence or effortless prediction (In POW or Future Casper POS) by various parties. The solution to this problem is extensively mixed hashing (keccak256) of the contributing factors to the point that influencing block variables and predictions prove ineffective on the final hash output.

The problem here is after all the mixed hashing the creator of such smart contract (Niguez Randomity Engine) will identify what the outcomes of certain blocks are and hence may use this to their advantage. Therefore, no entity will use such a facility as it is imperative and necessary to provide a degree of freedom and customisations to the random number end users.

The pseudorandom numbers generated are 24 sequences of unsigned integers of 256 bits. The end user could use any sequence, cross sequence, allocate a slot in a sequence and re-hash it. Thus, the smart contract creator has no influence due to the fact that the contract is immutable. Accordingly, the smart contract creator is incapacitated to comprehend and influence the sequences or slots of the random number a user picked. Consequently, a user can only have control over the customised sequence they generate but not the outcome of the random number, avoiding prediction of numbers all through.

What is Niguez Randomity Engine?

Niguez Randomity Engine is a smart contract deployed on the Ethereum blockchain that functions on the foretold protocol. It is immutable, providing impulsive sequences of pseudorandom number with every block.

In the scenario of influenced blockchain variables, Niguez Randomity Engine makes them redundant due to its very essence. It is an immutable smart contract and cannot predict and dictate the slots determined by the user. It serves as an escrow for random numbers.

In conventional pseudorandom number, the pattern tends to repeat, that is not the instance with this randomity engine as it uses a cryptographic hash function. Hence, every sequence is non-repeating and unique; if the sequences repeat, that would be considered an instance of a hash collision.

The engine still renders the sequence of random numbers even if the block variables are unpublished. Utilities, the likes of ‘web3.eth.getStorageAt()’ are redundant because nothing is stored in the storage and the contract dependencies are self-modifying.

The pseudorandom sequences generated are named alphabetically from ‘Ra’ to ‘Rx’, that is 1 to 24 respectively. The illustration below elucidates the mechanism of this randomity engine.

Published at Fri, 21 Jun 2019 16:33:52 +0000

Previous Article

Facebook’s Libra Pushes France to Form a G7 Crypto Task Force

Next Article

Quantstamp Releases Decentralized Security Protocol with Staking and Improved Transparency

You might be interested in …