> For the complete documentation index, see [llms.txt](https://stableempires.gitbook.io/stable-empires-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stableempires.gitbook.io/stable-empires-litepaper/introduction/what-we-do.md). # What we do Stable Empires is a partially on-chain tamagotchi-style horse-breeding, horse-training, stable-management, racing experience game that has decentralised user-owned racetracks. ### Not just horseracing In Stable Empires there are many roles that a player can take. It's not just about betting on races. The game offers multiple styles of gameplay, in which somebody may choose to never actually participate in a race and instead choose for a horse-breeding, horse-training or stable-management play that is both fun - and if done correctly: profitable! ### Partially decentralized, gameplay protected Because large sums of money will likely be involved in the outcomes of races, the results would be gameable by sophisticated parties if entirely everything were to be on-chain. Stable Empires is as decentralized and on-chain as possible to protect the outcomes of the races from manipulation. And when we say decentralized, we mean it. Whereas many games offer tokens and player NFTs that are on the blockchain, the creators still own the house in which the players play. That, in our vision, is a form of centralization where the creators still own the most fundamental part of the game. Not very web3-friendly, and not very fun either. ### Own the player, or own the house We decided to do it differently. In Stable Empires, one can invest in a racetrack and maintain it to facilitate games for other players to play on. The game has a race-matching interface on which the racetrack-owners can put up their racetrack for people to choose. The owner gets paid part of the fee and with that create their own profitable business in Stable Empires. --- # 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://stableempires.gitbook.io/stable-empires-litepaper/introduction/what-we-do.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.