> For the complete documentation index, see [llms.txt](https://brownfi.gitbook.io/brownfi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brownfi.gitbook.io/brownfi-docs/brownfi-v3/architecture-overview/core-v3-pair.md).

# Core V3 Pair

Each pool has an explicit base token (e.g. ETH) and quote token (e.g. USDC). Sell trades (give quote, receive base) use KB and the ask spread; buy trades (give base, receive quote) use KQ and the bid spread. The two directions can behave differently.

* Adding liquidity follows a 50/50 dollar-value rule. BrownFi takes only what keeps the pool balanced, returning any excess to your wallet. LP tokens are issued based on the more conservative of two independent price valuations (Oracle and AMM TWAP), preventing sandwich attacks at deposit time.
* Removing liquidity is purely proportional to your pool share and requires no price feed, exits are always available regardless of oracle status.
* Imbalance hard cap. The gamma parameter (default 90%/10%) acts as a circuit breaker: no swap may push the pool beyond this split. Trades that would cross the limit are partially filled; the remainder is returned.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://brownfi.gitbook.io/brownfi-docs/brownfi-v3/architecture-overview/core-v3-pair.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.