> For the complete documentation index, see [llms.txt](https://docs.kaiprotocol.fi/kai-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiprotocol.fi/kai-protocol/english/protocol-and-mechanisms/chance-g/ladder-dice-beta.md).

# Ladder Dice Beta

### **Game Rules** <a href="#id-1907" id="id-1907"></a>

1. **A random number between 0 and 27 is generated every hour.**

* Just like the first generation game of Chance-G, a random number between 0 and 27 will be generated every hour using BNB Chain’s Chainlink VRF(\*).\
  \&#xNAN;**\*** Chance-G uses BNB Chain’s Chainlink VRF to call for transparent and fair random numbers.\
  \* Ladder Dice Beta VRF: <https://bscscan.com/address/0xF946eB67F711212933AF0CF03ec5A8217e0842dA#events><br>
* **\[Contracts]**\
  Fund Contract: 0xBbe7Ca2f92fb5E3FA308B786Bed67ec7Ffc36c4c\
  Game Contract: 0x8141e8ac11d5cb6e2c7dc5741ee2b142c38a499a\
  Chainlink VRF: 0xF946eB67F711212933AF0CF03ec5A8217e0842dA

**2.** **Below are options determined by a random number generated between 0 and 27.**

* You can place a bet on any of the four options, and if the option you selected matches with the number conditions, you can receive 1.95 times the amount you bet.
* 1\) O/E(Odd/Even): predict whether the randomly extracted number is odd or even.\
  \* Number of rungs on ladder will be affect the result of the destination of the ladder (whether L or R).\
  Three rungs for 0–13 and four rungs for 14–27.
* 2\) L/R (Left/Right): the destination of the ladder will be determined (left or right)depending on the results of the number(O/E, 3/4).

**3.** **Game Cycle: Every hour (1 round = 1 hour).**

**4.** **Betting Limits**

* The current version is in beta, and there are restrictions on the betting size as shown below for stability testing and other purposes.\
  The minimum bet is 1 KAI. You can bet up to 2,000 KAI for each betting options (four options) separately.
* The betting limit may be adjusted based on the size of the deposited KAI funds in the future.
* **Here are the example:**\
  \- Assume that a user bets on \[O: 100 KAI, L: 300 KAI].\
  \- If the random number is 15, the result is \[O, 4, L].\
  \
  **Therefore, the user can claim a total of 780 KAI.**\
  \- O betting result: +195 KAI (100 x 1.95)\
  \- L betting result: +585 KAI (300 x 1.95)

### **\[G-Fund]** <a href="#id-6a85" id="id-6a85"></a>

* KAI holders can mint LP token by providing KAI token as a liquidity. 0.1% fees will be paid when minting the LP token. After minting LP token, LP token holders will be able to sold the tokens after 7 days.
* By providing liquidity, LP token holders may (or may not) earn fees generated from every round.
* If the betting amount that failed to match the option of the random number is greater than the size of the matched option amount, token holders will earn benefits.
* In the opposite case (when the amount of the winnings players are greater), losses may occur.
* Part of the fees generated from the players will be deposited into the G-Fund.\
  \- 195% of the betting amount goes to the player who matched.\
  \- 2.5% is burned.\
  \- 2% is deposited to KAI LP.\
  \- 0.5% is used for marketing expenses.
* **Example:**\
  Let’s assume that 100:100 is bet on both L/R.\
  **If R wins,**\
  \- 95 KAI of the 100 KAI bet on L will be paid to R, and the remaining 5 KAI will be used for the following purposes:\
  \- 2.5 KAI will be burned, 0.5 KAI will be used for marketing, and 2 KAI will be deposited into the KAI fund.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.kaiprotocol.fi/kai-protocol/english/protocol-and-mechanisms/chance-g/ladder-dice-beta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.