> For the complete documentation index, see [llms.txt](https://doc.hivereward.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.hivereward.co.uk/limitless-miners.md). # Limitless Miners An incremental Web3 mining game on the Hive blockchain. ## Limitless Miners Limitless Miners is an incremental Web3 mining game built on Hive. Build and expand a mining operation over time. Progress continues through idle gameplay and blockchain-backed assets. ### Core gameplay Manage your mining operation and improve its output. Each upgrade strengthens your long-term progression. #### Card merge system Combine two matching base cards to create a higher-level card. Each merge increases card stats by **50% per level**. Merge costs increase by **25%**, balancing stronger upgrades with rising investment. ### Economy and architecture Limitless Miners operates natively on the Hive network. It uses Hive-Engine smart contracts and decentralized asset management. #### Drought protection An automated backend monitoring script protects reward pools from rapid liquidity depletion. The system monitors and regulates payouts for these assets: * `STARBITS` * `SWAP.HIVE` * `HASHSCORE` This protection supports a more resilient in-game economy during sudden changes in liquidity. ### Art direction The game uses a clean, high-contrast black-and-white visual style. Its 2D vector cutout assets create a unified, minimalist look across the game. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.hivereward.co.uk/limitless-miners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.