# Position Characteristics

Click on each one to learn more

## Collateral Token

An ERC20 that the user is providing.

## User Amount

The amount of collateral tokens that the user is providing

## Provided Token

An ERC20 token that the user is borrowing to form their position.

## Goal Leverage

A leverage amount. Anywhere from 1x to 10x. The max leverage depends upon the liquidation fee of a position. When the leverage is below 2x, then the user tokens are used to compensate for the provided side(may change depending on bounds).

## Lower and Upper Tick Bounds

These are the bounds for the position. They are set in ticks and they do not have to be proportional on each side.

## Take Profit Point

This is the amount of profit that the position needs until it will be closed. The profit is calculated by essentially closing the position and comparing how much more collateral token the position contains. If the threshold is passed then its closed by a relayer.

## Stop Loss Point

This is the amount in losses that the position needs until it will be closed. The loss is calculated by essentially closing the position and comparing how much less collateral token the position contains. If the threshold is passed then its closed by a relayer.

## Lower Exit

This is a tick level, where if the position crosses **below** the level it will be closed.

## Upper Exit

This is a tick level, where if the position crosses **above** the level it will be closed

## List of Accepted Routes

These are all of the routes that are accepted for the liquidation of the position. The routes must be a subset of the lender's choices of routes. 


---

# 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://sandcastle.gitbook.io/sand-castle-finance/uniswap-v3-leverage/position-characteristics.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.