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

# Tax (Donation) System

At the heart of **EmpaFee's** mission is our commitment to making a tangible difference in the world through every transaction. Our tax system is designed not only to support our ecosystem but also to contribute meaningfully to humanitarian causes. Here’s how it works and why it matters.

Every buy or sell transaction within the **EmpaFee** ecosystem incurs a 3% tax. This tax serves two key purposes: supporting charitable causes and sustaining the growth of **EmpaFee** itself. Let's break down how this works across chains:

***

***EVM Chains:***

* The tax collected is automatically swapped into the chain's native asset (e.g. ETH, BASE, BNB, ARB).
* Manual Donation Process: On a regular basis, 70% of the tax revenue is donated to Charity on-chain. This manual process allows flexibility in managing funds and optimizing contributions for greater impact.
* The remaining third goes to **The EmpaFee Fund** to support impactful initiatives and sustain the ecosystem.

***

***Solana Contract: Community-Driven Governance***

* **Tax in $EPF Tokens**
  * On Solana, the tax is collected in $EPF tokens rather than being converted into a native asset. This allows for a unique level of community engagement.
* **Community Governance:** Holders have the power to decide how to best utilize the collected $EPF tokens, with options that include:
  * Bridging to New Chains: Supporting cross-chain liquidity and creating arbitrage opportunities.
  * Burning Tokens: Reducing the total supply and potentially enhancing value.
  * Swapping and Donating: Converting tokens to SOL and making direct donations to charities.

***

**Why the Tax System Matters**

1. **Transparency and Trust**\
   The blockchain records every donation, ensuring that all contributions are verifiable and traceable, fostering trust among community members.
2. **Efficiency and Security**\
   Automation reduces the risks of manual errors and potential fraud. Smart contracts ensure funds are distributed according to the predetermined rules without any tampering.
3. **Scalability Across Chains**\
   As EmpaFee expands to more chains, transaction volumes—and consequently, donations—will increase. This scalability means a growing impact, with the tax model remaining consistent and effective.

***

**Making a Real-World Difference**

By participating in **EmpaFee**, you're not just trading a cryptocurrency—you're contributing to a movement of decentralized philanthropy. Every transaction makes a difference, supporting vital humanitarian causes and building a new, inclusive model of giving. Together, we aim to harness the power of blockchain to create a better world.

Join us on this journey, where every transaction matters, and together, let’s redefine what it means to give back through decentralized finance.


---

# 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://empafee.gitbook.io/empafee-whitepaper/tax-donation-system.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.