# AMM Liquidity Pools

{% hint style="info" %}
**Disclaimer:** [here](/relics/introduction/disclaimer.md)
{% endhint %}

Once a relic mints out, depending on its mint terms, the accrued $MBTC will be put into a liquidity pool together with the configured amount of the minted relic. Following you will have a pair like e.g. MBTC/WE•LOVE•RELICS. The AMM pool operates on the same price curve as [Uniswap V2](https://docs.uniswap.org/contracts/v2/concepts/protocol-overview/how-uniswap-works).

The fee of the pool can be controlled by whoever owns the relic inscription. After setting them initially, they can only be decreased and never again increased.

## Swaps

Swap protocol messages typically come with the following options: 

| Parameter       | Description                                                                         |
| --------------- | ----------------------------------------------------------------------------------- |
| Input relic     | Specifies the input relic, defaults to MBTC                                         |
| Output relic    | Specifies the output relic, defaults to MBTC                                        |
| Input amount    | Min/max amount of input tokens                                                      |
| Output amount   | Min/max amount of output tokens                                                     |
| Is exact input? | If false, this is an exact-output swap. If true, this is an exact-input input swap. |

### MEV?

One measure to reduce MEV ([Miner Extractable Value](https://bitcoinmagazine.com/technical/miner-extractable-value-mev-and-programmable-money-the-good-the-bad-and-the-ugly)) is to prevent tokens bought in one block from being sold again in the same block. This means that if a sniper wants to sandwich a purchase of 10 WE•LOVE•RELICS for 1 MBTC with a 10% slippage, they must either assume multi-block risk or hold a substantial amount of WE•LOVE•RELICS. In that case, they would function more as a market maker than as an MEV extractor.


---

# Agent Instructions: 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:

```
GET https://docs.relicsprotocol.com/relics/core-features/amm-liquidity-pools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.