> For the complete documentation index, see [llms.txt](https://battlestakes.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://battlestakes.gitbook.io/whitepaper/battle-stakes.md). # Battle Stakes {% hint style="warning" %} **Disclaimer:** This whitepaper is to provide additional information about how the protocol "Battle Stakes" is designed and will function. Nothing in this paper is intended to be financial advice or promises of future income generation. Participation assumes you are aware of any potential risks involved in cryptocurrency. {% endhint %} The Battle Stakes Ecosystem is an innovative DeFi protocol that is designed to be a hybrid of a staking protocol and a play-to-earn project. The protocol enables users to earn rewards in 3 different ways. This will include payouts in stable coins($BUSD), rewards in a native coin to the protocol $GEN, and $ARENA - a token designed to increase in value as the battle stakes network grows. The treasury and the liquidity pool will be backed by a never before used, experimental, Recursive Neural Network Machine Learning Trading Bots. The system has been used in beta/paper testing mode for the last 28 months(since 4/2020). The results produced were beyond extraordinary. Further testing in bear market scenarios of 2021 and 2022 confirmed the results and strengthened the machine learning database. It was decided in the summer of 2022 to give indirect access to this trading system via an interactive interface now known as Battle Stakes. The trading system will not work if funds are moved in and out of the pool, therefore a reward system that incentivizes long term hold had to be implemented. Early penalty withdraw mechanisms were added as well. This all became known as the Battle Stakes Ecosystem. The yields that are paid out to players were compiled based on the impressive test results over more than 2 years in every possible market scenario. ### Guides: Jump right in Follow our handy guides to get started on the basics as quickly as possible: {% content-ref url="/pages/v9oE6arWFXdUpIDiHTwy" %} [Yield Farming](/whitepaper/getting-started-and-basics/yield-farming.md) {% endcontent-ref %} {% content-ref url="/pages/vqs5GfvlSPJiHWoQA0Q9" %} [Using Metamask](/whitepaper/getting-started-and-basics/using-metamask.md) {% endcontent-ref %} ### Fundamentals: Dive a little deeper Learn the fundamentals of Battle Stakes to get a deeper understanding of our main features: {% content-ref url="/pages/4j1iVci8kav1dMMxKqPw" %} [Basics of Battle Stakes](/whitepaper/basics-of-battle-stakes/battle-stakes-intro.md) {% endcontent-ref %} {% content-ref url="/pages/7iB4awwrA1j4ROktCluF" %} [Strategies](/whitepaper/strategies/1-wallet.md) {% endcontent-ref %} {% content-ref url="/pages/3yJneVkmzjBW4fNukTsX" %} [Tokenmomics](/whitepaper/tokenmomics/supply-+-pre-launch-allocation.md) {% endcontent-ref %} {% content-ref url="/pages/EkP8GVeXUz2q98weosCt" %} [Protocol Specific Functionality](/whitepaper/protocol-specific-functionality/wallets-overview.md) {% endcontent-ref %} --- # 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://battlestakes.gitbook.io/whitepaper/battle-stakes.md?ask=&goal= ``` `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.