Feddas - Gov Ops Council Beta

Introduction Part of the YAM Re-Org that we have been working on in the last few months includes the creation of a new advisory group of contributors who are empowered to help run and streamline the operations and governance of the DAO. This group would have a limited scope of powers intended to make it easier for token holders and grant applicants to perform their required tasks to make the new system run smoothly.

I have put together a full write-up on the scope and responsibilities of this new group, from here on called the Gov-Ops Council, in this document: https://github.com/yam-finance/documents/blob/master/govops/govops-council.md 2

Building on this document, I am proposing that the DAO implement an initial beta version of this council to start performing these tasks and working out the kinks and what scope may or may not need to be added. I want to be clear that this would be a temporary measure while the complete specification for the group is worked out. Implementing the grants model with the current contributors while we continue to work it out has been very helpful in understanding where the pain-points are for the process, and I expect similar benefits from this working implementation.

Beta Implementation The proposed beta implementation would begin with 3 members: @Ross, @Feddas, and @ethe . They will be responsible for the scope of work laid out in the linked document above (under scope of work). Since we do not have the full nomination and voting model worked out, I propose the following addendum to that document:

Each of the above members will present the scope of work that they intend to fulfill within the Gov-Ops council and the expected amount of time they expect to spend on that work, with a not-to-exceed amount. Initial term to be 2 months (to align with the quarterly periods) and each member will get a separate snapshot vote to ratify their membership.

during the beta test, @desiger and @ross will collect feedback on the process and use this information to craft the Gov-Ops Service Agreement, which will enshrine the roles and responsibilities of the council more concretely. Research into voting processes and standing up a voting front-end will also be worked on as part of the Gov-Ops silo work.

After the 2 months are up, we will review the state of the Gov-Ops council and adjust as needed in the next implementation.

Member Roles Ross I expect to perform the following roles, which are an subset of what I currently do for the DAO:

Communicate with applicants and community members to clarify the process to apply for funding from YAM. Make recommendations about the completeness of applications for funding. Manage bookkeeping and governance flows. Collate approved consensus actions into one location used as a source of truth for creating on chain execution transactions. Communicate with different Silos about their expected needs and outline requirements to get their transactions included within the monthly on-chain proposal contracts. Review monthly on-chain transaction and vet them for security and accuracy to the best of my ability. Coordinate with 0xE on what needs to go into them. Maintain and moderate of the following infrastructure: Discord server. Discourse server (forum). Minor maintenance of the main website (https://yam.finance). Time Commitment: 20 hours a month expected. Not to exceed 40 hours a month. Hours to be recorded and accounted for in monthly transparency reports.

Compernsation: Base rate of $85/h, split 70% in stables and 30% in yam tokens based on the 30day avg value.

E I expect to perform the following roles, which are an subset of what I currently do for the DAO:

Assist contributors with the governance and payment processes. Develop, manage and coordinate onchain proposals interacting with the yam governance contracts, including testing, deployment, proposing, execution and following through with the transactions. Approved transactions include*: Payouts for approved contributor payments and grants. Replenishing multisig wallets. Yam Treasury assets transfers and deposits. Swapping and trading Yam Treasury assets through uniswap and exchanges. Depositing and removing UMA tokens from UMA 2Key Contracts. Interact with other approved contracts*. Maintain existing services and systems, including: Yam Website DApp. Yam API and dev docs. Github Organization including related repos and services. Servers. Webhosts. Gitbook. Snapshot. Discord. Telegram. Coordinate and prepare multi-sig transactions. Manage governance security, monitoring and maintenance. Communicate with applicants and community members to clarify the process to apply for funding from YAM. Make recommendations about the completeness of applications for funding, including development feedback.

• See the section below called “Not in Scope of Gov-Ops Council” for more information about what is and is not included.

Time Commitment: 40 hours expected, not to exceed 80 hours a month. Hours to be recorded and accounted for in monthly transparency reports.

Compensation: Base rate of $100/h, split 70% in stables and 30% in yam tokens based on the 30day avg value.

Feddas I expect to perform the following roles:

Communicate with applicants and community members to clarify the process to apply for funding from YAM. Make recommendations about the completeness of applications for funding. Time Commitment: 15 hours a month expected. Not to exceed 30 hours a month. Hours to be recorded and accounted for in monthly transparency reports.

Comp: Base rate of $85/h, split 70% in stables and 30% in yam tokens based on the 30day avg value.

Not in Scope of Gov-Ops Council Code that falls outside of the prior “off the shelf” classification is the responsibility of the Silo or Grantee that is requesting its inclusion. They should write and test the required code and either implement it in their own deployed contract that can be called by the monthly on-chain transaction, or they should coordinate with the Gov-Ops silo to include it directly into the main proposal contract. More information can be found here: https://github.com/yam-finance/documents/blob/master/govops/govops-council.md 2 Specification This document will be posted publicly on the YAM discourse forum for 1 week before voting begins. Each proposed member will get their own snapshot vote, to be posted and last at least 3 days after the completion of the review period.

Assuming acceptance of all 3 votes, work on the above scope will begin in August.