> For the complete documentation index, see [llms.txt](https://whitepaper.angryfloki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.angryfloki.com/charity.md).

# Charity

As one climbs the ladder in society, it is only right that they give back to the communities that helped them grow. The project attests that through cryptocurrency donations, more money gets to the hands of those that need it most. In the case of AngryFloki, the charity of choice will be aligned towards dogs and since the crypto donations will have low processing fees, more funds will get to these facilities helping dogs.

Our team is planning on holding monthy charity drives to both sensitize people on different issues and help raise money. This being a community-centric project, we have decided to collect 1% from each buy and sell transaction to go towards charity. The funds will be used as part of the donations to several charities.

We would also love to engage our members and hear what they have to say on this issue, mostly on the specific charities they would like us to donate to.


---

# 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://whitepaper.angryfloki.com/charity.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.
