# Reserve Liquidity

[Contract Git Source](https://github.com/dopex-io/dopex-v2-clamm/blob/c47ed162e778d188e077b6b1874a8b5873e15c1d/src/handlers/UniswapV3SingleTickLiquidityHandlerV2.sol)

Reserve Liquidity from future

*This can be called by the user directly, it uses msg.sender context. Users share would be burned and they will receive the V3 AMM fees upto this point.*

```solidity
function reserveLiquidity(bytes calldata _reserveLiquidityParam) external whenNotPaused returns (uint256);
```

**Parameters**

| Name                     | Type    | Description                                |
| ------------------------ | ------- | ------------------------------------------ |
| `_reserveLiquidityParam` | `bytes` | The data required for reserving liquidity. |

**Returns**

| Type      | Description                  |
| --------- | ---------------------------- |
| `uint256` | The number of shares burned. |

The \``_reserveLiquidityParam`\` parameter has to be constructed the following way:

```solidity
struct BurnPositionParams {
    IUniswapV3Pool pool;
    address hook;
    int24 tickLower;
    int24 tickUpper;
    uint128 shares;
}

bytes memory _reserveLiquidityParam = abi.encode(
    _params.pool,
    _params.hook,
    _params.tickLower,
    _params.tickUpper,
    _params.shares
);

// To decode:
BurnPositionParams memory decodedParams = abi.decode(encodedData, (BurnPositionParams));
```

### **BurnPositionParams Struct**

| Field Name | Type           | Description                      |
| ---------- | -------------- | -------------------------------- |
| pool       | IUniswapV3Pool | The Uniswap V3 pool contract     |
| hook       | address        | The address of the hook contract |
| tickLower  | int24          | The lower tick of the position   |
| tickUpper  | int24          | The upper tick of the position   |
| shares     | uint128        | The amount of shares to burn     |


---

# 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.stryke.xyz/developers/contracts/lp-management/reserve-liquidity.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.