# Pegged Pair Strategy

## Strategy One (Constant price, non-rebalancing)

### Description

Liquidity ranges are set at various bin positions surrounding `bin 8388608` depending on backtesting results. For more volatile pegged pairs, wider bin ranges will be used. For less-volatile pairs, narrower bin ranges will be used.

Liquidity will only be deployed when the active bin is surrounding or at `bin 8388608`, to maintain vault ranges and minimize the impacts of slippage.

### Applicable Pool Types

Stable-stable asset pairs trading out of parity or pegged pairs trading around a constant price

*Example Pools: WBTC.e-BTC.b*

### Advantages

* Accrued fees will be compounded back into the position regularly on behalf of LPs compounding yield.
* The strategy will enable LPs to capture a large range of profitable swap fees.
* The strategy is non-rebalancing to mitigate the impacts of IL.

### Risks

* During times of high volatility in the markets, the allocation of assets could vary quite significantly from 50/50.
* Compounding and deposits during highly volatile times will not be deposited until either`bin 8388608` or surrounding bins are reached, which may lead to temporarily lower APRs.
* The liquidity book requires deposited reserves to meet a bin's composition. As such, amounts deposited when the active bin is outside of `bin 8388608` may result in some slippage.

## Strategy Two (Proportional price, rebalancing)

Coming Soon!

### Description

Coming soon!

### Applicable Pool Types

Related asset pairs which do not trade at a constant value, but trade in close sequence

*Example Pools: sAVAX-AVAX*


---

# 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://whitepaper-old.steakhut.finance/getting-started/liquidity/passive-strategies/pegged-pair-strategy.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.
