# Algorithm

* **We compare $KIMBO and $Avax to "Trainers"**

1. ## - Revenue algorithm logic

   Users deposit $KIMBO or $AVAX on our Dapp to start hiring their Trainers. Trainers train $KIMBO with Treats. Users sell their Treats to make profits, Trainers work indefinitely for you, and users can withdraw profits until the contract balance is no longer sufficient.\
   \
   The entire operation involves <mark style="color:blue;">**purchasing Trainers with your $KIMBO or $AVAX - Trainers train $KIMBO with Treats - selling Treats for $KIMBO(revenue withdrawal)**</mark><mark style="color:yellow;">**.**</mark> You can also compound your Treats to acquire more Trainers and earn even more Treats.<br>
2. ## - Algorithmic formula related to income

* <mark style="color:blue;">**Trainer price = deposit amount / (deposit amount + contract balance) \* Kimbo market.**</mark>
* We can observe that the Trainer price is not fixed; it depends on several variables such as the deposit amount, contract balance, and the Kimbo market.&#x20;
* The earlier you enter the market, the more advantage you have!

<mark style="color:blue;">**Summary:**</mark> The daily interest rate is not stable at <mark style="color:blue;">**8%**</mark>; it will fluctuate based on various situations. First and foremost, the sooner you enter Kimbo Trainer, the greater your advantages. Secondly, during the project's operation, we can perform actions such as reinvestment to maintain our daily interest rate stable and growing. Finally, as long as the contract has a balance, it will be possible to withdraw funds.


---

# 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.kimbotrainer.com/kimbotrainer/algorithm.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.