> 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/stock-dividends/supported-stocks-and-limits.md). # Supported stocks and limits Not every tokenized stock is a good reward asset. A stock is usable as a div.fun dividend only if it can be bought on HyperCore and delivered to holders on HyperEVM. This page sets out what makes a stock usable and the limits to keep in mind. ### What makes a stock usable For a stock to work as a reward asset, it must be: * **Tradable on a HyperCore spot market**, quoted in USDC, so the protocol can buy it with the accumulated dividend value. * **Linked to a HyperEVM ERC-20**, so the bought stock can be bridged back and pushed to holders as a normal token. * **Backed by real order-book liquidity**, so orders actually fill at a sensible price. Stocks that exist only as off-chain wrappers, or that have no live HyperCore market, or whose markets are effectively empty, cannot serve as reward assets in practice — even if they convert in theory. ### Liquidity is the real limit The binding constraint is order-book depth. A stock with an active market and real resting liquidity fills dividend orders cleanly. A stock whose market shows little or no volume cannot absorb buy orders without large price impact, so dividends in it would be small, slow, or unreliable. Prefer stocks with genuine, active markets over a long tail of listed-but-dead ones. Because liquidity changes over time, div.fun curates the stocks it offers in the launch wizard toward those with viable markets, rather than exposing every theoretically listed name. The curated set is what you should treat as supported. ### Access restrictions Some tokenized stocks restrict transfers to permitted wallets. div.fun's design handles this at the holder level: a holder who cannot receive a given stock does not block the distribution to other holders. Where this applies, it is managed by the protocol — but it is a property of the stock, not of div.fun, and it is worth knowing before choosing a stock that gates its holders. ### Practical guidance for creators If you are choosing a stock reward asset: 1. **Choose from the curated list** unless you have a specific reason not to. The list reflects which stocks actually have viable HyperCore markets. 2. **Favor liquid, active names.** Liquidity is what determines whether your token can actually pay in that stock. 3. **Understand the cadence.** Stock dividends are [asynchronous and batched](/stock-dividends/how-stock-dividends-work.md). Set holders' expectations accordingly — this is equity exposure, not a per-trade drip. 4. **Remember it is permanent.** Like every reward asset, the stock is fixed at launch. ### For holders If you hold a stock-paying token, your dividends arrive as the stock's ERC-20 in your wallet, on the batched cadence described in [how it works](/stock-dividends/how-stock-dividends-work.md). You hold real, transferable exposure to the underlying. As with any reward asset, the token's [page](/for-traders/the-token-page.md) records what it has actually paid. Not every tokenized stock is a good reward asset. A stock is usable as a div.fun dividend only if it can be bought on HyperCore and delivered to holders on HyperEVM. This page sets out what makes a stock usable and the limits to keep in mind. ### What makes a stock usable For a stock to work as a reward asset, it must be: * **Tradable on a HyperCore spot market**, quoted in USDC, so the protocol can buy it with the accumulated dividend value. * **Linked to a HyperEVM ERC-20**, so the bought stock can be bridged back and pushed to holders as a normal token. * **Backed by real order-book liquidity**, so orders actually fill at a sensible price. Stocks that exist only as off-chain wrappers, or that have no live HyperCore market, or whose markets are effectively empty, cannot serve as reward assets in practice — even if they convert in theory. ### Liquidity is the real limit The binding constraint is order-book depth. A stock with an active market and real resting liquidity fills dividend orders cleanly. A stock whose market shows little or no volume cannot absorb buy orders without large price impact, so dividends in it would be small, slow, or unreliable. Prefer stocks with genuine, active markets over a long tail of listed-but-dead ones. Because liquidity changes over time, div.fun curates the stocks it offers in the launch wizard toward those with viable markets, rather than exposing every theoretically listed name. The curated set is what you should treat as supported. ### Access restrictions Some tokenized stocks restrict transfers to permitted wallets. div.fun's design handles this at the holder level: a holder who cannot receive a given stock does not block the distribution to other holders. Where this applies, it is managed by the protocol — but it is a property of the stock, not of div.fun, and it is worth knowing before choosing a stock that gates its holders. ### Practical guidance for creators If you are choosing a stock reward asset: 1. **Choose from the curated list** unless you have a specific reason not to. The list reflects which stocks actually have viable HyperCore markets. 2. **Favor liquid, active names.** Liquidity is what determines whether your token can actually pay in that stock. 3. **Understand the cadence.** Stock dividends are [asynchronous and batched](/stock-dividends/how-stock-dividends-work.md). Set holders' expectations accordingly — this is equity exposure, not a per-trade drip. 4. **Remember it is permanent.** Like every reward asset, the stock is fixed at launch. ### For holders If you hold a stock-paying token, your dividends arrive as the stock's ERC-20 in your wallet, on the batched cadence described in [how it works](/stock-dividends/how-stock-dividends-work.md). You hold real, transferable exposure to the underlying. As with any reward asset, the token's [page](/for-traders/the-token-page.md) records what it has actually paid. --- # 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/stock-dividends/supported-stocks-and-limits.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.