> For the complete documentation index, see [llms.txt](https://docs.ledgity.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ledgity.finance/governance-council/veldy-voting.md).

# veLDY Voting

veLDY is the **governance layer** of the Ledgity protocol.\
When users stake LDY, they receive a **veNFT** representing their **voting power** and **economic participation** in the protocol.

This model ensures that **those who commit long-term** have **stronger influence** over protocol decisions.

***

### **What is veLDY?**

| Property                                   | Explanation                                           |
| ------------------------------------------ | ----------------------------------------------------- |
| **veLDY = Voting Escrow LDY**              | A non-transferable representation of staked LDY       |
| **Issued as a veNFT**                      | Your staking position is stored on-chain as an NFT    |
| **Voting Power scales with lock duration** | Longer lock → more governance weight                  |
| **Accrues buyback yield**                  | veLDY receives distributions from real-yield buybacks |

veLDY cannot be sold or traded — it represents **commitment**, not speculation.

***

### **Voting Power Formula**

Voting weight is determined by:

```
Amount of LDY locked × Lock Duration Multiplier
```

Longer lock = more influence + larger share of buyback rewards.

***

### **What veLDY Holders Vote On**

veLDY stakers govern **all key protocol decisions**, including:

| Category                      | Examples                                             |
| ----------------------------- | ---------------------------------------------------- |
| **Yield Parameters**          | Performance fee rate, liquidity buffer ratio         |
| **Treasury Allocation**       | Incentives, partnerships, liquidity deployments      |
| **Vault Listings**            | Approval of new RWA strategies or network expansions |
| **Burn / Distribution Split** | Decide how buybacked LDY is allocated                |

> **Stakers (veLDY) are the DAO.**\
> The DAO sets direction. The Council executes it.

***

### **Voting Process**

1. **Discussion** starts on governance forum (or community call)
2. A formal proposal is drafted following the Proposal Template
3. Proposal is submitted to **Snapshot**
4. veLDY holders vote off-chain (gasless)
5. If approved, the **Council executes the decision on-chain**

```
Forum → Proposal → Snapshot Vote → Council Execution → On-Chain Result
```

***

### **Economic Alignment**

veLDY ensures that **those who benefit from protocol growth are the same people who guide it.**

| Stakeholder                 | Benefit                                               |
| --------------------------- | ----------------------------------------------------- |
| **Long-term stakers**       | Earn yield from buybacks + shape the protocol         |
| **Short-term participants** | Can still use vaults, but do not influence governance |

This prevents short-term liquidity from influencing long-term strategic decisions.

***

### **In Summary**

| Principle                            | Outcome                                              |
| ------------------------------------ | ---------------------------------------------------- |
| Commitment = Influence               | Governance power reflects long-term alignment        |
| veLDY is non-transferable            | Governance cannot be bought temporarily              |
| Voting controls real economic flows  | Stakers direct how value is captured and distributed |
| Governance is transparent & on-chain | No closed decision-making                            |

> **veLDY makes Ledgity a community-directed protocol — not a company-controlled product.**


---

# 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.ledgity.finance/governance-council/veldy-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.