> 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

**Solana-native Merger-as-a-Service infrastructure for campaign-based token consolidation and asset migration.**

***

**Version:** 1.0\
**Date:** 2026-04-26\
**Authors:** Tuncer Timur, Ahmet Akın Aktan\
**Status:** Public draft for community review.

***

## What is REDAX Hub?

REDAX Hub is a Solana program that lets any project run a token migration campaign through a single audited factory, instead of writing a custom contract and paying for a dedicated audit each time.

A project opens a campaign, defines what old tokens it accepts and at what rate, and users convert their old tokens into the new one through one program. The conversion is atomic and the math is precise. The platform charges a small fee on the new token plus a flat campaign creation fee in SOL.

We call the category **Merger-as-a-Service**. REDAX is designed to define a Solana-native Merger-as-a-Service category through a reusable campaign factory.


---

# 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.redaxhub.com/readme.md?ask=<question>&goal=<endgoal>
```

`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.
