> For the complete documentation index, see [llms.txt](https://fightly-ai.gitbook.io/fightly-ai-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fightly-ai.gitbook.io/fightly-ai-whitepaper/sustainability-commitment.md). # Sustainability Commitment Technology should serve progress without compromising the environment. Fightly AI contributes to sustainability by optimizing the use of existing hardware and reducing the need for new infrastructure. By running multiple workloads on shared nodes, energy use is minimized, and electronic waste is reduced. The network also supports research into energy-efficient algorithms, ensuring that AI training and security processes consume fewer resources. In the long term, Fightly AI aims to integrate renewable energy partnerships, where contributors who operate on clean energy can earn additional rewards. This sustainability commitment positions Fightly AI not only as a technological project but also as a movement towards responsible innovation. --- # 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://fightly-ai.gitbook.io/fightly-ai-whitepaper/sustainability-commitment.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.