> 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/two-layers-of-value.md).

# Two Layers of Value

This architecture ensures that evolution within the platform is driven primarily by healthy habits, consistency, and active participation, reducing dependency on the natural fluctuations of digital markets. By establishing layers with distinct functions, the ecosystem preserves the core user experience while expanding participation and utility possibilities over time.

To achieve this balance, Gympfy operates through two complementary layers: SWEAT Points and the $GYM token.

#### SWEAT Points

SWEAT Points represent the primary unit of participation and progression within Gympfy. They are earned by performing physical exercises validated by the platform and directly reflect the effort, consistency, and participation of users within the ecosystem.

These points can be used across various platform features, including:

* Profile customization;
* Partner-provided benefits;
* Maintaining streaks;
* Recharging Evolution Companions;
* Evolving user experience;
* Conversion into the $GYM token.

Because they are generated through validated physical activities, SWEAT Points function as the bridge between movement, progress, and participation within the ecosystem.

#### $GYM

$GYM represents the premium and governance layer of the ecosystem. It can be acquired by converting SWEAT Points or through direct purchase on compatible markets.

Its role is to expand interaction possibilities within the platform, allowing access to exclusive features, special items, unique experiences, and community governance mechanisms. While SWEAT Points are tied to daily progression and active participation, $GYM represents a strategic layer of long-term value and engagement.

#### Balancing Health and Economics

The separation between SWEAT Points and $GYM was conceived to protect the core user experience. Evolution within Gympfy continues to be built through physical exercise, consistency, and personal progress, while the economic layer acts as a complement capable of expanding opportunities and strengthening the ecosystem.

This structure allows individual growth to remain connected to healthy behavior, regardless of market dynamics.

#### A Sustainable Architecture

By separating progression from economics, Gympfy creates a more balanced foundation for the platform's development:

* SWEAT Points incentivize continuous participation and daily evolution.
* $GYM expands utility, benefits, and governance mechanisms.

Together, these elements form an architecture capable of connecting health, engagement, and value without compromising the ecosystem's core mission.

> The objective remains the same from the start: to use technology to encourage healthy habits and transform consistency into long-term evolution.


---

# 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/two-layers-of-value.md?ask=<question>&goal=<endgoal>
```

`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.