> 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/core-concepts/dividend-distribution.md). # Dividend distribution This is the core of div.fun: how a share of trading volume becomes a dividend in a holder's wallet. The model has one defining property — **holders never claim**. Dividends are pushed. ### From trade to dividend Each trade sets aside the token's configured share of the trade. That accumulates in the token contract as a pending dividend. From there: 1. The pending amount is **converted into the** [**reward asset**](/core-concepts/reward-assets.md) on-chain — by swapping on HyperSwap for HYPE or a stablecoin, or by routing through HyperCore for a [tokenized stock](/stock-dividends/how-stock-dividends-work.md). 2. The reward asset is **split** between holders and the creator, according to the creator-chosen split set at launch. 3. The holders' portion is **distributed in proportion to eligible balance** — a holder with 2% of the eligible supply receives 2% of the holders' portion. ### Push, not claim In a claim model, dividends sit in a contract and each holder must send a transaction to withdraw their share — paying gas, remembering to do it, and leaving unclaimed dust behind. div.fun does not work this way. Instead, div.fun **pushes**. A [keeper](/protocol/the-keeper.md) service continuously distributes the accumulated reward asset to holders by sending it directly to their wallets. A holder does nothing. The reward asset simply appears in their balance. This has consequences worth understanding: * **You pay no gas to receive dividends.** The keeper covers distribution. * **There is nothing to forget.** You do not need to visit the site to collect. * **Distribution is periodic, not per-trade.** The keeper works through holders over time, so dividends arrive in batches rather than on every single trade. Over any meaningful window, your share is proportional to your eligible balance. ### Proportional to eligible balance Your dividend is your share of the **eligible supply**, not the total supply. Certain addresses are excluded from dividends — the liquidity pool, the bonding curve, the protocol contracts, and other non-holder addresses. Excluding them means their share is not wasted; it is redistributed across real holders. See [reward eligibility](/core-concepts/reward-eligibility.md) for the full picture. ### What this means for a holder Hold an eligible balance of an actively traded token, and the reward asset accrues to your wallet on its own. The more the token trades and the larger your share of the eligible supply, the more you receive. You can watch it happen in [your portfolio](/for-traders/your-portfolio.md) and in the token's dividend history. ### What this means for a creator The push model is why a div.fun token feels like a dividend instrument rather than a staking dApp. Your holders do not have to be taught a claim flow or chased to collect. They buy, they hold, they get paid. Your job as a creator is to give the token a reason to be traded. See [after launch](/for-creators/after-launch.md). This is the core of div.fun: how a share of trading volume becomes a dividend in a holder's wallet. The model has one defining property — **holders never claim**. Dividends are pushed. ### From trade to dividend Each trade sets aside the token's configured share of the trade. That accumulates in the token contract as a pending dividend. From there: 1. The pending amount is **converted into the** [**reward asset**](/core-concepts/reward-assets.md) on-chain — by swapping on HyperSwap for HYPE or a stablecoin, or by routing through HyperCore for a [tokenized stock](/stock-dividends/how-stock-dividends-work.md). 2. The reward asset is **split** between holders and the creator, according to the creator-chosen split set at launch. 3. The holders' portion is **distributed in proportion to eligible balance** — a holder with 2% of the eligible supply receives 2% of the holders' portion. ### Push, not claim In a claim model, dividends sit in a contract and each holder must send a transaction to withdraw their share — paying gas, remembering to do it, and leaving unclaimed dust behind. div.fun does not work this way. Instead, div.fun **pushes**. A [keeper](/protocol/the-keeper.md) service continuously distributes the accumulated reward asset to holders by sending it directly to their wallets. A holder does nothing. The reward asset simply appears in their balance. This has consequences worth understanding: * **You pay no gas to receive dividends.** The keeper covers distribution. * **There is nothing to forget.** You do not need to visit the site to collect. * **Distribution is periodic, not per-trade.** The keeper works through holders over time, so dividends arrive in batches rather than on every single trade. Over any meaningful window, your share is proportional to your eligible balance. ### Proportional to eligible balance Your dividend is your share of the **eligible supply**, not the total supply. Certain addresses are excluded from dividends — the liquidity pool, the bonding curve, the protocol contracts, and other non-holder addresses. Excluding them means their share is not wasted; it is redistributed across real holders. See [reward eligibility](/core-concepts/reward-eligibility.md) for the full picture. ### What this means for a holder Hold an eligible balance of an actively traded token, and the reward asset accrues to your wallet on its own. The more the token trades and the larger your share of the eligible supply, the more you receive. You can watch it happen in [your portfolio](/for-traders/your-portfolio.md) and in the token's dividend history. ### What this means for a creator The push model is why a div.fun token feels like a dividend instrument rather than a staking dApp. Your holders do not have to be taught a claim flow or chased to collect. They buy, they hold, they get paid. Your job as a creator is to give the token a reason to be traded. See [after launch](/for-creators/after-launch.md). --- # 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/core-concepts/dividend-distribution.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.