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

# Governance

## <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" 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 proposal’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, the protocol revenue split, 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="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Protocol direction and strategy\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Governance framework changes\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Asset listings\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Major risk-related discussions\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" 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="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Clearly explain the problem being addressed\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Include supporting research or reasoning\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" 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). During Phase I, the core team publishes each NGV to the Vote Portal.

Time-sensitive questions can also be put to an **Emergency Community Signal Vote (ECSV)**, run outside the standard framework with a shorter window. ECSV-01, which consolidated DUST liquidity into a single pool in July 2026, ran for 24 hours.

### 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, including delegated power</td></tr><tr><td>Initial quorum</td><td>500,000 veDUST, counting every vote cast, Abstain included</td></tr><tr><td>Pass threshold</td><td>More votes For than Against (a tie fails)</td></tr><tr><td>Cost to vote</td><td>Free: a signed message on Monad, no transaction</td></tr></tbody></table>

#### Voting power

When a proposal is published, a **snapshot** of all voting power is taken at that block, shortly before voting opens. Your voting power for that specific proposal remains fixed for the duration of the voting period, even if your veDUST balance changes afterward. veDUST you add after a proposal is published counts from the next proposal.

Voting power is based on your **veDUST balance at the snapshot**, including the effects of lock duration and veDUST decay. It is the sum of the voting power of every veDUST NFT your wallet holds at the snapshot, plus any power delegated to you. If you have delegated your own power to someone else, your voting power for that proposal is zero, because all of it counts for your delegate. 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. Every vote counts toward quorum, including Abstain. If quorum isn’t reached, the proposal is rejected for insufficient participation. If quorum is reached, a For/Against/Abstain proposal passes only when For votes strictly exceed Against votes; Abstain does not count toward the majority, and a tie fails. On a proposal with several options, the option with the most votes wins.

{% 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.

<img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Delegation is a free signed message, made from the Vote Portal. No transaction or gas is needed.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">You delegate all of your voting power to one address at a time. A new delegation replaces the previous one.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">You can set an optional expiry date. Without one, the delegation lasts until you change it.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">To revoke, delegate back to yourself.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">A delegation counts for a proposal if it was made before the proposal’s snapshot and has not expired by then. While it is active, your power counts for your delegate, not for you.

### 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="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">How to Participate

#### Vote on a proposal

1. Lock DUST for veDUST (if you haven’t already)
2. Open the [<mark style="color:$primary;">Governance page</mark>](https://app.neverland.money/governance) in the Neverland app, or visit the [<mark style="color:$primary;">Vote Portal</mark>](https://vote.neverland.money)
3. Connect your wallet on the Monad network
4. Select an active proposal, choose your option, and sign the vote

Voting is a free signature, not a transaction. You can change your vote while the proposal is open; your latest vote replaces the earlier one.

The Governance page lists open and recent proposals with live results and quorum progress, and shows your voting power for each proposal. For/Against/Abstain and single-choice proposals can be voted on in the app; other proposal types open on the Vote Portal. You can read each proposal in full in the app and ask Nadette, Neverland’s in-app assistant, to summarize it.

Remember: your voting power is locked in at the snapshot taken when the proposal is published.

#### 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="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">[<mark style="color:$primary;">Neverland Governance Forum</mark>](https://governance.neverland.money)\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">[<mark style="color:$primary;">Neverland Governance Guides</mark>](https://governance.neverland.money/t/neverland-governance-guides/26)\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">[<mark style="color:$primary;">Neverland Vote Portal</mark>](https://vote.neverland.money)\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">[<mark style="color:$primary;">Governance page in the Neverland app</mark>](https://app.neverland.money/governance)


---

# 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.neverland.money/governance.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.
