> For the complete documentation index, see [llms.txt](https://docs.gammaswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gammaswap.com/markets-and-trading/market-making.md).

# Market Making

Market making has certain advantages including fee rebates and lower latency.

Anyone is welcome to market make. The SDK is available here: <https://github.com/gammaswap/v2-exchange-sdk>\
\
We also have open sourced a market making bot that anyone can use to provide liquidity: <https://github.com/gammaswap/v2-tradingbot>\
\
There is no guarantee of profits when market making. Start small and adjust parameters until you find a working strategy.

### Rebates

Makers earn a 30% rebate from taker fees on filled orders for the following markets:

* BTC 5 minute market
* ETH 5 minute market

The fee is rebated as soon as the fill occurs.

### Latency Advantage

There is a taker delay of 100ms on BTC and ETH 5 minute markets which allows makers time to react to incoming orders, creating deeper liquidity.

*The rebate structure and latency advantage may be subject to change in the future depending on factors such as asset type, duration or liquidity.*

### Co-Location

For minimal latency as an automated trader or market maker, you can co-locate in AWS Tokyo with the GammaSwap matching engine.

### Maker Support

If you have technical integration questions, it's recommended to start in the Discord: [discord.gg/gammaswaplabs](https://discord.com/invite/gammaswaplabs)


---

# 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.gammaswap.com/markets-and-trading/market-making.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.
