> For the complete documentation index, see [llms.txt](https://docs.javsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.javsphere.com/engineering/smart-contracts/leveragex/llptoken.md).

# LLPToken

The LLPToken contract is designed for managing LeverageX LP (LLP) tokens. It integrates upgradeable capabilities and access control mechanisms for minting and burning tokens, essential for leveraged trading systems.

**Key Features**

• Mintable & Burnable Tokens: Dynamically mint and burn LLP tokens as needed.

• Upgradeable Architecture: Built using OpenZeppelin’s proxy upgradeable framework.

• Access Control: Minting permissions restricted to a designated borrowing provider.

**Core Functionalities**

**Initialization**

• The contract initializes the LLP token with the name “LeverageX LP” and symbol “LLP”.

• Ensures upgradeability by following OpenZeppelin’s recommended practices.

**Borrowing Provider**

• Set Borrowing Provider:

Allows the contract owner to assign or update the borrowing provider, the entity authorized to mint LLP tokens.

• Access Control:

Includes a modifier to restrict certain functions to the borrowing provider only.

**Minting Tokens**

• Mint Tokens:

Enables the borrowing provider to mint LLP tokens for a specified account and amount.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.javsphere.com/engineering/smart-contracts/leveragex/llptoken.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.