> For the complete documentation index, see [llms.txt](https://docs.bifrost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bifrost.io/for-the-community/governance/opengov-tracks/liquid-staking.md).
# Liquid Staking
## **What to post in the** Liquid Staking **Track?**
The ValidatorElection Track only has the permission to call related functions with validators setting, such as add\_validator or add\_validator\_boostlist and etc. If you are willing to apply for a VBL, you should post in this Track.
Check passed Liquid Staking Track proposals:
* Bifrost Polkadot: [Bifrost Polkadot](https://bifrost.subsquare.io/referenda/tracks/10)
* Bifrost Kusama: [Bifrost Kusama](https://bifrost-kusama.subsquare.io/referenda/tracks/10)
{% hint style="warning" %}
**Notice**: In Polkadot.js, Bifrost Polkadot is a network under Polkadot & Parachains, Bifrost Kusama is a network under Kusama & Parachains. If you are proposing vDOT, then you should post under Bifrost Polkadot; If you are proposing vKSM or BNC, then you should post under Bifrost Kusama.
{% endhint %}
## **Guidance for** Liquid Staking **Proposing**
1. Check this [guidance ](/for-partners/validator-boost-list-vbl.md)for VBL applying.
2. Post the discussion in subsquare to clarify the details of your proposing, receive feedbacks from the community.
3. Check [Liquid Staking Track parameters](/for-the-community/governance/opengov-tracks.md#validatorelection), post the on-chain proposal.\
The functions you might call with (check the example below):\
\- slp: addToValidatorBoostList
Preimage construction
* If you are proposing for DOT VBL on Bifrost Polkadot, the currencyid is `Token2:0`
* If you are proposing for KSM VBL on Bifrost Kusama, the currencyid is `Token:KSM`
Use the preimage to submit Liquid Staking Proposal:
---
# 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.bifrost.io/for-the-community/governance/opengov-tracks/liquid-staking.md?ask=&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.
