Frequently Asked Questions

How does the system behind EZRage operate?

Each player can deposit up to 20 VGO items per deposit. The items must sum up to at least 1.00. The placed sum influences your chance of winning. Although the winnerticket is picked randomly, you can increase your chance of winning by having a bigger percentage of the round.

How high is EZRage's per-pot rake?

Depending on which items are available in the pot, we aim to take no more than 9-11% in the form of one single item, in some cases even less. If the smallest item in the pool is worth more than 11% of the whole pool, we do not take any rake.

How do I validate a round with the new Provably Fair?

Our new provably fair system uses a 3rd party website (Random.org) for generating random seeds, making our provably fair system 100% legitimate and winning tickets cannot be predictable before the round ends. As soon as the round starts, the server generates a random seed and makes it into hash presented to our users using the SHA256 hashing algorithm. When the round ends, our system reaches out to Random.org for a randomly generated string with will be used to calculate the winning module (you can check the time our system reaches out to their API as well as serial number). After that, our server generates the hash which will be used to generate the winning module using server seed and random.org string:

const mod = server_seed+'-'+random_seed;
Code which we use to generate winning module (we are using the node chance package):
const chance = new ChanceJS(mod); 
const percentage = ((chance.floating({min: 0, max: 100, fixed: 6}))/100);
At the end, when the winning module is generated, the server calculates the winning ticket using the jackpot sum multiplied by winning module.
const ticket = jackpot_sum * percentage;
We have also store every random.org response (serial numbers) to prove that we didn't made multiple calls at the end of the round.

The new Coinflip game mode uses exactly the same system described above to generate the winning ticket. On Coinflip, the T-Side (red coin) will always take the low ticket portion, while the CT-Side (blue coin) will always take the high ticket portion.

How do I validate a round with the old Provably Fair?

At the beginning of each round a "Secret"(Salt) is randomly created, and a SHA-1 Hash gets generated out of it and shared publicly. The winning ticket is generated at the end of a round, with unpredictable values. As soon as a round is closed an MD5 Hash is generated with the total value of the round (eg. 123.10) and the Salt that was generated in the beginning.

As an example, the MD5 hash of123.10-04495e619935d08c is4963362068a5aae28c0ab8e7994a0e75. Changing the value or salt the tiniest bit will result in a completely different hash. The total value and salt are seperated by a dash(-). The decimal point of the value is always a dot(.) and not a comma. The total value always has two decimal places.

After generating the MD5 hash, the first 8 characters of it are converted from hexadecimal to decimal (32 bit integer), and divided by4294967296 (Maximum value of a 32 bit integer). This will result in a Decimal number between 0 and 1 which is the winnerticket. We do not provide an automated Provably-fair calculator for reputability reasons. Required calculators can be found with Google searches:

Why did the arrow stop on a different person than the one who won when picking the winner?

Since we work with a Ticketsystem, and a winning percentage to pick the winner, and the because the chart has subdivisions / because of rounding errors it is possible that there are small margins between whats displayed, and the actual winner. The animation is just there for entertainment purposes, and the correct winner can always be seen in the Game history.