> For the complete documentation index, see [llms.txt](https://docs.hivesql.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivesql.io/technical-informations/operations/txdelegatevestingshares.md).

# TxDelegateVestingShares

#### Blockchain operations

* delegate\_vesting\_shares

#### Columns

| Name            | Description                                         |
| --------------- | --------------------------------------------------- |
| delegator       | the account that delegates its Hive Power           |
| delegatee       | the account that receives the Hive Power delegation |
| vesting\_shares | amount of Hive Power delegated in VESTS             |

#### Description

The table contains all vesting shares (Hive Power) delegation operations from one account to another. The vesting shares are still owned by the original account, but content voting rights and resource credit are transferred to the receiving account.&#x20;

Multiple operations involving the same accounts can be used to increase or decrease the amount of VESTS delegated.&#x20;

If the amount is set to 0 then the delegation is removed. When a delegation is removed, the VESTS are placed in limbo for 7 days to prevent using them and voting on the same content twice.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hivesql.io/technical-informations/operations/txdelegatevestingshares.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
