> For the complete documentation index, see [llms.txt](https://docs.tea.xyz/tea/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tea.xyz/tea/i-want-to.../begin-earning-tea-and-interact-with-the-protocol/donating-to-oss-projects.md).
# Donating to OSS Projects
## Why donate to OSS Projects via the *tea* Protocol?
Donating to OSS projects via the ***tea*** protocol allows you to directly support the development and maintenance of open-source software that you rely on and appreciate. Donations also affect dependencies by trickling down to them, providing a strong foundation for software to be built upon.
Donations via the ***tea*** protocol provide you with a way to track and audit donations that either you or others made to any OSS project. As all donations are stored on the blockchain, donors automatically receive on-chain recognition as their donation is visible for other community members to see. This transparency and accountability is very important to both users and package maintainers and is made possible by the power of the immutable ledger which the blockchain provides.
## How to donate to OSS Projects on the *tea* protocol
To donate TEA to a project of your choosing, follow these steps:
1. Navigate to the Projects Leaderboard and click on the project you would like to donate to.
2. Click on "Make a Donation" button and input donation amount.
3. Wait for the transaction to be confirmed.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tea.xyz/tea/i-want-to.../begin-earning-tea-and-interact-with-the-protocol/donating-to-oss-projects.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
