> For the complete documentation index, see [llms.txt](https://gympfy.gitbook.io/gympfy-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gympfy.gitbook.io/gympfy-whitepaper/whitepaper-gympfy/sweat-points-the-fuel-of-evolution.md). # Sweat Points: The Fuel of Evolution They were created to transform validated physical effort into progress within the platform, serving as the bridge between completed activities, user evolution, and access to the ecosystem's various features. More than just a simple score, SWEAT Points represent the energy generated by each user's active participation in their own journey of health and development. #### How SWEAT Points Are Obtained SWEAT Points are generated through physical activities validated by the system. Each completed exercise contributes to the accumulation of points, according to the validation criteria defined by the platform. The amount earned can vary based on factors such as: * Performance * Completed challenges * Active benefits * The evolution stage of your Evolution Companion In this way, the system creates a direct relationship between real effort, consistency, and progression. #### Consistency Over Intensity Gympfy was not designed to reward only isolated moments of high performance. Its main objective is to encourage the building of sustainable, long-term healthy habits. For this reason, consistency plays a central role in generating SWEAT Points. > We believe that small actions repeated continuously produce more significant results than intense, sporadic efforts. #### The Fuel of the Ecosystem SWEAT Points are integrated into several fundamental mechanics of the platform. Their applications include: * Recharging the energy of Evolution Companions; * Unlocking specific features and experiences; * Acquiring customization items; * Accessing ecosystem benefits and initiatives; * Participating in the conversion mechanisms for the $GYM token. New utilities may be incorporated as the ecosystem evolves. #### The Bridge Between Movement and Value Within Gympfy’s architecture, SWEAT Points occupy a strategic position. They connect validated physical activities to the progression systems, Evolution Companions, and the economic layer of the platform. The entire growth flow of the ecosystem begins with a simple action: movement. By transforming exercise into SWEAT Points, Gympfy creates a structure where participation, recognition, and evolution remain connected to the real effort put in by users. #### A Participation-Based Economy SWEAT Points represent one of the most important expressions of Gympfy's philosophy. Each generated point is directly associated with validated movement, active participation, and commitment to one's own evolution. The goal is not just to create a reward. The goal is to build a system where healthy habits generate visible progress, growth opportunities, and an experience capable of encouraging the continuity of the journey over time. --- # 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://gympfy.gitbook.io/gympfy-whitepaper/whitepaper-gympfy/sweat-points-the-fuel-of-evolution.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.