> For the complete documentation index, see [llms.txt](https://gitbook.datsproject.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.datsproject.io/overview/our-approach.md).

# OUR APPROACH

1. Participants download the DATS Project Desktop application. (Participants do not have to install any Linux distribution and invest in hardware.)
2. &#x20;Participants dedicate their system resources such as CPU, GPU, and internet bandwidth to the project.
3. Through those system resources, the needed computing power of DATS Project services is ensured.
4. Clients can use needed the services through our computing power marketplace.
5. Defined tasks are shared among the participants and completed in the fastest way possible.
6. 60% of the income is shared with the participants.

**Besides that the DATS Project will be able to develop addition al services through its immense computing power in line with to the customer demands.**

{% embed url="<https://www.youtube.com/watch?v=hOvPA9h267U>" %}


---

# 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://gitbook.datsproject.io/overview/our-approach.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.
