Treasury Management

Outlines how the DAO manages its treasuries, including structure, oversight, approval processes, and fund types. Covers tools like Realms and Squads used for tracking and control.

How the DAO Manages Its Funds

• We use Realms to track treasuries and support transparent, on-chain governance.

• Funds like the Operations Fund or Reserve Fund are held in Squads.

• All spending requests must include a budget.

• Reimbursements require receipts or proof of payment.

• DAO-sponsored Clubs, Projects, and Working Groups that receive funding will manage their own assets through a multi-sig on Squads.

• The Core Team reserves the right to have at least one member on each Squad to maintain oversight and coordination.

Treasury Structure

Approval Requirements & Oversight

• Treasuries and funds must maintain a minimum 60% approval threshold to move any assets.

• This applies to all treasuries and funds, including:

  • Main Treasury

  • Community Treasury

  • Operations Fund

  • Reserve Fund

• The Core Team holds proposal and voting power.

• The community has veto power (66% threshold) over both the Main Treasury and Community Treasury to prevent misuse.

Main Treasury

• Purpose: Central holding for all incoming funds and high-level DAO expenses.

• Use: Primarily supports core DAO projects, Core Team funding, strategic partnerships, and long-term initiatives. It also provides funding to other DAO treasuries, such as the Community Treasury. It is not used for individual contributor payments. Those are handled through other designated funds.

• Inflows: External revenue, including but not limited to protocol earnings, referrals, royalties, NFT sales, grants, and partnerships. These types of revenue typically enter the Main Treasury first.

Community Treasury

• Purpose: Supports proposals submitted to the Core Team by members, then vetted and voted on, with clear plans and optional repayment terms.

• Use: Ideal for funding events, community tools, or projects.

• Assets moved to the Community Treasury are allocated specifically for community use. Even if unused, they remain in the treasury and are reserved for future community proposals.

Operations Fund

• Purpose: Covers subscriptions, platform costs, contributor stipends, marketing and ongoing DAO operations.

• Source of Assets: Normally comes from approved budgets via or Revenue Staging or the Main Treasury

• Management: Handled by the Core Team.

• May be divided into sub-accounts to separate assets by team.

• Revenue Staging sub-account:

  • Reserved for budget planning

  • No expenses allowed from this wallet, other than validator operation fees

  • Receives inflows from validator revenue and Core Team projects

  • Used to maximize yield (e.g. vSOL strategies)

Reserve Fund

• Purpose: Used for emergencies, long-term stability, or when the Operations Fund runs out before the next budget.

• Set up as a sub-account within the Operations Fund.