🏇Funding

Ensuring a pathway for Core SubDAO to access treasury funds is a key functionality of the Perion DAO. Perion contributors will developing funding mandates, that outline usage and guardrails of funds from the Perion treasury.

Overview

Purpose:

  • Allow CoreSubDAOs to secure funding

  • Allow DAO members a clear view of subcommittee actions

  • Establishes guardrails and reporting requirements

Vote types used:

Funding mandates

Funding mandates submitted via the Core SubDAO funding pathway should be broad to the point of not being restrictive, or requiring bureaucratic processes that would functionally handicap the relevant subcommittee. In-turn mandates should contain sufficient guardrails to ensure funds are not utilised in a manner that is unrestricted and without controls on risk or expenditure.

Mandate templates and examples

Core SubDAO funding pathway

For a Core SubDAO is to be allocated funds from the Perion treasury, a funding mandate should be submitted and apporved. Approving the mandate of a Core SubDAO for treasury funding involves a multi-step process:

1. Creating and refining the mandate:

The funding mandate / proposal is created and submitted to forum.perion.gg.

Timeline and voting details:

  • The proposal development timeline is open ended

  • A commentary window of up to 7 days on the forum allows input from the community, subcommittees and independents

  • An adjustment window of up to 7 days allows the prposer(s) to adjust the mandate

2. First vote: Subcommittee consensus

The Subcommittee consensus vote is significant during Phase 1 of the governance rollout, as detailed in the reference diagram. This vote aims to secure alignment between the subcommittees, the community of PERC holders and independent validator(s).

Timeline and voting details:

  • Once the proposal is complete, the 3-way vote is used to determine whether the proposal passes to the next phase

  • The voting window will be up to 72 hours

3. Voting stage II: Global subcommittee consensus

A final vote whereby each SubDAO subcommittee votes to approve or deny the funding. In order to achieve successful funding each Core SubDAO subcommittee votes internally to approve or deny the proposal, with the proposal passing if >50% of the Core SubDAOs subcommittees independently vote to approve.

Timeline and voting details:

  • The voting window will be 72 hours

  • A GC vote is used to determine whether the proposal passes and secures funding

Further details

Amendment funding pathway

Generally speaking budget allocations for the Support SubDAO will be covered by the initial Core SubDAO funding mandate. Should the Core SubDAO require additional budget beyond the funding mandate, an amendment must be made. This voting pathway for an amendment is identical to the initial funding pathway.

Budgeting for reviews

All subcommittees should sequester a small percentage of their budget, within their funding proposal, for review of mandates requiring cross-Core SubDAO (GC) consensus.

Operating expenses

Throughout the Phase 1 soft launch operational expenses (contributor stipends, tech dependencies, services, subscriptions, travel, etc) are covered by the treasury in order to keep the DAO functional and building towards Phase 2 and decentralisation.

Emergency backstop

The Perion DAO values upholding the best interests of the community. Should a SubDAO within the Perion ecosystem begin to act in a manner that is not beneficial to the community of PERC token holders (for example in the event a SubDAO was found to be egregiously spending funds on items other than stipulated, was hacked, or the victim of a hostile takeover), the founding contributors may choose to act as a backstop, limiting this party's access to funds from the treasury.

Last updated