> For the complete documentation index, see [llms.txt](https://scalex.gitbook.io/scalex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scalex.gitbook.io/scalex/ways-to-profit.md). # Ways to profit There are a great many ways to profit from the ever expanding ecosystem of ScaleX. Some of them are: * Cross-chain arbitrage [Omnichain reflections](/scalex/token/omnichain-reflections.md) * Bots arbitraging between chains = more reflections [Custom reflections formula](/scalex/token/custom-reflections-formula.md) * Attractive rewards at the beginning, with rewards becoming more sustainable as the ecosystem expands * For all buys or sells, you are profiting! The temporary launch fee will drastically minimise the impact of any dumps. * Gain eligibility for the highly anticipated LayerZero airdrop & farm activity on the chains we're launching on, supported by further upcoming airdrops to farm all of them at once! \ We have many ideas for expanding our utility for the times to come. Stick around for that! --- # 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://scalex.gitbook.io/scalex/ways-to-profit.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.