> For the complete documentation index, see [llms.txt](https://stonkfun.gitbook.io/stonkfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkfun.gitbook.io/stonkfun-docs/earning/holder-rewards.md). # Holder rewards On a reward coin, trading fees go to holders instead of the creator. There is no claiming step. ![The rewards dashboard](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-7e98868ba661f5ca6a29a7d90305ea663d24890b%2Frewards-stats.png?alt=media) ## Where the money comes from A reward coin's mint carries a transfer tax that is withheld on every transfer, on any venue. The platform collects that tax, swaps it into the quote token, and pays it out pro-rata to holders. You are paid in the quote token, meaning whatever the launch is paired against, not in the launched token itself. ## How often Distributions run continuously in the background. There is nothing to claim and nothing to sign. ## Who is eligible A wallet needs to hold at least **`$20`** of the launched token. That bar is set in the units a buyer actually thinks in: hold `$20` of the token and you earn its fees. It also makes splitting a position across wallets strictly losing, since each fragment would have to clear the bar on its own, and it keeps distributions off airdrop dust. There is a second, much smaller floor on individual payouts, so that the platform is not spending a transaction to deliver a fraction of a cent. If the token's own price cannot be read at that moment, the `$20` bar is not applied. A price outage widening a distribution to some small holders is harmless; freezing payouts because a feed blinked is not. ## Nothing carries between rounds Rewards go to whoever holds at the moment of distribution. Nothing accrues to a wallet between rounds. A holder too small to clear the bar in a given round simply is not paid that round, and their share is re-split among those who are. This is why eligibility cannot be a fixed percentage: it depends on how big that round's pot happens to be. ## Your first payout The first time you are paid in a given quote token, an account has to be created for you to receive it. That cost is taken from the pot as a whole rather than charged to you individually, and after that your account exists permanently and you are paid every round at ordinary transaction cost. Because that cost is real, first-time recipients are onboarded gradually, largest holdings first, rather than all at once out of a single round's pot. ## Why a small slice is kept back Every collection, swap and payout costs SOL, and those costs belong to no individual holder. A small percentage of each pot is retained to cover them, which is what keeps distributions running without manual funding. It is always rounded in the holders' favour, and it is only taken when a distribution actually pays someone. ## How the split is calculated Each eligible holder receives a share of the pot proportional to their balance, always rounded down. Rounding down guarantees the payouts can never sum to more than the pot. The leftover, which is at most a fraction of a token, stays in the pot and rolls into the next round. ## Reading rewards data ```bash # Platform-wide totals and recent distributions curl 'https://www.stonkfun.xyz/api/public/v1/rewards' # One token's distribution totals curl 'https://www.stonkfun.xyz/api/public/v1/tokens//rewards' ``` Standard launches answer with `mode: "standard"` and a null rewards object. --- # 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://stonkfun.gitbook.io/stonkfun-docs/earning/holder-rewards.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.