Abstract

This RPIP provides a split for incoming funds, describes what will be done with existing funds, describes how spending will be tracked and describes how current reserves and future income may be reapportioned by the pDAO.

Motivation

Now that snapshot voting is available to allow “the RP community” to express their will, it is important to use that will to direct the pDAO’s funds as we see fit. These funds can be used for many purposes, which can change over time, so this RPIP will be a Living document that can reflect changes to how the funds should be directed.

Specification

• Incoming funds SHALL be tracked and apportioned per category with the following split:
  • Incentives (e.g., LP bonuses) - 50%
  • Grants and Bounties - 20.5%
  • Reserve Treasury - 29.5%
• Where a matching Management Committee exists (eg, the “Incentives Management Committee” for the “Incentives” category), incoming funds SHALL be disbursed to the matching Management Committee as quickly as practical.
  • When possible, automation SHOULD be used to facilitate and expedite disbursements.
• Where no matching Management Committee exists, funds SHALL stay in the same category indefinitely.
  • Upon creation of a matching Management Committee, these funds SHALL be disbursed to the newly created Management Committee as quickly as practical.
  • Funds SHALL NOT be spent from an accounting category directly.
  • Funds MAY be clawed back from an accounting category to the Reserve Treasury by vote.
• The pDAO MAY vote to change the split and/or to move existing funds; this includes retrieving funds from an Management Committee, or sending funds to an Management Committee.
• MCs MAY accept funds from sources other than the pDAO.
  • If explicitly requested by the source providing the funds, these funds SHALL NOT be removed by the pDAO. In such a case, the Management Committee’s Treasurer SHALL track those funds separately from pDAO-sourced funds to enable this.
  • If not explicitly stated, the pDAO MAY move these funds. In such a case, the Management Committee’s treasurer MAY track these funds together with pDAO-sources funds.
• There SHALL NOT be a “Reserve Treasury Management Committee”.
  • Funds MAY be reallocated by voting on a desired amount and category.
  • Funds MAY be spent directly by voting on a desired expense.
    • The expense SHALL have a description in the rpip-10 assets directory
    • The expense SHALL be recorded below, in the direct expenses section
    • This SHOULD be rare; it is RECOMMENDED that the vast majority of expenses be delegated to MCs.
• There SHALL be a pDAO Treasurer appointed via pDAO vote within 3 months.
  • The pDAO treasurer SHOULD post an update within one week of the end of each rewards period, which details the following for each category: starting funds, income, spend, final funds.
  • The pDAO MAY vote to change the pDAO Treasurer at any time.

Management Committee Governance

The following apply to all Management Committees, except where their charter explicitly deviates from this Management Committee Governance section.

• Management Committee members SHALL structure transactions and execute them from a multisig.
  • The multisig MUST allow for successfully signing with at least 2 members missing. The Management Committee MAY allow for more missing members when signing.
  • The multisig SHALL require at least a majority in order to sign. The Management Committee MAY require a larger majority for signatures.
  • The above means 3 of 5 is the absolute minimum requirement possible for a multisig.
  • Existing Management Committee members MAY vote to remove a member with a 2/3 or greater supermajority.
    • Note that this cannot be done if it would violate the above multisig requirements.
  • The Management Committee SHALL have one or more stated goals; where possible, they SHOULD be measurable enough for the community to judge how well the goals are being met.
• Management Committee members MAY appoint one backup signer from the core dev team, by a majority vote.
  • A backup signer, if any, SHALL NOT vote, unless publicly asked to do so by two or more Management Committee members.
  • Management Committee members MAY choose to remove a backup signer by majority vote.
  • There SHALL NOT be more than one backup signer on an Management Committee.
• The pDAO MAY vote to change the membership of the Management Committee at any time, via a full selection.

Management Committee Treasurer

• The Management Committee SHALL appoint one of their number as Management Committee treasurer.
  • The Management Committee MAY change the Management Committee treasurer by a simple majority vote.
• The Management Committee Treasurer SHALL publish reports of how funds were used within one week of the end of each rewards period.
  • The report SHALL include: initial funds available, new income received, funds deployed (including locations, amounts, and justifications for each platform), final funds available, and a list of the active Management Committee members.
  • The Management Committee SHALL receive feedback following those reports.
  • The Management Committee SHOULD respond to this feedback and respect the will of the broader pDAO.

Management Committee Selection

This process SHALL be followed when committees are newly formed, as well as when all or part of a committee’s membership is to be replaced (eg, due to term limits or a vote).

• Nominations
  • A nomination thread for the Management Committee SHALL be posted on the forum for at least 5 days.
    • Any member of the community MAY nominate any member (including themselves).
    • Any nominated member MAY ask to be removed from consideration.
    • A final list of nominees (except those that asked to be removed) SHALL be created and posted as a comment in this thread.
    • If this results in insufficient nominees to fill the spots, the Management Committee Selection process fails and must be restarted from the beginning.
• Nominee information sharing
  • Within 3 days of the final list being posted, each nominee SHALL provide the following:
    • An alignment statement explaining why they are motivated to act according to the Management Committee charter.
    • A conflict statement explaining any other entanglements that could be perceived as motivation to act against the Management Committee charter or the protocol. This includes entanglements with other crypto, other LSD providers, etc.
    • An identity statement explaining as much or as little of who they are as they wish to share. This MAY provide verification to the degree the nominee desires.
    • A contribution statement explaining their contributions to RP.
    • If any of the above four statements is not provided, the nominee shall be removed from consideration. If this results in insufficient nominees to fill the spots, the Management Committee Selection process fails and must be restarted from the beginning.
  • The nominee MAY also provide any additional information they deem helpful.
  • An organizer SHALL provide some basic hard metrics for all candidates; this SHOULD include:
    • Account ages of RP-related accounts.
    • Activity metrics for RP-related accounts (this MAY include items like: number of posts, how often their posts are liked, number of git commits, etc).
• Membership selection
  • The information from “Nominee info sharing” SHALL be compiled and made available on a forum post.
  • Once that post is available, a Snapshot “Weighted” vote SHALL be made.
  • Voters MAY split their vote however they wish. If the voter has no specific split they wish to follow, it is RECOMMENDED that they evenly split their weight among their top N candidates, where N is the desired number of members on the committee.
  • If quorum is not met, the Management Committee Selection process fails and MUST be restarted from the beginning.
  • The selected membership SHALL be the nominees with the highest N vote weights, where N is the desired number of selections. In the event of a tie, the pDAO treasurer SHALL randomly select which of those nominees are selected.
• Terms and Vacancies
  • MCs SHALL be fully re-selected between 10-14 months from their last full selection.
    • MCs SHOULD be re-selected approximately yearly.
    • Selection timing MAY consider convenience (holiday timing, conventions, etc).
    • Selection timing MAY consider efficiency (aligning multiple elections).
  • If a vacancy occurs within six months of the previous selection, the next highest vote recipient from the previous election SHALL be offered the seat, with the Management Committee going down the list of vote-receiving nominees until the position is filled.
    • The offered seat SHOULD be accepted or rejected within 1 week; if it is rejected, or there is no response, the Management Committee SHALL continue down the list.
  • If at any time more than half of an Management Committee is composed of non-elected members (ignoring any backup signer), the Management Committee SHALL be fully re-selected as soon as practical.
  • If a vacancy occurs more than six months since the most recent selection, there SHALL be a selection for only the vacant seats. Note that these seats SHALL be subject to the schedule used by the Management Committee for full reselection.
  • Members MAY be re-selected freely; no term limit is specified.

Updating this RPIP

This is a “Living” RPIP, so that it can be kept up to date with changes to the pDAO budget or budget procedures. There SHALL NOT be any merged updates (beyond correcting errata and add non-normative clarifications) unless they are accepted by pDAO vote. The following process SHALL be followed to update this RPIP:

1. An author SHALL make edits as desired and create a pull request; the status in the PR SHALL be “Draft”
2. An RPIP editor SHALL review it. If there are no structural issues, the status shall be changed to “Review”
3. The vote procedure SHALL be followed as if this were an entirely new RPIP. This includes making forum posts, appropriate wait times, quorums, etcetera, as detailed elsewhere.
4. If criteria for a vote are not met, the status SHALL be changed to “No Vote Taken” and the PR SHALL be closed.
5. If there was a vote, then after the vote is concluded:
   1. If the vote passed, the status SHALL be changed to “Living” and the PR SHALL be merged
   2. If the vote failed, the status SHALL be changed to “Vote Failed” and the PR SHALL be closed

Rationale

The main goal is to establish a starting budget and provide for a quick initial state where funds can be allocated and spent.

The major alteration from the original budget discussion is the removal of the Marketing allocation from the pDAO budget. This was suggested as the core team has recently hired a Marketing team member from their funds and the Bankless marketing blitz is likely sufficient coverage for the time being.

The community believes that it’s important to start spending, particularly on liquidity incentives as quickly as possible. The liquidity bucket amounts to 67.5k RPL, or 1,087 ETH at market prices, annually. For a theoretical run of 1 reward period (28 days), this gives ~83.6 ETH or ~140,200 USD to work with. In light of parallel discussions about tokenomics changes, this amount serves as a conservative starting point.

In addition to https://dao.rocketpool.net/t/pdao-liquidity-committee-and-budget-proposal/895, see https://dao.rocketpool.net/t/pdao-budget-definition/644 for more context.

6/1: Adjustments are being made here to support inflation changes per RPIP-25. A significant one allows the pDAO to vote directly for expenses from Reserve Treasury – this is done specifically with Protocol Development Funding in mind. The budget split is being updated to be roughly steady given the initial proposed inflation step.

Historical budget splits

Date	Split
2022-08-09 (ratified 2022-08-24)	Incentives (e.g., LP bonuses) - 50%, Grants and Bounties - 30%, Reserve Treasury - 20%
2023-07-17	Incentives (e.g., LP bonuses) - 27%, Grants and Bounties - 16%, Reserve Treasury - 57%
2023-11-16	Incentives (e.g., LP bonuses) - 50%, Grants and Bounties - 20.5%, Reserve Treasury - 29.5%

pDAO Treasurer History

Current and historic pDAO Treasurers are recorded in RPIP-36.

Direct expenses

Date	Amount	Summary	Link to full description
2023-09-03	3584 RPL	3 months initial dev funding	expense_1
TBD	0-3909 RPL	Additional dev funding with seat reduction	expense_1
2023-11-29	4643.69	Compensate IMC for lower-than-intended split in past periods	expense_2
2023-11-29	2985.22	Compensate GMC for lower-than-intended split in past periods	expense_2
2024-02-15	49420.55 RPL	Protocol development funding (from 2023-10-26 until 2024-10-24 inclusive)	expense_3
2024-10-27	52079.20 RPL	Protocol development funding (from 2024-10-25 until 2025-10-24 inclusive)	expense_4

Copyright

Copyright and related rights waived via CC0.

Citation

jasperthegovghost, Valdorff, "RPIP-10: pDAO Budget Allocation [LIVING]," Rocket Pool Improvement Proposals, no. 10, August 2022. [Online serial]. Available: https://rpips.rocketpool.net/RPIPs/RPIP-10.