> For the complete documentation index, see [llms.txt](https://docs.liquifydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquifydao.com/getting-started/core-features.md).

# Core Features

## 🔁 **Cross-Chain Liquid Restaking**

LiquiFy DAO enables users to stake once and **restake their assets across multiple networks**, boosting yield opportunities. Our liquid restaking model allows users to maintain access to their staked capital, maximizing capital efficiency and composability across DeFi.

## 🌉 **Multi-Chain Support**

The protocol is designed for **interoperability**, allowing staked assets and their derivatives to be bridged and utilized across various ecosystems including Ethereum, BNB Chain, and beyond.

## 🪙 **LRT Minting (Liquid Restaking Token)**

When users deposit into LiquiFy, they receive an LRT (e.g., `liqBNB`) that represents their restaked position. This LRT is fully composable and can be traded, used as collateral, or bridged across supported chains.

## 🛡️ **Secure & Transparent Architecture**

Smart contracts are built with modularity and security in mind, with regular audits and community-led governance ensuring trust and transparency.


---

# 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://docs.liquifydao.com/getting-started/core-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.