# DUEL’s Provable Fairness

Whenever random number generation (RNG) is required, the DUEL platform uses[ RANDOM.ORG](https://random.org) to generate the random numbers in a process that is transparent and provably fair.

Random.org offers true random values to anyone through their API. Users are issued tickets and use the ticket to generate random numbers or strings. Anyone can audit and verify the status of a ticket as they are always discoverable[ here](https://api.random.org/tickets/form). This feature random.org allows us to prove the fairness of the game results.

When a game is created on the DUEL platform, we issue a random.org ticket through the random.org API. We then generate the random values corresponding with that ticket when the game has ended. At no point can DUEL control the generated random value. The generated random value can only be generated by the ticket, which allows this process to obtain true random status.

With this system, anyone is able to verify: 

1. Whether the ticket was used to generate random values after the game ends. 
2. The random value generated by the ticket. 
3. Whether the result of the game matches with the result calculated by the random value and provided code snippet.

For example, [here](https://api.random.org/tickets/form?ticket=21349c0c5472cb80) is an example of a ticket which has not been used yet.

And[ here](https://api.random.org/tickets/form?ticket=5c8166391c37865e) is the example of a used ticket, which generated the string **azIEfVgM\`9.**

### **Jackpot**

1. A game is created when the first player places a bet. When the game is created a ticket is issued and shared with the players through the UI. Players can check and verify that the ticket has not been used until the game ends.
2. When the game has ended, a random string is generated by the ticket issued when the game was created. Players can check the generated string was generated by the appropriate ticket.
3. Players can run the code snippet provided below with the generated random string from the ticket to check the result.

<figure><img src="/files/eITSSLX37b9Qri838oL8" alt=""><figcaption></figcaption></figure>

### **Coinflip**

1. A game is created when the first player places a bet. When the game is created a ticket is issued and shared with the players through the UI. Players can check and verify that the ticket has not been used until the game ends.
2. When the game has ended, a random string is generated by the ticket issued when the game was created. Players can check the generated string was generated by the appropriate ticket.
3. Players can run the code snippet provided below with the generated random string from the ticket to check the result.
4.

```
<figure><img src="/files/ddikm5PrVcg9ASqsfHV2" alt=""><figcaption></figcaption></figure>
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.duel.win/more-info/duels-provable-fairness.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.