# Fee Allocation ### Fee Allocation Fees are the fuel. At the initial stage, $FUEL plans to use a simple allocation model: * 50% — Solid Community Fund * 40% — Attention Growth Fund * 10% — Dev Allocation #### Solid Community Fund — 50% This is the core of $FUEL. A portion of fees will be directed toward selected resilient meme communities through Fuel Rounds, Attention Cup rewards, marketing support, content support, visibility campaigns, direct community support, and other community-focused initiatives. The goal is to return fuel to communities that have proven persistence, loyalty, and cultural energy. #### Attention Growth Fund — 40% This is used to grow $FUEL’s own attention engine. It may support content production, campaign assets, collaborations, Attention Cup operations, meme creation, banners, design, strategic exposure, moderator rewards, contributor rewards, translations, community operations, and other growth-related work. The purpose is not to spend for empty hype. The purpose is to increase the size of the attention loop, so future Fuel Rounds can send more fuel back into the meme ecosystem. #### Dev Allocation — 10% This is reserved for the dev. Building and maintaining $FUEL requires time, coordination, execution, and responsibility. The dev allocation exists so the project can be operated sustainably without hiding incentives behind vague language. $FUEL is an experimental project, and this allocation may evolve with community feedback. But the principle is fixed: Attention creates fees.\ Fees become fuel.\ Fuel returns to the meme ecosystem. --- # Agent Instructions: 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: ``` GET https://usdfuel-experiment.gitbook.io/the-usdfuel-manifesto/fee-allocation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.