> For the complete documentation index, see [llms.txt](https://help.wavesfunnynode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.wavesfunnynode.com/documentation/governance/wavesfunny-governance.md).

# WavesFunny Governance

## WavesFunny Governance

**WavesFunny Governance** is an on-chain system that gives WAVES stakers a real voice in the future of the node. We believe that a node’s direction should be shaped by its community, not just its operator

### Governance Contract

All voting and proposals are managed through the **WF-WavesDAO** governance contract: `3PD2g7DBsnrk3idy7xBpTXEcGhPkw95L3x7`

### How It Works

Voting in WFN V2 is fully decentralized and non-custodial. **Your WAVES always stay in your wallet**, and your voting power is directly proportional to the amount of WAVES you have staked (leased) to our node

#### Stake-Weighted Voting

The more you stake, the more impact your vote has on the final decision. This ensures that the most committed community members have the greatest influence over the project’s direction

#### Non-Custodial & Secure

* **No Lock-in:** You can vote without ever sending your funds to a third-party account
* **Control:** Since your WAVES are never "locked" for voting, you can still unlease or move them at any time

{% hint style="warning" %}
**Stake Power Maturity:** To prevent governance manipulation, your voting power (Stake Power) only becomes active after your lease has matured for **1,000 blocks** (approx. 17 hours)
{% endhint %}

### What You Can Vote On

WavesFunny Governance allows you to participate in key decisions, including:

1. **Node Strategies:** Deciding which ecosystem projects to support or invest in (e.g., through WavesFunnyVC)
2. **Reward Payouts:** Voting on changes to reward distribution or new token integrations.
3. **New Features:** Proposing and deciding on new technical implementations (like the "King of the Hill" feature)
4. **Community Initiatives:** Directing node resources toward events, marketing, or community projects

{% hint style="info" %}
**Proposing a Change?** While everyone is encouraged to suggest new ideas, all proposals must first be **discussed with and agreed upon by the WFN team** before they can be officially pushed to the governance contract. Proposals submitted without prior team approval will not be placed on the **WF-Node governance**
{% endhint %}

### Governance Features

#### WavesDAO Integration

We actively participate in **WavesDAO**, and our stakers play a role in how we representing the node's interests in the broader Waves ecosystem. Through our governance, you can influence how the node votes on global Waves proposals

### How to Participate

1. **Stay Staked:** As long as you have an active lease to WavesFunnyNode (`3P98uUFYSP3jRr76kUAeW96Vb2m4LZhrAAf`), you are eligible to vote.
2. **View Proposals:** All decisions and voting results are visible directly on the [Governance UI](https://app.wavesfunnynode.com/governance/WF-WavesDAO) or through the contract data
3. **Cast Your Vote:** Sign an on-chain transaction with the following actions:
   * **WfnWDAOvoteYes:** To support a proposal
   * **WfnRetractWDAOvote:** To cast your maddness

#### WF-WavesDAO Operational Rights

To ensure the stability of our participation in the broader Power.tech - WavesDAO, WFN maintains the right to:

* **WfnFinalWDAOVote:** Force a vote or cancel a proposal if consistency or safety requirements are not met.
* **Emergency Protection:** These actions are only used to ensure that our collective voice doesn't cause harm to the node or its stakers


---

# 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://help.wavesfunnynode.com/documentation/governance/wavesfunny-governance.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.