> 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/economic-model/nft-utility.md). # NFT Utility ## **Jockeys** There will be 8888 jockeys in total. The first XXXX will be free-minted minted through a whitelist and waitlist during the launch. The other jockeys will be made available through mint-for-ETH sales throughout the phases. ## **Stables** The number of stables is capped by jockeys until phase 5 (8888 jockeys, for every jockey a stable). After phase 5, more stables will be made available through mint-for-$stable sales. A stable can hold at most 5 horses, of which 1 can be a pregnant horse. The capacity can be upgraded with consumables. Stables can be sold to other users. ## **Horses** Horses must be bred in stable by one male and female in a stable. During pregnancy, the female horse is frozen. Neither training nor racing is possible during this period for the mare. Males during the pregnancy period have reduced stamina. This is to have an "incurred cost" to minting more horses. This way the number of newly minted horses are controlled. ## **Race tracks** Race tracks require jockeys to be stakelocked to be minted. Once more and more jockeys get frozen “into” race tracks, this will cause a deflationary dynamic for the jockeys. Racetracks get burned once the player decides to pull out their jockey again. Race track owners will receive $stable during race-to-earn inflationary epochs, and can take the spread on bets during the race-to-win static epoch. --- # 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/economic-model/nft-utility.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.