> For the complete documentation index, see [llms.txt](https://flokifi.gitbook.io/flokifi-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flokifi.gitbook.io/flokifi-documentation/about-flokifi/what-is-flokifi-locker.md).

# What is FlokiFi Locker?

FlokiFi Locker is the industry’s most innovative crypto locker protocol with key features that include the ability to lock Liquidity Pool (LP) tokens, fungible tokens, NFTs, and multi tokens.

We’re currently the only crypto locker protocol in the industry that allow users to do the following:

* Lock LP tokens for as long as you want to (billions or trillions of years if you so desire).
* Lock multiple assets through a single transaction.
* Lock ERC-1155 multi tokens.
* Batch lock NFTs.

FlokiFi Locker also allows you to securely lock your digital assets on the following 14 blockchains, making it the most versatile crypto locker protocol in the industry:

* Ethereum
* BNBChain 
* opBNB
* Optimism 
* Arbitrum 
* Base
* Avalanche 
* Polygon
* Fantom
* OKX Chain 
* Kucoin Chain 
* Cronos 
* Dogechain 
* Evmos


---

# 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://flokifi.gitbook.io/flokifi-documentation/about-flokifi/what-is-flokifi-locker.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.