> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/info-hub/usdvirtual-token-base-asset-for-ai-agents/virtuals-protocol-governance-with-vevirtual.md).

# Virtuals Protocol Governance with veVIRTUAL

Learn how veVIRTUAL holders govern Virtuals Protocol through onchain proposals, snapshot voting, quorum requirements, and protocol governance decisions.

### Onchain governance for Virtuals Protocol

<figure><img src="https://4242579099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frrll8DWDA3BJwEBqOtxm%2Fuploads%2FBsl2HmYIZ8JQlkKrwygu%2FScreenshot%202025-07-01%20at%209.57.32%E2%80%AFPM.png?alt=media&amp;token=9fea58fb-25e5-4c0d-ae62-b5b3587821ce" alt="Virtuals Protocol onchain governance powered by veVIRTUAL holders"><figcaption><p><strong>veVIRTUAL holders shape protocol decisions through transparent, permissionless onchain governance.</strong></p></figcaption></figure>

veVIRTUAL holders govern Virtuals Protocol. Strategic direction, capital allocation, and protocol upgrades evolve through transparent, permissionless onchain governance.

This governance system guides protocol growth, funding, and risk decisions. veVIRTUAL provides voice, responsibility, and control beyond token staking.

{% hint style="info" %}
Explore current and past proposals at [gov.virtuals.io](https://gov.virtuals.io)
{% endhint %}

### How veVIRTUAL governance works

* **Onchain proposal creation**

  Any wallet holding ≥0.10% of total veVIRTUAL supply can submit a proposal. Once submitted, the proposal enters a 72-hour comment window. During this phase, voting is disabled and all feedback is recorded onchain.
* **Snapshot voting**

  After the comment window closes, a snapshot is taken of all veVIRTUAL balances. This snapshot locks each wallet’s voting power for that specific proposal. Voting then opens for 72 hours, where veVIRTUAL holders can vote “For” or “Against.”
* **Quorum and proposal execution**

  A proposal is valid only if it reaches 25% quorum of the total veVIRTUAL supply. If quorum is met, a simple majority (50% + 1) determines the outcome. Passed proposals become eligible for execution.

### Governance principles

* **Permissionless participation**

  Governance is open to all veVIRTUAL holders. No centralized approval is needed to submit, comment, or vote.
* **Conviction-based voting power**

  Voting power is earned through long-term staking and cannot be rented or delegated. Influence reflects conviction, not capital alone.
* **Structured deliberation**

  All proposals undergo a fixed discussion and voting cycle to ensure transparency, informed decisions, and community alignment.

### Passed Virtuals Protocol governance proposals

**Wave-1 Governance Proposals**

1. **Establishing the Virtuals Foundation**\
   Establishing the Virtuals Foundation to drive ecosystem growth, adoption, and innovation through treasury-backed incubation, partnerships, grants, and talent, advancing Virtuals’ leadership in AI.\
   [Read Proposal](https://gov.virtuals.io/proposal/58238259969716106252633733975150732933829817308503391581801496289223305313092)
2. **Sniper Defense & Yield Fund**\
   Allocated 1% of $VIRTUAL supply to fund anti-sniper operations and generate yield for stakers via defended agent token airdrops.\
   [Read Proposal](https://gov.virtuals.io/proposal/56996763629027767054698714571712096750640983191659498948864059685705038611655)
3. **Performance-Based Grant to Virgen Labs**\
   Introduced milestone-based streaming incentives (up to 6% of supply) for core contributors, aligned to $VIRTUAL performance and market growth.\
   [Read Proposal](https://gov.virtuals.io/proposal/85863080150801247354820503347649561342766624974699481992117779927201501850460)

{% hint style="info" %}
Review, debate, and vote: [gov.virtuals.io](https://gov.virtuals.io)
{% endhint %}


---

# 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://whitepaper.virtuals.io/info-hub/usdvirtual-token-base-asset-for-ai-agents/virtuals-protocol-governance-with-vevirtual.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.