> 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-misc.md).

# ActionMisc

ActionMiscV3 handles FW and BT+CT minting/redemption, position exits, multicall batching, and transaction simulation.

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

## Functions

### BT+CT lifecycle

* **`mintBcFromToken` / `mintBcFromFw`** — Convert tokens or FW into equal BT + CT
* **`redeemBcToToken` / `redeemBcToFw`** — Recombine BT + CT back to tokens or FW

### Position exits

* **`exitPreExpToToken` / `exitPreExpToFw`** — Exit all positions (LP + BT + CT) pre-expiry. First matches BT with CT for direct redemption (cheapest path), then swaps any remaining unmatched tokens via the AMM.
* **`exitPostExpToToken` / `exitPostExpToFw`** — Post-expiry exit. Burns LP, sends BT to CT contract, redeems via `CT.redeemBC()`. CT is not burned post-expiry.

### Utility

* **`multicall`** — Batches multiple router calls via `delegatecall` to self. Each sub-call can be marked `allowFailure`.
* **`simulate`** — Executes a call and reverts with the result bytes. Used by off-chain code to preview transaction outcomes without sending a real transaction.

### Rewards

* **`redeemDueInterestAndRewardsV2`** — Collects interest from CT + rewards from FW + rewards from markets, optionally swapping reward tokens via an aggregator.


---

# 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-misc.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.