# Governance

## <img src="/files/gpB1h9o1IkPZkDQCvijn" alt="" data-size="line">Phase I Governance

Neverland Governance is live. veDUST holders can now vote directly on proposals that shape the protocol’s direction, making Neverland the first live governance system in the Monad ecosystem.

This page covers how Phase I governance works: the structure, the proposal process, voting mechanics, and how to participate.

{% hint style="info" icon="sparkle" %}
**New to governance?** Start by acquiring DUST and locking it for veDUST. Voting power is based on your veDUST power at the time a vote’s snapshot is taken, not your liquid DUST balance.
{% endhint %}

### Phase I Philosophy

Phase I is intentionally lightweight. Rather than introducing complex governance machinery from day one, the focus is on building participation habits, establishing clear processes, and decentralizing progressively as the ecosystem matures.

Meaningful decentralization doesn’t happen overnight. Early-stage realities, such as relatively low circulating supply, developing participation, and evolving operational structures, call for a framework that can adapt over time. Phase I is the starting point, not the destination.

### Governance Structure

Phase I separates responsibilities into two areas:

#### Operational governance

Handled by the core team. Covers day-to-day ecosystem coordination, partnerships, protocol operations, product improvements, communications, and ongoing execution. This separation allows Neverland to move efficiently during early growth without governance bottlenecks slowing development.

#### Directional governance

Where the community participates directly. Includes:

<img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Protocol direction and strategy\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Governance framework changes\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Asset listings\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Major risk-related discussions\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Other strategic protocol matters

These decisions move through the formal governance process described below.

#### Emergency authority

The **Sentinel Safe** (Emergency Council) retains limited authority to pause or freeze protocol functionality in response to exploits, oracle failures, security incidents, or other critical risk events. This authority exists strictly to protect users and protocol integrity during emergencies.

### Governance Process

Governance moves through two stages: an open discussion phase (RFC) followed by a formal vote (NGV).

#### Stage 1: **Request For Comment (RFC)**

All proposals begin as an RFC on the [<mark style="color:$primary;">Neverland Governance Forum</mark>](https://governance.neverland.money).

A well-formed RFC should:

<img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Clearly explain the problem being addressed\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Include supporting research or reasoning\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">Propose a realistic solution or implementation path

Anyone can submit an RFC. During Phase I there is no fixed minimum discussion period; proposals mature organically through public discussion while the core team acts as governance facilitator, helping determine when a proposal is complete enough to proceed to a vote. This approach keeps discussions flexible while preventing incomplete proposals from rushing to a vote.

#### Stage 2: **Neverland Governance Vote (NGV)**

Once an RFC is ready, it advances to a formal vote on the [<mark style="color:$primary;">Neverland Vote Portal</mark>](https://vote.neverland.money).

### Voting Rules

<table><thead><tr><th width="271">Parameter</th><th>Phase I value</th></tr></thead><tbody><tr><td>Voting period</td><td>7 days</td></tr><tr><td>Voting power basis</td><td>veDUST at snapshot</td></tr><tr><td>Initial quorum</td><td>500,000 veDUST</td></tr><tr><td>Pass threshold</td><td>Simple majority</td></tr></tbody></table>

#### Voting power

When a vote opens, a **snapshot** of all voting power is taken. Your voting power for that specific proposal remains fixed for the duration of the voting period, even if your veDUST balance changes afterward.

Voting power is based on your **veDUST balance at the snapshot**, including the effects of lock duration and veDUST decay. It is **not** based on liquid DUST balances or the total amount of locked DUST alone.

#### Quorum and outcome

For a vote to be valid, at least **500,000 veDUST** of voting power must participate. If quorum isn’t reached, the proposal is nullified due to insufficient participation. If quorum is reached, the option receiving a simple majority determines the outcome.

{% hint style="info" %}
The 500,000 veDUST quorum is a starting threshold. As governance activity and participation patterns become clearer, quorum requirements may be adjusted to better reflect meaningful community participation.
{% endhint %}

#### Delegation

The governance system supports delegation, including **time-limited delegation**. This lets veDUST holders assign their voting power to another participant without permanently transferring it - useful if you want to support a delegate’s judgment on specific topics or during periods when you can’t actively participate.

### Execution

An approved NGV establishes the direction and outcome endorsed by the DAO. From there:

1. The **core team** organizes and carries out the work required to fulfill the proposal, including planning, coordination, and development.
2. **Onchain execution** and administrative actions are performed asynchronously through the protocol multisig and governance infrastructure via the protocol’s timelock lanes.

This division keeps execution efficient while ensuring the DAO’s approved direction is what drives action.

## <img src="/files/gpB1h9o1IkPZkDQCvijn" alt="" data-size="line">How to Participate

#### Vote on a proposal

1. Lock DUST for veDUST (if you haven’t already)
2. Visit the [<mark style="color:$primary;">Vote Portal</mark>](https://vote.neverland.money)
3. Connect your wallet
4. Select an active proposal and cast your vote

Remember: your voting power is locked in at the snapshot taken when the vote begins.

#### Submit an RFC

1. Sign up on the [<mark style="color:$primary;">Governance Forum</mark>](https://governance.neverland.money)
2. Post your proposal in the RFC category with a clear problem statement, supporting reasoning, and a proposed path forward
3. Engage with community feedback and iterate
4. Once the proposal is sufficiently mature, it can advance to a formal NGV

#### Delegate your voting power

If you’d prefer not to vote directly, you can delegate your veDUST voting power, including for a fixed period, through the Vote Portal.

## What Comes Next

Phase I establishes the initial framework. It is intentionally an introductory structure - strong enough to build on, flexible enough to evolve.

As participation grows and governance processes mature, future phases will explore expanded decentralization, broader community responsibility, and additional governance mechanisms. These will be developed collaboratively with the DAO.

This is only the beginning. Welcome to Neverland Governance.

## Resources

<img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">[<mark style="color:$primary;">Neverland Governance Forum</mark>](https://governance.neverland.money)\ <img src="/files/oN7tnEG1WV2vQKVKi7YG" alt="" data-size="line">[<mark style="color:$primary;">Neverland Vote Portal</mark>](https://vote.neverland.money)


---

# Agent Instructions: 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:

```
GET https://docs.neverland.money/governance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.