> 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/delegation-voting.md).

# Delegation Voting

### **What to post in the Delegation Voting** **Track?**

You can vote to Polkadot referedum by using Bifrost Opengov’s vDOT, which delegated by vDOT holders - check [here](/faq/what-is-vtoken-delegation-voting.md) to learn more. The DVT track allows you to call these vDOT for voting.

### **Guidance for Delegation Voting Proposing**

1. Post the [discussion](https://bifrost.subsquare.io/discussions) in subsquare to clarify the details of your proposing, receive feedbacks from the community.
2. Once you get enough positive comments, you can try to post on chain.

Here are some steps that you might need to know for on chain posting:

#### Note preimage

Edit [this call](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fbifrost-polkadot.ibp.network#/extrinsics/decode/0x320300016d6f646c62662f666d72697216000000000000000000000000000000000000008200090005070000000000e40b54020000000000000000000000), copy the call data (do not submit at this step!)

<figure><img src="https://757947912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJFtVsA5N3spWTWKvFvv0%2Fuploads%2FngyQNR39XExG4NhnBxla%2Fimage.png?alt=media&amp;token=8c8cb5a8-0e3b-4377-936c-fa4cf461e39f" alt=""><figcaption></figcaption></figure>

Paste your call data at preimage: note\_preimage and click submit.

<figure><img src="https://757947912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJFtVsA5N3spWTWKvFvv0%2Fuploads%2FVg4dFWutTDcbQiWybhjF%2Fimage.png?alt=media&amp;token=794e69fb-bd16-4287-a89c-6a73a3816522" alt=""><figcaption></figcaption></figure>

Find your preimage at [here](https://bifrost.subsquare.io/preimages), submit it in [Referedum](https://bifrost.subsquare.io/referenda)

<figure><img src="https://757947912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJFtVsA5N3spWTWKvFvv0%2Fuploads%2FjdJsCfrvtStmEctqV99Z%2Fimage.png?alt=media&amp;token=af7737b3-000b-4c3b-a0b2-59eb31e32332" alt=""><figcaption></figcaption></figure>

<figure><img src="https://757947912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJFtVsA5N3spWTWKvFvv0%2Fuploads%2FaACEADtcZFpAL1n3GVzn%2Fimage.png?alt=media&amp;token=1729cbfc-1de6-45f3-8b90-8f5178b5c605" 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 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/delegation-voting.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.