> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/ecosystem-components/platform/sweepfarm.md).

# SweepFarm

#### **What is Sweepfarm**

Sweepfarm is a blockchain-based agriculture and trade simulation game built around production, strategy, and economic growth.

Players build and manage their own farms, grow agricultural products, process them through machines, and generate income by participating in an in-game economy. The experience is designed not only for entertainment, but for strategic production, long-term planning, and sustainable value creation.

Rather than focusing on instant outcomes, Sweepfarm is structured around productivity. Users plant crops, harvest resources, convert them into more advanced products, and increase their value through production chains. As players complete tasks and activities, they earn XP, level up, and unlock more efficient production opportunities.

This progression system encourages continuous engagement while rewarding users who optimize production, plan ahead, and participate more actively in the ecosystem.

***

#### **How it works**

Sweepfarm begins with users establishing and managing their own production environment.

Players participate by:

* planting crops
* harvesting resources
* processing raw materials through machines
* converting basic goods into higher-value products
* selling products within the in-game economy

As users continue playing, they can choose different production strategies. Some may focus on selling raw goods for immediate liquidity, while others may prioritize processing resources into more advanced products for higher profitability. Users can also complete specific tasks and activities to gain XP more efficiently and accelerate their progression.

As XP increases, players level up. Higher levels unlock improved production efficiency and stronger economic positioning inside the game. This creates a system where progression is not only tied to time spent, but to how effectively a player manages production and growth.

Sweepfarm also includes a dynamic financial distribution model. A portion of in-game spending is redistributed to players based on their levels. This means progression is not only cosmetic or operational, but also directly connected to the user’s influence within the in-game economy.

***

#### **Key mechanics**

Sweepfarm is built around production, progression, and economic participation.

Its core structure is based on:

* agricultural production
* resource processing
* XP-based progression
* level-based economic distribution
* user-defined strategy

What makes Sweepfarm different is that progression is directly tied to productivity. Users do not simply wait for outcomes; they actively create value through farming, processing, and trading. The more efficiently they operate, the stronger their position becomes.

The in-game economy is modeled around real market logic. Users can decide how to allocate resources, when to sell, when to process for higher margins, and how to balance short-term returns with long-term growth. This makes Sweepfarm more than a simple farming experience. It becomes a structured economic system where planning and production directly affect results.

Built on transparent and sustainable Web3 infrastructure, Sweepfarm is not just a farming game. It is a production-based, profit-oriented Web3 economy where growth is driven by strategy, participation, and continuous value creation.


---

# 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://docs.sweep.finance/ecosystem-components/platform/sweepfarm.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.
