> For the complete documentation index, see [llms.txt](https://docs.div.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.div.fun/for-traders/receiving-dividends.md). # Receiving dividends This is the shortest workflow on div.fun, because there is almost nothing to do. Hold an eligible balance of a div.fun token, and dividends arrive in your wallet on their own. ### What you do 1. **Buy** a div.fun token that is being traded. 2. **Hold** it in your own wallet. That is the entire process. There is no staking, no locking, no claiming, and no gas to pay to receive. ### What happens behind the scenes 1. Each trade (curve or pool) sets aside the [dividend share](/core-concepts/dividend-distribution.md). 2. That share is converted to the token's [reward asset](/core-concepts/reward-assets.md). 3. The [keeper](/protocol/the-keeper.md) distributes the reward asset to holders, proportional to [eligible balance](/core-concepts/reward-eligibility.md), by sending it directly to wallets. You receive the reward asset as a normal token in your balance — wrapped HYPE, a stablecoin such as USDC, or a tokenized stock, depending on the token. ### When dividends arrive Distribution is **periodic**, not instantaneous per trade. The keeper works through holders over time, so dividends arrive in batches. Over any meaningful window, what you receive reflects your share of the eligible supply and the volume the token traded. A token with heavy volume pays its holders more often and more; a token that is not trading pays little or nothing until it does. ### Seeing your dividends * **In your wallet** — the reward asset appears in your token balance directly. * **In your** [**portfolio**](/for-traders/your-portfolio.md) — div.fun aggregates what you hold and what you have received across tokens. * **On the token's** [**page**](/for-traders/the-token-page.md) — the dividend history shows the token's distributions over time. ### If a reward asset is a tokenized stock Stock dividends settle through HyperCore and arrive as the stock's ERC-20 token in your wallet. The path is more involved than a simple transfer — see [How stock dividends work](/stock-dividends/how-stock-dividends-work.md) — but from your side the result is the same: the asset shows up in your balance. Some tokenized stocks may restrict which wallets can receive them; where that applies, it is handled by the protocol's design without blocking distribution to other holders. ### The point Dividends on div.fun are designed to require nothing of you. Buy, hold, get paid. The only decision that matters is which tokens to hold — and that decision is what the [board](/for-traders/the-board.md) and [token page](/for-traders/the-token-page.md) are built to inform. This is the shortest workflow on div.fun, because there is almost nothing to do. Hold an eligible balance of a div.fun token, and dividends arrive in your wallet on their own. ### What you do 1. **Buy** a div.fun token that is being traded. 2. **Hold** it in your own wallet. That is the entire process. There is no staking, no locking, no claiming, and no gas to pay to receive. ### What happens behind the scenes 1. Each trade (curve or pool) sets aside the [dividend share](/core-concepts/dividend-distribution.md). 2. That share is converted to the token's [reward asset](/core-concepts/reward-assets.md). 3. The [keeper](/protocol/the-keeper.md) distributes the reward asset to holders, proportional to [eligible balance](/core-concepts/reward-eligibility.md), by sending it directly to wallets. You receive the reward asset as a normal token in your balance — wrapped HYPE, a stablecoin such as USDC, or a tokenized stock, depending on the token. ### When dividends arrive Distribution is **periodic**, not instantaneous per trade. The keeper works through holders over time, so dividends arrive in batches. Over any meaningful window, what you receive reflects your share of the eligible supply and the volume the token traded. A token with heavy volume pays its holders more often and more; a token that is not trading pays little or nothing until it does. ### Seeing your dividends * **In your wallet** — the reward asset appears in your token balance directly. * **In your** [**portfolio**](/for-traders/your-portfolio.md) — div.fun aggregates what you hold and what you have received across tokens. * **On the token's** [**page**](/for-traders/the-token-page.md) — the dividend history shows the token's distributions over time. ### If a reward asset is a tokenized stock Stock dividends settle through HyperCore and arrive as the stock's ERC-20 token in your wallet. The path is more involved than a simple transfer — see [How stock dividends work](/stock-dividends/how-stock-dividends-work.md) — but from your side the result is the same: the asset shows up in your balance. Some tokenized stocks may restrict which wallets can receive them; where that applies, it is handled by the protocol's design without blocking distribution to other holders. ### The point Dividends on div.fun are designed to require nothing of you. Buy, hold, get paid. The only decision that matters is which tokens to hold — and that decision is what the [board](/for-traders/the-board.md) and [token page](/for-traders/the-token-page.md) are built to inform. --- # 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://docs.div.fun/for-traders/receiving-dividends.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.