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

# LAVA Protocol's Features

Our cross-chain bridge offers an efficient and secure liquidity solution for BRC20 assets, facilitating the circulation across different blockchain networks. This innovative feature allows assets like BTC to be seamlessly transferred to EVM-compatible chains, enabling users to conduct cross-chain transactions, transfers, and to create & participate in liquidity pools. Additionally, the bridge integrates LAVA Protocol's own Launchpad, supporting project storage and cross-chain operations, thereby broadening its application scenarios.

LAVA Protocol aims to develop a more decentralized cross-chain bridge, enhancing transaction speed, security, and user satisfaction through ongoing tech improvements. Our goal is to simplify operations and provide stable support for BRC20 and other tokens' circulation and trading, strengthening the blockchain ecosystem's connectivity.

<figure><img src="/files/dYYEax9rcIGmy8V2FllJ" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://lava-protocol.gitbook.io/lava-protocols-guidebook/features/lava-protocols-features.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.