> For the complete documentation index, see [llms.txt](https://docs.redaxhub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redaxhub.com/readme.md). # Introduction REDAX Hub is campaign-based Solana token migration infrastructure. Current Phase 1 is single-project migration. One project moves holders of its accepted legacy tokens into one fresh output token, under one Campaign. Classic SPL Token only. The accepted tokens, their conversion rates, the output caps and the Campaign's lifecycle are enforced by a Solana program, and every conversion is one holder converting one amount of one explicitly selected token configuration. These pages are the structured explanation of that system: what the on-chain objects are, how a conversion is computed, what the protocol fee does and does not do, where interface behavior differs from program behavior, and what is and is not true today. ## Where the authority lives **Technical authority** — the current public technical specification at . Exact account layouts, field names, instruction account order, program-derived address seeds, error codes, event field schemas and the invariant catalogue live there. Where these pages and the specification differ on a technical detail, the specification wins. **Narrative overview** — the current public litepaper at . ## Current status The public REDAX Devnet interface is available at [app.redaxhub.com](https://app.redaxhub.com/). Its sanitized frontend source is public at [redaxhub/app](https://github.com/redaxhub/app). The interface runs on Solana Devnet. Its public Campaign directory is curated and default-deny; an empty directory is expected until Campaigns are explicitly listed. Current limits: * No mainnet deployment. * No completed audit, and no audit engagement, is established. * No production-readiness claim. Start with [What is REDAX Hub?](/readme/what-is-redax-hub.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.redaxhub.com/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.