> 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/tokenomics.md). # Tokenomics * **Total Supply:** 1 Billion Tokens * **5 Chains:** Ethereum, BASE, Binance Smart Chain, Arbitrum, Solana. * **EmpaFee Bridge**: $EPF can be bridged across all chains within our ecosystem. **Tax Mechanism (3% on Buys and Sells):** * **EVM Chains (ETH, BASE, BSC, ARB):** On these chains, the 3% tax is automatically swapped into the chain’s native token (e.g., ETH, BNB, ARB). 70% of the proceeds will be manually donated to charities, while 30% will be reinvested into the project for operational and marketing purposes. * **Solana:** On Solana, the 3% tax is collected in $EPF tokens. The community will participate in deciding what to do with the collected tokens—whether to burn them, bridge to other chains, or donate. **Key Features:** * **No Team Tokens Held Back:** Consistent with the decentralized nature of the project, no tokens have been held back for the team. * **The EmpaFee Bridge:** Developed in partnership with the industry-leading team at [Wormhole](https://wormhole.com/). --- # 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/tokenomics.md?ask=&goal= ``` `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.