Work in Progress
Nothing in this post is final. Governance design and framework components are all subject to change. Parameters will be tuned, mechanisms will be revised, and entire sections may be rewritten. Expect iteration. Expect breaking changes during the early testing. Expect this page to look different from day to day.
Introduction
Neverland Governance exists to steward the long-term sustainability, security, and progressive decentralization of the protocol.
As a lending protocol operating within a rapidly evolving ecosystem, governance must balance decentralization, operational efficiency, security, and responsible risk management. Governance is therefore designed as a phased system that evolves alongside protocol maturity, circulating supply distribution, governance participation, and ecosystem growth.
Neverland Governance is built around transparency, structured public discussion, and progressive decentralization rather than immediate fully autonomous execution.
Governance Structure
Neverland Governance operates through a structured proposal lifecycle designed to encourage discussion, review, iteration, and informed decision making.
The governance process currently consists of three primary stages:
1. Discussion
The Discussion stage is intended for early governance conversations, exploratory ideas, feedback gathering, and community sentiment.
Discussions are informal and are not considered governance proposals.
Topics may include:
-
New protocol ideas
-
Reserve onboarding discussions
-
Incentive discussions
-
Governance improvements
-
Technical proposals
-
Risk discussions
2. Request for Comment (NRFC)
The RFC stage is intended for structured governance proposals seeking formal community review and feedback.
RFCs should contain sufficient detail for meaningful evaluation by governance participants and the team.
An RFC should generally include:
-
Summary
-
Motivation
-
Technical specification
-
Economic impact
-
Risk considerations
-
Implementation approach
-
Timeline considerations
RFCs may evolve during public discussion prior to advancing to Governance Vote.
All RFCs are expected to follow the official RFC proposal template published within the governance forum.
3. Governance Vote (NGV)
Governance Vote represents the final governance approval stage.
Proposals that successfully pass governance vote become approved governance decisions subject to execution by the team, constitutional safeguards, and protocol security review.
Governance votes are considered binding governance decisions during Phase I, subject only to constitutional safeguards, protocol security requirements, and temporary veto protections.
During Phase I governance, a successful proposal does not directly execute protocol changes onchain.
All Governance Vote proposals are expected to follow the official Governance Vote template published within the governance forum.
Phase I Governance
Neverland is currently operating under Phase I Governance.
Phase I governance exists because circulating supply remains limited and governance participation is still developing. At this stage, fully autonomous governance execution would introduce unnecessary governance capture risk and operational instability.
The purpose of Phase I is to:
-
Establish governance culture
-
Build governance participation
-
Expand token distribution
-
Preserve protocol security
-
Protect users and protocol solvency
-
Gradually decentralize governance authority over time
Neverland Governance is expected to evolve through multiple constitutional phases tied to protocol maturity and circulating supply distribution.
-
Phase I: Bootstrap Governance (<50% circulating supply)
-
Phase II: Transitional Governance (>50% circulating supply)
-
Phase III: Mature Governance (>80% circulating supply)
Governance evolution will occur progressively through future constitutional amendments as circulating supply distribution and governance participation mature.
Team Authority
During Phase I, the team remains responsible for:
-
Protocol operations
-
Reserve configuration management
-
Borrow and supply cap adjustments
-
Oracle operations
-
Infrastructure maintenance
-
Security operations
-
Emergency response coordination
-
Execution of approved governance decisions
The team is responsible for implementing approved governance decisions in accordance with protocol security requirements and operational constraints.
The team does not possess authority to arbitrarily seize user funds, bypass constitutional safeguards, or ignore approved governance decisions outside explicitly defined security and emergency scenarios.
Governance Veto Powers
During Phase I, the team retains limited veto authority.
Veto powers exist exclusively to protect:
-
Protocol solvency
-
User funds
-
Governance integrity
-
Protocol security
-
Operational continuity
Veto authority may be exercised in situations including:
-
Governance attacks
-
Malicious proposals
-
Critical security risks
-
Insolvency risks
-
Technically dangerous or unimplementable proposals
The existence of veto authority is a temporary constitutional safeguard designed to protect the protocol while circulating supply remains limited and governance participation matures.
Progressive Decentralization
Neverland Governance is designed to evolve through multiple governance phases over time.
Future constitutional amendments are expected as:
-
Circulating supply increases
-
Governance participation broadens
-
Governance infrastructure matures
-
Ecosystem conditions evolve
Future governance phases may introduce:
-
Expanded governance execution authority
-
Reduced team safeguards
-
Delegate systems
-
Additional governance tooling
-
Greater governance autonomy
Governance Transparency
Governance discussions, RFCs, governance votes, and governance-related decisions are intended to occur publicly through the governance forum whenever possible.
Transparency is considered a core governance principle of Neverland.
Closing Statement
Neverland Governance is designed to prioritize long-term protocol sustainability, security, transparency, and responsible decentralization.
The governance framework will continue evolving alongside the protocol and its community through future governance participation and constitutional amendments.