Q1 & Q2 2023 | DAO Teams Budget Request Proposal

I’m not sure where you’re getting 10hrs per week from. On average, I work somewhere between 60-70 hours per week.

In the last six months, I have:

  • Manage comms across two product releases and worked with various teams to market their cover purchases
    • StakeWise ETH Staking Cover co-marketing campaign
    • Sherlock Excess Cover co-marketing announcement
    • Everstake ETH Staking Cover co-marketing announcement
    • Liquid Collective co-marketing campaign
  • Coordinated, provided regular updates on 13 governance proposals, discussions
    • Transitioned DAO proposals to Snapshot votes
    • Provided updates on vote outcomes, review of process
  • Managed comms, coordinated announcements across six listings in Q3, Q4.
    • Worked with Euler, Gearbox, and Nested
      • Planned, participated in Euler Twitter Spaces while on vacation
      • Worked with Nested on regular updates for their repeat cover buys, given they cover their entire TVL with Nested Protocol Cover
  • Managed comms, helped members prepare for, and provided support across three claim evens
    • Provided comms on Celsius claims, though no legitimate claims were filed
    • Provided extensive comms on Hodlnaut claims, shared individual updates on claim submissions, votes, and outcomes. Handled proof of loss questions, followed up with members who didn’t provide proof of loss initially, etc.
    • Shared Hodlnaut claim outcomes, updated claims history section in docs.
    • Provided extensive support for FTX cover holders planning to file claims in February
    • Provided regular updates on cover liabilities, eligible covers for filing for FTX, BlockFi, Gemini Earn after repeat questions from members; added this update to newsletter and community call
  • Attended ETH Berlin, made valuable contacts, represented Nexus Mutual.
  • Worked with engineers and Safe team to get Nexus Mutual listed in the Safe app, so multisigs users could access the Nexus Mutual user interface right from the Safe UI.
  • Regularly reviewed listed protocols, provided chain deployment updates to frontend engineering team, and ensured all listings were up-to-date on which chains they were deployed on and what Protocol Cover protects against (i.e., which EVM-compatibile chains).
  • Coordinated comms on Proposal 172: Capital Pool Investment into Maple Finance via Enzyme
    • Worked with Chainlink, Enzyme, Maple Finance, M11 Credit on co-marketing announcement, campaign
    • Updated Nexus Financials section of documentation to provide members with the resources to review, audit the wETH pool investment
    • Managed updates, comms on Auros, Orthogonal loans
    • Worked with Investment team to share timely updates, as they become available
  • Regularly updated the Nexus Mutual V1 documentation
  • Rewrote the Nexus Mutual V2 documentation, moving all content to open-source Docusaurus platform
    • Worked with engineering team to write user documentation
    • Managed technical documentation project
    • Wrote V2 resources for existing distributors
  • Contributed to, edited 22 issues of the newsletter with Sem, Community Manager, contributing as well
  • Hosted 15 Nexus Mutual community calls, which the Community team started in September 2021
  • Overhauled, and in process of, overhauling the Nexus Mutual Discord server

I’ve heavility contributed to the Nexus Mutual website project; I was a stakeholder in the brand update project; I’ve worked with the engineering team to write the copy in the Nexus Mutual V2 UI; I’ve standardized terminology, so it’s consistent across the mutual; I’ve created a usage guide, glossary for V2; I’ve created a contributors’ guide for those who want to make contributions to the open-source V2 documentation in the future.

Within the DAO, I serve as a resource across teams, and I keep in regular contact with the Foundation teams to coordinate comms, provide support on various projects, and I essentially own the claims process when loss events happen. Since I started working for the DAO, I have defined the comms strategy for claim events, and I am heavily involved from when a loss occurs until the final claim is filed.

I’m dedicated to my role, and I make myself available to other teams, to Foundation teams, and to members who ask for help on Discord, Twitter, and beyond. My Community Manager, Sem, has helped me with regular reporting, answering questions in Discord, writing a portion of the newsletter each week, contributing research to the projects I work on, and more.

All of the proposed teams have their roles defined, with individual contributors denoted with (FT) for full-time, (PT) for part-time, and Contractor for those who are contributing on a short-term basis. You can see a breakdown of all the teams in the Q1 & Q2 2023 | Proposed Teams, Priorities, and 6-month Budget Breakdown post.

Working across teams within a DAO requires regular meettings, consistent communication, and collaborative work. I regularly work with all of these teams, and they put in a significant amount of work.

1 Like