> 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/core/fira-market-factory.md).

# FiraMarketFactory

FiraMarketFactory deploys FiraMarket instances via split-code CREATE2 and manages fee configuration.

{% hint style="info" %}
**Source:** `src/fira_bonding/core/Market/v3/FiraMarketFactory.sol`
{% endhint %}

## Contract summary

Deploys markets using split-code CREATE2 (because `FiraMarket` exceeds the 24KB EVM contract size limit). Markets are keyed by `BT + scalarRoot + initialAnchor + lnFeeRateRoot` — creating the same combination twice reverts.

## Functionality

### Market creation

The factory validates that the BT comes from the registered `YieldContractFactory` and is not expired, then deploys the market using the split-code pattern (bytecode is split across two storage contracts and concatenated at deploy time).

### Fee management

The factory stores:

* **Treasury address** — Receives reserve fees from swaps
* **Reserve fee percent** — Portion of swap fees sent to treasury
* **Router-specific fee overrides** — Must be strictly less than the market's base fee

`getMarketConfig(market, router)` is called by the market on every `readState` to load treasury, fee overrides, and reserve percent. This means fee changes take effect on the next trade without redeployment.

### Duplicate prevention

Markets are uniquely identified by their BT address and curve parameters. Attempting to create a duplicate reverts.


---

# 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/core/fira-market-factory.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.