> For the complete documentation index, see [llms.txt](https://docs.volufy.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.volufy.io/misc/volume-projection.md). # Volume projection All chains use the **same configuration and rule set**. ### **Projected Volume** The projected trading volume is estimated based on the package size you select, the live USD price of the underlying asset (SOL, ETH, BNB), and trading parameters such as pool fees and margin settings. Market conditions like slippage, gas fees, and liquidity depth are also factored in. ### **Transaction Count (n)** The number of transactions, n, is derived from an internal rule that ties your package size to the transaction distribution logic. The bot then computes the projected volume dynamically, taking into account: * Package size in native units (SOL, ETH, BNB) * Pool/DEX fee rates * Minimum swap thresholds * Slippage protections * Liquidity availability * Txn count, n This ensures each boost generates a natural pattern of buys and sells. The computed projected volume is always shown to the user in the order summary before payment. --- # 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.volufy.io/misc/volume-projection.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.