> For the complete documentation index, see [llms.txt](https://docs.aozo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aozo.io/stake/protocol-and-security/liquid-staking-protocol-slp.md).

# Liquid Staking Protocol (SLP)

SLP is Bifrost’s liquid-staking module. It manages liquid-staking flows and vToken issuance on the deployments described below.

For user-facing minting and redemption, see [Staking and vToken guides](/stake/user-guides/staking-and-vtoken-guides.md).

### How SLP works

Bifrost will become AOZO's dedicated liquid-staking sub-brand. The mechanisms below remain Bifrost protocol mechanisms.

1. Users mint a vToken with its underlying asset.
2. Staking rewards increase the conversion rate, not the token balance.
3. Redemptions can settle through order matching when liquidity is available.
4. Other redemptions follow the underlying network's unbonding process.

### Asset reference

| Asset           | Key mechanism                                                      | Redemption note                                                                                   |
| --------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| vETH            | Exchange-rate rewards include staking and MEV rewards.             | Validator exits and Ethereum’s withdrawal queue affect redemption.                                |
| vDOT and vKSM   | The rate reflects staked assets and rewards per vToken allocation. | Ready Pool matching can settle early. Native unbonding is 28 days for DOT and seven days for KSM. |
| vFIL            | Represents staked FIL and rate-based rewards.                      | Uses a FIFO redemption queue and cross-chain account binding.                                     |
| vGLMR and vMOVR | Shared delegation and rate-based rewards.                          | Stated maximum redemption times are 168 hours and 48 hours.                                       |
| vMANTA          | Delegation and rate-based rewards.                                 | Stated maximum redemption time is 168 hours.                                                      |
| vASTR           | Astar dApp staking and rate-based rewards.                         | Stated maximum redemption time is 240 hours.                                                      |

Token-specific deployment data is retained in hidden legacy pages until it is revalidated.

### Token documentation

<table data-view="cards"><thead><tr><th>Asset</th><th data-card-target data-type="content-ref">Reference</th></tr></thead><tbody><tr><td>Ethereum liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/veth.md">vETH</a></td></tr><tr><td>Polkadot liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vdot.md">vDOT</a></td></tr><tr><td>Kusama liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vksm.md">vKSM</a></td></tr><tr><td>Filecoin liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vfil.md">vFIL</a></td></tr><tr><td>Moonbeam and Moonriver liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vglmr-and-vmovr.md">vGLMR &amp; vMOVR</a></td></tr><tr><td>Manta Pacific liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vmanta.md">vMANTA</a></td></tr><tr><td>Astar liquid staking</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/vastr.md">vASTR</a></td></tr></tbody></table>

### Operations

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Reference</th></tr></thead><tbody><tr><td>Validator selection and governance</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/validator-governance.md">Validator Governance</a></td></tr><tr><td>XCM v3 confirmation process</td><td><a href="/stake/protocol-and-security/liquid-staking-protocol-slp/xcm-v3-confirmation.md">XCM v3 confirmation</a></td></tr></tbody></table>

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aozo.io/stake/protocol-and-security/liquid-staking-protocol-slp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.