GMC Standard Operating Procedures
Reference · Living document

Standard Operating Procedures

How the Grants and Management Committee is formed, staffed, and run — from awards and payments to treasury management and governance votes. Minor edits for clarity may be made by the administrator; substantive changes follow the Decision Making process below.

Committee · GMC Founding authority · RPIP-26 Sections · 16
01

Formation of the Committee

The Grants and Management Committee’s chief mission SHALL be to distribute Grants and Bounties, retrospectively and prospectively, in order to harness the community’s talent to further the goals of the protocol. The GMC consists of nine members appointed by the protocol DAO during a yearly election cycle. The GMC was founded upon the passage of RPIP-15, which is superseded by RPIP-18, and then superseded by RPIP-26.

02

Subcommittees

In order to optimize efficiency and workload, the GMC may utilize subcommittees when application volume or other operational needs make dividing the committee’s workload beneficial. Subcommittees are currently frozen, with all committee members reviewing all applications.

Subcommittee Composition

There are currently no active preset subcommittees. The previous three-subcommittee structure has been suspended due to the reduced number of applications and the committee’s smaller membership.

Rather than establish a new subcommittee structure before it is needed, all committee members will review and participate in decisions on all applications.

The GMC may reinstate subcommittees if application volume, workload, or other circumstances make them useful again. The appropriate composition and structure of those subcommittees will be determined at that time based on the committee’s membership and operational needs.

The administrator retains the ability to recommend the formation of subcommittees or customized review groups when appropriate.

Application Review

While subcommittees are frozen, applications will be assigned to the entire committee for review. All committee members are encouraged to review, provide feedback on, and participate in decisions for each application.

If the volume or nature of applications makes review by the entire committee inefficient, the GMC may determine that subcommittees should be reinstated. At that time, the committee will establish an appropriate structure and application delegation process before dividing applications among subcommittees.

03

Communication Code Of Conduct

When discussing applications, GMC members shall adhere to fundamental communication principles such as ensuring clarity, avoiding misunderstandings, and refraining from making promises that cannot be kept.

Clear Communication and Certainty Transparency

  • Members are expected to communicate clearly and unambiguously, avoiding statements that may be misinterpreted. Members are expected to clearly express their level of certainty on any given matter; if uncertainty exists, members must explicitly acknowledge it.

Majority Opinion Representation

  • When expressing personal opinions on matters discussed within the committee, members must make it explicit that their views are personal and not representative of the committee majority opinion. For instance, consider phrases like, "In my personal view, X appears to be the best way to Y based on our discussions."

Acknowledging Committee Divisions

  • In cases where there is a divergence of opinions within the committee, members should acknowledge the diversity of perspectives. For example, use phrases like, "While I lean towards X when trying to achieve Y, it's important to note that there are varying opinions within the committee."

Formal Clarification Process

  • If a member expresses a personal preference that hasn't been discussed within the committee, encourage formal committee discussions before making decisions. For instance, consider stating, "While I personally prefer X, it hasn't been formally discussed within the committee. I suggest we bring it up for collective consideration to ensure alignment."

Timely Responses

  • If asked a question you are uncertain about, inform the questionnaire that more information will be provided at a specified time and adhere to the communicated timeline.

Decision Privacy

If the GMC has decided on an application, members shall refrain from talking about the outcome before the official announcement. If a grantee or rejected applicant inquires about a decision, the GMC members shall refer to the official decision. If they wish, they can give personal context or commentary about the decision to clarify the thought / decision process for the sake of transparency.

Constructive Criticism

GMC members bear the responsibility to gently correct any inaccuracies or misstatements observed within discussions. Whether through private or public channels, members should actively seek to rectify errors and welcome corrections as part of maintaining the integrity of the committee's communication standards.

Confidentiality of Private GMC Communications

Members will refrain from disseminating content from private communications if such information could be perceived as insensitive or damaging to community relations.

04

Administrator

The expanded GMC Administrator role's responsibilities will include: meeting coordinator, awards facilitator, spokesperson, grants and bounties liaison, treasurer, and governance author.

Hiring Process

Job Posting

  • The GMC will publish an open job posting for a part-time GMC Administrator position with a 1-year term. The posting will include the position's title, responsibilities, qualifications, expected time commitment, and compensation.

  • The job posting will be accessible to the public, allowing interested candidates to submit their applications within a designated 14-day window.

Application Review and Interview

  • The Grants and Management Committee (GMC) will review the received applications once the application window closes.

  • The GMC will conduct interviews with shortlisted candidates to assess their suitability for the role.

    • The interviews may include a combination of virtual or in-person meetings, skill assessments, and reference checks.

Decision-Making

  • After the interviews and evaluations are complete, the GMC will deliberate and make a decision regarding the candidate selection. The decision will be made through a single choice vote, where each member of the GMC selects their preferred candidate from the pool of applicants. The candidate who receives more than 50% of the votes cast by the GMC members will be selected. In the event that nobody meets the threshold (no candidate receives more than 50% of the votes), or if multiple candidates receive an equal number of votes, The GMC has 7 days to engage in further discussions to reevaluate the candidates, review their qualifications, and reconsider their merits.

  • Within 7 days they will hold another single choice vote to choose their preferred candidate (ie, the result of a second round will come within 14 days of the application window closing). This 7 day discussion process repeats itself until a candidate is successfully chosen.

  • The decision will be based on the candidate's qualifications, experience, alignment with the organization's values, and their ability to fulfill the position's responsibilities effectively.

Transition and Renewal of Administrator's Term

To ensure a smooth transition and maintain operational continuity, the committee will assess the administrator's term one month prior to its end. At that point, the committee will have two options:

  • Term Extension: The committee may choose to extend the current administrator's term by one year, provided they have been performing effectively and meeting the organization's expectations. This allows for continuity in their role and provides stability within the position.

  • Hiring Process Initiation: Alternatively, the committee may decide to initiate the hiring process outlined below, seeking potential applicants for the position. This proactive approach ensures a seamless transition if a new candidate is selected.

Contingency Plan for GMC Administrator Removal and Replacement

Consensus Vote for Removal

  • Any committee member can formally request a vote to remove the current GMC administrator by bringing the matter to the attention of the committee.

    • The request will initiate a consensus vote among the committee members, where they will collectively decide on the removal. A majority vote of greater than 50% is required for removal.

Committee Member Replacement

  • If the GMC Administrator role is vacant at any time, the GMC SHALL, within at most 3 days, select a current GMC member to act as interim administrator during the hiring process. This selection is based on a vote, with the highest vote receiver being selected. In the event of a tie, the pDAO treasurer will cast the tie breaking vote. The backup will receive compensation equivalent to the administrator's compensation during the time the backup serves.

  • The backup committee member will ensure the smooth functioning of the administrator's duties until a replacement is hired.

Replacement Hiring Process

  • Upon the initiation of the replacement hiring process, the GMC will promptly begin the recruitment procedure outlined in the standard hiring process mentioned above.

  • The job posting for the administrator position will be updated to indicate the urgency of the situation and the need for an emergency replacement.

Administrator Responsibilities

  • Meeting Coordinator / Scheduler - Ensuring equitable participation and fostering respectful discussions within the committee. Providing timely reminders for deadlines and important action items.

  • Awards Facilitator - Facilitating the rolling awards process. Maintaining accurate records and documentation, including scoring processes and relevant spreadsheets.

  • Spokesperson - Leading discussions and drafting official GMC statements and proposals on the DAO forum. Collaborating with the community to enhance GMC processes and communicating improvements effectively. Reporting to the community regularly on committee member activity.

  • Grants and Bounties Liaison - Effectively communicating with members and the wider community on the cultivation of individual grants, and bounties. Verifying work has been completed before payments are sent.

  • Treasurer - Maintaining treasury sheet, verifying project payment status’, creating a json file for transactions, publishing reports including 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 MC members.

  • Governance Author - Drafting RPIPs and pushing forward governance initiatives.

Compensation And Benefits

Current Compensation

The position offers a monthly payment of $2,625.00 in RPL, paid regularly over a span of 12 months. Compensation is subject to recalculation based on Section 7.3.2 (Large Grants).

Compensation History

  • August 18, 2023 — $3,750/month: Initial compensation established with the passage of RPIP-26.

  • March 17, 2024 — $5,000/month: Compensation increased to $5,000 per month.
    Link To Discussion

  • August 9, 2024 — $5,375/month: Compensation increased to $5,375 per month.
    Link To Discussion

  • August 1, 2025 — $3,500/month: Compensation decreased to $3,500 per month due to the reduced workload.
    Link To Discussion

  • February 2026 — $2,625/month: Compensation decreased to $2,625 per month as part of a global administration cost reduction.
    Link To Announcement

05

New Member Onboarding

There will be a meeting held by the administrator to orient new committee members upon their joining. The meeting is optional for existing or previous members. The administrator will review the standard operating procedures and assign each new member to a subcommittee. New members will be provided access to all internal GMC documents. They will be added to the GMC Google Calendar. The administrator will answer any questions new members have. Maverick, or another Rocket Pool Discord member with the proper permissions will add that member to the GMC role.

06

Temporary Member Replacement

  • The member seeking replacement MUST declare how many GMC rounds they will be missing.

  • The leave of absence MAY be up to, but SHALL NOT exceed 3 GMC rounds, starting from the following round.

  • The leaving member MAY return earlier than originally declared, but they SHALL NOT return to participate in decisions in the middle of an active round. They will be reinstated the following round.

  • A majority vote of 5 out of 8 members is required to honor the request. GMC members SHALL have seven days to approve, deny, or abstain from the request. If the request is unsuccessful, normal replacement procedures outlined in RPIP-10 will take effect.

  • 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. They SHALL be communicated the length of the position.

  • Following the maximum duration of three GMC rounds, the member on leave MAY request an extension for an additional three GMC rounds. - - This extension does not prolong their term beyond the next election.

  • If the departing member does not declare their return IMMEDIATELY (48 hours) after the end of their leave, the replacement member will be permanently instated until the conclusion of the current election year.

  • The committee member who is temporarily stepping down SHALL be replaced on the multisignature wallet by the new member for the duration of the vacancy.

Link To Discussion

07

Meetings

Meeting Types

Retrospective

Retrospective meetings were frequent during the early years of the GMC as the committee worked to establish and improve its processes and protocols. As these processes have matured, retrospectives are now held on an as-needed basis to evaluate current operations, identify areas for improvement, and establish any necessary action items.

Application Discussion

There will be an application discussion meeting held for each subcommittee. The agenda for the meeting will be composed by the administrator in Sesh. Each application will be discussed in rounds and members will signal their current stance, and then inform the administrator of any negotiation questions. The admin will confirm the method of communication and whether it is one-on-one with the admin, private with the subcommittee, public with the applicant, private with other parties, or public with the applicant and other parties. Post meeting, the admin will post a summary of the current sentiment towards each application in the GMC Private channel for all members to see.

Rocket Pool Team

The GMC will meet bi-weekly with members of the Rocket Pool team, typically Langers, to share updates, discuss current and upcoming initiatives, coordinate priorities, and identify opportunities to improve efficiency and collaboration between the GMC and the Rocket Pool team.

Town Hall

Town Halls are public meetings between members of the Rocket Pool protocol DAO and the GMC, held live in the Rocket Pool Discord. The GMC provides updates on current activities and initiatives, discusses relevant committee topics with the community, and concludes by fielding questions and feedback from attendees.

Scheduling

The administrator will use the Doodle application to provide committee members with multiple meeting options for retrospective and awards meetings. The meeting time will be chosen based on the most popular option.

Agenda

An agenda will be prepared and hosted through the interactive agenda tool, Sesh. Sesh will allow each member to have ample time to share their opinions and viewpoints while optimizing the time spent on each topic. The agenda will include topics for discussion, decisions to be made, and any relevant presentations. Members are encouraged to ask the administrator to add items to the agenda ahead of time.

08

Awards Process

The awards process should be followed from RPIP-26 https://github.com/rocket-pool/RPIPs/blob/main/RPIPs/RPIP-26.md which is detailed below.

  • Community members can submit grant, bounty, and retrospective award applications at any time

    • Submissions received before the seventh of the month will be reviewed that month; if received after that, they will be queued for next month.

  • The GMC will meet on or around the second Sunday of the month to make preliminary decisions and provide comments

  • The GMC administrator will contact the submitter and:

    • Share preliminary decision and rationale

    • Work with submitter on edits, if desired

    • Assign individual committee members for verification, if work is specialized

  • The GMC will meet on or around the last Sunday of the month to make final approval/rejection decisions and provide comments

  • Submitters are free to resubmit applications in later months if desired

  • Prior to the first call for applications, the GMC SHALL develop one or more rubrics by which to select winning grants and bounties. The rubric(s) SHALL be publicly posted and anyone so interested in participating SHALL be solicited in their development. The GMC MAY choose to develop separate rubrics for grants, bounties, and retrospective awards.

  • The GMC MAY give retrospective awards for previously-completed work. Such applications MAY be submitted on behalf of others rather than being self-nominated.

  • Anyone MAY file an RPIP disputing a grant, bounty, or retrospective award within two weeks of the announcement of recipients. Such an RPIP SHALL be subject to a snapshot vote.

  • Funds for grants and bounties SHALL only be considered approved upon either the completion of the two-week waiting period without any objecting RPIPs, or the failure of any objecting RPIP snapshot votes.

  • After the approval of BA032305, the GMC will grant a $100 RPL reward for bounty submissions, provided that the awarded bounty amount exceeds 100 RPL. https://discord.com/channels/405159462932971535/1140375701300723876

Assessment of Awards

  • Recipients of Grants SHALL update the GMC in a publicly-available document about their progress on at least a monthly basis.

  • If a majority of the GMC agrees that a grant recipient is failing to provide the specified services to the protocol in a timely manner (as documented in the original application and in subsequent monthly updates), the GMC SHALL publicly announce such a decision and cease any future payments. This decision MAY be disputed by anyone through the creation of an RPIP within two weeks of the GMC's announcement. The RPIP SHALL be subject to a snapshot vote.

  • Any group or individual MAY submit a publicly-available document to the GMC claiming successful completion of the bounty. The GMC SHALL discuss all such applications. If a majority of the GMC agrees then the GMC SHALL announce the award of the bounty. Anyone MAY dispute the awarding of the bounty through the creation of an RPIP within two weeks of the GMC's announcement. The RPIP SHALL be subject to a snapshot vote.

Conflicts of Interest

  • The GMC SHALL abide by the following processes to minimize conflicts of interest:

    • Any GMC member SHALL NOT score, vote on, or participate in GMC discussions about any retrospective award for which they are nominated. They MAY participate in the ratifying snapshot vote.

    • Any GMC member who submits a grant application SHALL abstain from scoring, voting on, or participating in GMC discussions about any grants during the application period for which they are an applicant. They may participate in the ratifying snapshot vote. They may also score, vote, and participate in discussions in future rounds during which their grant is ongoing, provided they have not submitted an application during that round for any new grants.

    • Any GMC member who submits a bounty SHALL not complete that bounty.

Awarded Amounts

  • To optimize efficient decision-making across applications and facilitate consensus, members are requested to indicate their preference for each applicant from the following options:

    • 'Award at 133%'

    • 'Award at 100%'

    • 'Award at 66%'

    • 'Award at 50%'

    • 'Award at 33%'

    • 'Custom Amount'

    • 'Defer with Further Consideration'

    • 'Decline'

    The prevailing choice will be determined by the majority vote, requiring more than half of the total recorded votes. Selections indicating approval are regarded as affirmative votes, while 'Defer' and 'No' choices are deemed negative votes. In instances where a majority 'yes' decision emerges, but it did not receive more than half of the total votes, a ranked vote of the affirmative options is conducted for that application during the final award slate. Each application must receive votes from at least two committee members to pass. If a proposal is deferred due to a lack of consensus or a majority vote within a three-person committee, it will be deliberated on by the entire committee in the following cycle.

Link to Discussion

History

  • November 21, 2024: Added the "Award at 50%" option alongside the "Award at 66%" option.
    Link To Discussion

Defer To PDAO

The GMC has a ‘Defer To pDAO’ decision on the GMC Decision sheet.

Requirements For Invocation

The majority of GMC members have:

1) Expressed interest in the project's goal.

2) Concluded that there is no clear evidence indicating interference with the protocol's current priorities.

3) Identified a specific question they wish to pose to the pDAO before funding can be approved. This inquiry may stem from a variety of factors, such as the contentious nature of the topic, significant grant amounts, proposals perceived as beyond the GMC's scope, or intricacies requiring technical expertise beyond the GMC's current capabilities.

Defer To pDAO Process

  • The GMC Administrator will draft a forum post for the committee's review within 24 hours of the decision.

  • The GMC will have 48 hours to review and provide feedback before the administrator posts it on the DAO forum.

  • The forum post will encompass the application, the GMC's feedback, a sentiment poll, and a request for guidance from the pDAO.

  • After ten days, the administrator will request a 7-day snapshot poll from Langers to approve or deny the application.

Link To Discussion

Decision Award Language

  • To ensure uniformity, members are requested to designate their choice for each applicant from the set of alternatives:

    • Approved - at X amt. (X may be what they requested or a modified number).

    • Deferred - No decision has been reached yet, still in discussion with the author.

    • Declined - because of Y. Submitters are welcome to refine, refactor and resubmit.

Link to Discussion

Final Slate Voting

The GMC will utilize a three-stage voting system during the finalization of an awards cycle. The administrator will present a compilation of the current slate of awards and also ask the GMC to review the award commentary, and make any revisions where necessary.

Stage 1 (24 hours)

Declare Amendments During this stage, GMC members will put forth any amendments they wish to propose regarding the final decisions. These amendments have the potential to alter the decision to any of the options outlined in the feedback sheet. For example, John might propose an amendment to revise RAXXXX funding to 100%, while Jane may revise GAXXXX funding to 66%. Jim, on the other hand, might suggest declining the BAXXXX application.

Stage 2 (48 hours)

Amendment Discussion and Voting In this stage, the proposed amendments from Stage 1 will be compiled. Committee members are then invited to vote 'Yes', 'No', or 'Abstain' on each of the amendments brought forward during Stage 1. For an amendment to pass, it requires a majority vote—meaning more than half of all standing committee members must be in favor of it.

Stage 3 (24 hours)

Vote To Reject Slate During this stage, committee members have a 24-hour window to collectively decide whether to accept or reject the entire slate of proposals. If a majority vote in favor of rejecting the slate is not attained, the slate will automatically be accepted. Following this decision, the 14-day objection window will commence, starting from the awards decision post made by the administrator.

Link To Discussion

09

Bounty Incentives

On May 28, 2024. The GMC passed the following incentives for bounties:

  • Proposal Incentive $50

  • Definition Incentive 2%, minimum $75

  • Support Incentive 2%, minimum $50

Link To Discussion

10

Payments

Payment Creation

On or around the 13th of each month, the administrator will prepare a payment json for any member of the GMC to create a transaction for.

The administrator will post in the GMC’s Discord ‘execute’ channel.

All payments will be listed with the following format:

  • Award Number - Project -recipient (recipient address) - Amount (Any applicable notes)

Example:

  • GA022301 - DeFi Page - opensourceventures.eth - 6.75 - final payment

Payment recipients will be pinged if the administrator has their Discord handle.

The following guide will be used: https://docs.google.com/document/d/1zfL9Gc3OBB2HMUKN5thviqLrq36A4WBfYtgwCMwKMQY/edit?usp=sharing

Payment Addresses

Payment addresses must be submitted in the specified Discord channel (https://discord.com/channels/1109303903767507016/1164602603280289874). The administrator will initiate prompts for awardees to share their addresses within this channel. Should anyone post their address in this channel without the administrator's prompt, verification of their identity will be conducted through cross-referencing by the administrator.

Swap Creation - USDC

Primary Option – OTC:
For each monthly conversion, the GMC will first attempt to execute an over-the-counter (OTC) swap with a designated counterparty.

On or around the 10th of each month at 00:00 UTC, the GMC will trigger the standard /ratio reading to lock the RPL↔︎USDC exchange rate for that month’s swap (“Rate Lock”). Prior to the Rate Lock, the GMC will notify the counterparty of the target notional amount of RPL to be converted to USDC, up to the budgeted monthly requirement, with the exact size determined by the GMC.

Following the Rate Lock and upon GMC request, the counterparty will transfer the agreed USDC amount to the GMC multisignature wallet. After receipt and verification of funds, the GMC will transfer the corresponding RPL amount to the counterparty’s address, calculated using the Rate Lock value from 10th 00:00 UTC. No premium or discount is applied; the locked /ratio is the sole pricing reference.

OTC swaps will only be used when the GMC has sufficient RPL in treasury to fulfill the month’s conversion in full; no IOUs or deferred settlements are permitted. The counterparty may remain pseudonymous to the public, provided appropriate internal verification occurs within the GMC (e.g., address whitelisting and contract address validation). Prior to releasing RPL, the GMC will verify token contract addresses, receipt of USDC, and correctness of amounts.

The GMC will publish a public summary of each month’s swap, including amounts converted and the method used, while preserving counterparty pseudonymity.

Fallback:
If an OTC swap is unavailable or impractical in a given month, the transaction initiator will employ the CowSwap application within the multisignature wallet. They will establish a limit order with a one-month expiry, set at 10% below the current market price. The administrator will furnish the transaction initiator with the specific RPL amount for the swap, and the initiator will confirm that this amount corresponds to the amount of “guaranteed” awarded funds from the most recent award round.

RPL Calculations

  1. Award amounts for grants, bounties, and retrospective awards will be denominated in USD. RPL amounts will not be price locked at the time of award for grants and bounties. The GMC will take into account the requested token on the original application but ultimately has discretion on whether or not to pay with RPL or LUSD at the time of payment. For RPL calculations, the value of RPL will be assessed on the 13th of the month at 0:00 UTC from CoinGecko and rounded to the nearest RPL. Grants awarded prior to Tuesday, May 7, 2024 4:30 PM will not be affected. Link To Discussion

Committee Stipends

Due to a growing workload and an upcoming budget increase, a more efficient system was needed to ensure fair compensation for members' contributions. On February 12 In the GMC voted against using RocketScrape and to use the following metrics for member compensation:

  • Message Count (25%)

  • Decisions Submitted (50%)

  • Meeting Attendance (15%)

  • Signed Transactions (10%)

The first payment for which this took effect was March 2025.

11

Treasury - Stablecoin

Starting in Round 26, the amount to be swapped from RPL to USDC will be determined at the time each award is approved. For grants without a fixed amount — such as those with ranges or performance-based incentives — the minimum guaranteed amount will be used.

The actual swap will occur at the time of regular monthly payments.

Key Points:

  • Applies to all awards that pay out (all or a portion of) the award after the acceptance round.

  • For fixed-amount grants:

    • Any portion being paid during the upcoming payment cycle will remain in RPL.

    • The remaining amount will be swapped to USDC during the same payment cycle.

  • For grants with ranges or incentive components, only the minimum guaranteed amount will be swapped.

  • Grants that had funds swapped to USDC will be paid in USDC.

  • If the final payout exceeds the minimum, the difference will be paid in RPL.

  • Swaps are scheduled alongside regular payments, not executed immediately at award approval.

  • Ensures that stablecoins are directly tied to actual disbursements, avoiding idle reserves.

  • Avoids past strategies where stablecoins were not clearly earmarked or effective.

Considerations:

Introduces some short-term RPL sell pressure, but in targeted, controlled amounts.

More transparent and operationally simple than gradual stable reserve buildup.

May reduce long-term treasury flexibility due to reactive rather than proactive swaps.

Link To Vote

The GMC switched from BOLD to USDC due to grantee requests after voting on August 11, 2026.

12

Decision Making

The GMC will follow a structured process for decision-making during critical decision points. The standard process for decision making is as follows:

  • The administrator will create a private GMC thread that explains the topic and has a sentiment poll.

  • After seven days, an official GMC vote will be created. The decision will be made through a single choice vote, where each member of the GMC selects ‘Yes’, ‘No’ or ‘Abstain. The decision that receives the majority of the votes cast by the GMC members will be recorded within the Standard Operating Procedures document, and the Member Contribution Sheet. In the event that no choice meets the threshold (no choice receives the majority of the votes), or if multiple choices receive an equal number of votes, The GMC has 7 days to engage in further discussions to reevaluate the choices, review the discussion, and reconsider their vote. Within 7 days they will hold another single choice vote. If after another seven day process, the results are the same, the administrator will be given the tie-breaking vote.

13

Documentation

Standard Operating Procedures

This document outlines the processes of the GMC. Minor, non-substantive revisions for clarity can be made by the administrator. Any GMC member can challenge the document's operations. Revisions with substantial impact undergo the Decision Making process detailed above.

Member Contribution Sheet

The administrator will maintain a GMC Member Contribution Sheet that will be made available to the public. The sheet is used to track member participation and calculate contributions based on defined activity categories.

Current Contribution Weighting

Member contributions are calculated using the following weights:

  • Message Count — 25%

  • Decisions Submitted — 50%

  • Meeting Attendance — 15%

  • Signed Transactions — 10%

Periods With No Decisions

The GMC subsequently voted on how the Decisions Submitted category should be handled during periods in which there are no decisions available for members to submit.

The GMC voted to maintain the full payout and award full credit for the Decisions Submitted category during these periods.

When there are no decisions:

  • Total GMC payout remains at 100%.

  • All members receive 100% credit for the Decisions Submitted category.

  • The existing category weights remain unchanged.

The decision was approved by a vote of 5–2, with five members supporting full payout and full Decisions credit and two supporting a 50% reduction in payout with the remaining categories pro-rated.

The rationale for the decision was that reducing compensation during periods without decisions could introduce unnecessary risk to committee stability and retention. Maintaining consistent compensation was preferred over introducing additional variability or complexity.

Historical Activity Tracking

Prior to the current contribution-weighting system, the administrator maintained a GMC Member Activity Sheet designed to publicly track several measures of member participation. The sheet contained the following tabs:

  • Meeting Attendance — Meetings that were not given at least 72 hours' notice were not recorded. Weekly meetings were recorded whether or not notice was provided.

  • Transactions — All completed transactions were recorded.

  • Channel Activity — Members' total post counts in #governance and #gmc-discussions were recorded monthly.

  • Forum Statistics — Recent read time and read time on the DAO forum were recorded.

  • Awards Cycles — Members were marked as either “Scored,” “Unable to Score,” or “Not Scored.”

    • Scored — The committee member submitted their feedback and scoring on time, and the administrator provided seven (7) days' notice of the deadline within the private GMC channel.

    • Unable to Score — The committee member was not part of the GMC roster during that award cycle, or the administrator did not provide seven (7) days' notice of the deadline.

  • Voting Decisions — Members' “Yes,” “No,” and “Abstain” votes on decisions were recorded.

This system was later overhauled and replaced by the current weighted Member Contribution Sheet described above.

Link To Discussion

Link To Member Contribution Sheet

Calendar

The administrator will assume responsibility for managing a comprehensive Google Calendar encompassing critical deadlines, essential meetings, and other significant events.

Awards Ledger

The administrator oversaw RPIP-29, however it was sunset because it was time intensive, had little to no usage, and was difficult to get reviewed.

Link To Discussion

14

Community Reporting

  • The GMC Member Contribution Sheet will be updated monthly and accessible to the community.

  • Near the end of each month, the administrator will post a treasury update to the protocol DAO forum which will include the GMC’s budget, inflows, and outflows.

  • The Standard Operating Procedures document will be made available to the protocol DAO at all times.

15

Review

  • In order to open a qualitative line of feedback from the GMC to the DAO, when applicable the administrator will post a review and recap of the committee to the DAO forum. The recap will include new processes the GMC has developed recently and any other important information. The GMC will gauge sentiment on the direction of the committee. There will be votes on:

    • Level of risk the GMC should be taking.

    • Areas / domains of focus the GMC should be funding with priority.

16

Continual Improvement

Based on feedback and outcomes, committee members are encouraged to follow the Decision Making process outlined in this document to make continual improvements to the process.

No matching sections. Try a different search term.