> For the complete documentation index, see [llms.txt](https://docs.fira.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fira.money/developers/protocol-contracts/router/action-swap-ct.md).

# ActionSwapCT

ActionSwapCTV3 synthesizes CT swaps through the BT/FW AMM using a flash-callback pattern with BT+CT minting/redeeming.

{% hint style="info" %}
**Source:** `src/fira_bonding/router/ActionSwapCTV3.sol`
{% endhint %}

## Overview

CT is not directly traded in the AMM — the pool only has BT and FW. CT swaps are synthesized:

### Buy CT (FW → CT)

Send FW to CT contract → mint BT+CT → sell BT back to market for FW → net output is CT. The callback mechanism handles this atomically: the market sends FW to the router first (flash-loan style), the router mints BT+CT using that FW to repay the BT debt.

### Sell CT (CT → FW)

Buy BT from the market using FW → pair with user's CT → redeem BT+CT for FW → net output is FW minus the BT cost.

## Functions

* **`swapExactTokenForCt`** — User token → FW → CT (via synthesis)
* **`swapExactFwForCt`** — FW → CT
* **`swapExactCtForToken`** — CT → FW → user token
* **`swapExactCtForFw`** — CT → FW

## Callback handling

The flash-style swaps use `ActionCallbackV3` to handle the market's callback. The callback data encodes the action type and parameters, and the callback contract performs the BT+CT minting or redemption needed to settle the flash swap.


---

# 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.fira.money/developers/protocol-contracts/router/action-swap-ct.md?ask=<question>&goal=<user_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.