[SCP-207] Operations renewal March 2026 - August 2026

Summary

Approving this proposal is would signal a continuation of budget funding for March 1st 2026 - August 31st, 2026, for an ninth consecutive term for the current Operations workstream that was established and renewed with passing of the previous proposals: [SCP-8], [SCP-59], [SCP-94], [SCP-125], [SCP-147], [SCP-165], [SCP-179], and [SCP-190].

This proposal seeks to renew the Operations workstream with its current contributors, but with a reduction of its KPIs and goals relative to the reduction in compensation. The Operations workstream is always open and flexible to collaborative updates to future responsibilities, processes, and success metrics to continue to support the DAO as we continue to constantly evolve.

This proposal adopts [SCP-92] Definition of Workstream Leader

Abstract

The Operations workstream is an integral part of the growth and development of healthy systems for reliably producing and maintaining the ShapeShift product suite and its uptime, responsiveness and feature functionality. The Operations workstream provides front line assistance and monitoring of the products produced by the DAO in both customer support and feature testing throughout the release process. The workstream additionally provides similar support and structure to the DAO, its ecosystem, networks, and meeting structure.

Through Production Issue Procedure Best Practices, Triage Management, Deployment and Regression Testing, Customer Support and DAO Admin Procedures and Practices, the ShapeShift DAO Operations Workstream provides essential resources and tools for efficiency, organization, and overall product and services health that are vital to the success of the DAO, the product suite, it’s contributors, and $FOX token utility.

Motivation

Renewing this workstream will allow Operations to continue to work side by side with other workstreams to increase efficiency in individual procedural processes across the DAO and help progress deployment and testing processes while still verifying and maintaining reliability, health, and full functionality of all outlined responsibilities and services.

Areas of focus and Operations responsibilities maintained by the workstream also include: Hosting the Weekly Governance call and advocating the Governance process, Organizing and hosting the quarterly AllFox community call, Leading and collaborating Expected Feature Release Testing guidelines, and other meetings or DAO processes, RDP management, and full coverage of customer support.

The Operations workstream continues to focus on the wider picture of the product suite’s uptime, functionality, and overall health and user support. It additionally mirrors that responsibility in the DAO Discord, Github (Linear), and Notion by synergizing and coordinating cross-stream collaboration further strengthening the DAO. Specification

The Operations workstream Notion repo can be found here.

Operations maintains:

Triage: Known Issues, Release Stats and testing fees,Ops Sprint, Governance Call, AllFox, Go/NoGos, Retros, RDP program, Customer support (via Chatwoot).

The Operations Workstream strives to keep the greater DAO agile and committed to maximizing efficiency, scalability, and transparency with a strategic lean into data-based decision making. At times, best practices and procedures may be challenged, modified, updated, changed, archived or revisited to maintain those objectives. (See: Marketing content creation support flow, The Bounty Process, Trusted Community Devs, Triage Report Tracker, Unsolved User Problems, the governance tracker, POAP minting, daily regression testing, the evolution of goat/no goats, Gitbook, etc)

The renewal term length for this workstream and its contributors is 6 months, from March 1st, 2026 through August 31st, 2026.

This proposal continues @TylerTylerTylerTyler | ShapeShift as the Workstream leader, @MBMaria as Operations Coordinator, and @Reedthorfox as an hourly part time contributor.

Budget ask: $60,000 over 6 months to be sent monthly in Colony in locked and unlocked FOX

Previous Monthly total budget: $26,900 Previous Monthly USDC: $16,648 (62%) Previous Monthly FOX: $10,252 (38%)

New Monthly total budget: $ $10,000 (62.8% decrease in overall budget) New Monthly USDC: $0 (0%) (100% decrease) New Monthly FOX: $10,000 (100%) (2% decrease)

Old 6 month snapshot of 12 month USDC budget: $99,888 Old 6 month snapshot of 12 month FOX budget: $61,512 Old 6 month snapshot of 12 month Total budget: $161,400

New 6 month USDC budget: $0 New 6 month FOX budget: $60,000 New 6 month Total budget: $60,000

Realized USDC savings from new proposal: $16,900/month or $101,400/term

Full budget details

There are two changes in this proposal’s budget from the previous renewal:

Compensation decreases were given to both Tyler (-75.86%) and MBMaria (40.48%). Tyler’s job requirements, responsibilities, and availability will be adjusted going forward with emphasis and priority given to supporting and triaging Ops issues, being an advocate for Operations in Leadership, Advocating for Ops Sprint, Weekly Governance, Weekly Leadership, and Quarterly AllFox. Tyler’s availability will dramatically change with this decrease and his role will be fractional/part time. MBMaria has proven to be a backbone of the Operations Workstream and has continually upskilled to match the requirements and requests of the Engineering team in our testing and release processes. Testing requirements may change over the course of the term but have still proven to be essential during the transition to more disruptive integration with AI. Her compensation has reduced to near what she was making when she was first hired albeit her responsibilities and tasks have only increased during her career here.

A decrease in Test funds/Op EX/We FOX’ed up was also applied to reduce the amount of FOX asked and being used to test.

This changes reflect an acknowledgement that the only way the DAO will be able to see meaningful revenue is through dramatically altering the spend needed to maintain and continue the project. This proposal seeks similar adjustments in compensation to mirror other tough decisions that were made in the mind of austere survival. Following in the footsteps of [SCP-204], and the reduction of the Marketing Workstream spend recently, this proposal puts the DAO first, forgoes any compensation in USDC, and keeps the essential team and integrity of the Operations workstream at an extremely minimal budget.

Operations would account for ~0% of the total DAO monthly stable spend if this proposal were to be passed. Taking only FOX does not solve the revenue problems the DAO is facing, but it is a first step in isolating the factors the DAO has control over while it rediscovers cost and utility for all workstream renewals.

If network conditions or the price of FOX decreasing dramatically alters or changes Operations ability to perform required deployment and regression testing, an additional proposal addendum for test funds may be proposed.

Operations will continue to be mindful and agile about its processes with the DAO to continue to provide proficient coverage and support in all of the outlined areas of this proposal while continuing to maintain our KPIs under this optimized budget.

Specific Goals and Success Metrics The goals and success metrics for the Operations Workstream are listed below, split into current Goals and KPIs.

Current Measurables:

Production Issue Best Practices Goals: To minimize downtime of the entire product suite. To resolve production environment bugs efficiently with minimal disruption to engineering processes, deployment cadences, or user experience. KPIs: 99% uptime of the product suite and services: August: 100%, September 100%, October: 100%, November: 99.9%, December: 100%, January: 100%, February: 100% Average 6 month uptime: 100% (99.83% last term) <8 Production Issue Escalations per Quarter: 0 escalation in the last 3 quarters: 0 in Q2, 0 in Q3, 0 in Q1. <50 Total Combined DAO Contributor hours dedicated to Production Issue Resolutions Per Quarter: 0 hours dedicated.

Triage Management Goals: To discover, isolate, navigate, and manage resolutions of user facing issues in all ShapeShift products and services. To provide known troubleshooting and mitigation steps for issue reporters and users during the discovery and recreation of triage tickets. To mitigate and expedite time required from core contributors spent on bug tickets, issue reports, and production level emergencies.

To transfer correctly completed and accurate Github tickets of triage bugs to Engineering or Product to be posted for bounty. KPIs: Greater than 80% resolution rate goal: 100% this term, 88.39% term seven, 96.8% Resolution term six, 75.3% Resolution rate term five, 71% resolution rate term four. This goal was maintained this term. Operations succeeded in continuing our overall resolution rate term over term with improvements and optimizations to the Triage process and ticket review/clean up practices as a new focus the previous term.

Deployment and Regression Testing

Goals: To catch 95% of prod issues during the deployment testing process. To catch user facing issues in production environments in regression tests and #triage them accordingly. A deployment test is completed by the Operations Workstream during each release process and upon request in pre-deployment branch testing. Specific regression tests are performed twice a week by an Operations Workstream contributor to complete a full monthly regression testing schedule in accordance with regression testing best practices.

The rest of this proposal is over the character limit for SnapShot but can be read and engaged with on the forums attached below: