> For the complete documentation index, see [llms.txt](https://navyai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navyai.gitbook.io/docs/gpu-contribution-program/contribution-flows.md).

# Contribution Flows

Fact, graphics cards of sufficient quality for training LLM models, such as the RTX 3080 or higher, are exceedingly rare, while weaker graphics cards are readily available in abundance. So, why don't we merge all the low qualify graphic card to create a new one that qualify enough for training LLM ?

<figure><img src="/files/HNyn1CknrQq7Ec03hABQ" alt=""><figcaption></figcaption></figure>

Step 1: User contributes GPU configuration \
Step 2: NavyAI's productivity tracking system will evaluate and mine the performance of the configuration.\
Step 3: After completing the mining process, the performance of the configurations that the user contributes will be merged through the merging system and performance synthesis. \
Step 4: Create a virtual server with input performance taken from the merging system \
Step 5: Provide virtual servers to decentralized GPU platforms as a worker.


---

# 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://navyai.gitbook.io/docs/gpu-contribution-program/contribution-flows.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.
