> For the complete documentation index, see [llms.txt](https://docs.tryflox.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryflox.xyz/reference/limits.md). # Known limits Stated plainly, because a risk product that hides its own model risk is a contradiction. ## Depth is measured in the active range Uniswap v3 depth is the closed-form amount absorbable within the pool's currently active tick range. If a 2% move would walk past that range, true depth is larger — so Flox *understates* absorbable size. This is wrong in the safe direction, on purpose: understating depth makes the agent more likely to refuse, not less. ## Off-chain supply is invisible Flox sees supply when it reaches the chain, not before. Tokens sitting in an off-chain treasury or an unbridged balance are counted only once they move. Scheduled unlocks partly close this gap, but only for schedules that have been entered. ## Redemption is inferred from burns Supply contraction is read from transfers to the zero address. An issuer that retires supply through a different mechanism would need a configuration change to be measured correctly. ## Pricing has no oracle cross-check Prices are read from pool state with a static fallback. There is no independent oracle confirmation yet. Chainlink is live on Robinhood Chain and is the obvious next step. ## Unlock data is hand-entered by default Free API coverage for token vesting schedules is poor. By default, unlock schedules are transcribed from public sources into configuration. A published schedule is a constant, so this is accurate — but it is manual. ## This is a hackathon build Flox is deployed and functional on mainnet, but it has not been audited. Treat it as a demonstration of an approach, not as production infrastructure. --- # 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.tryflox.xyz/reference/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.