[RFC] SCP-TBD - Renewing the Operations Workstream Feb - July 2024


Approving this proposal is would signal a continuation of budget funding for another 6 month term, February 1st - July 31st, 2024 (sixth 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], and [SCP-147].

This proposal seeks to renew the Operations workstream with its current contributors, KPIs, and goals. 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


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.


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, Marketing support and release communication, Leading and collaborating in Product specs, Weekly Release Thread updates in the forum, Expected Feature Release Testing guidelines, Go/No Gos, Retros and other coordinated meetings or DAO processes, RDP management, Gitbook documentation management (Undergoing a facelift this renewal),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, and Notion by synergizing and coordinating cross-stream collaboration further strengthening the DAO.

This six month period will have an additional focus on building out resources and KPIs focused around error monitoring in mixpanel and functionality monitoring such as refunded trades in decentralized public resources.


The Operations workstream Notion repo can be found here.

Operations maintains:

Triage: Known Issues

2023 Prod Issues tracking, Release Stats and testing fees,

Ops Sprint, Governance Call, AllFox, Go/NoGos, Retros, RDP program, Gitbook, 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: 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, etc)

The renewal term length for this workstream and its contributors is 6 months, from Februrary 1st 2024 to July 31st 2024.

This proposal continues @Tyler | ShapeShift as the Workstream leader and @MBMaria as Operations Coordinator.

Budget ask: $132,000 $177,000 - 25.42% ($45k) less than the previous term

Monthly USDC: $16,250 - 31.94% reduction from $23,875.00 last term.

Monthly FOX: $5,749.80 - 2.22% increase from $5,625.00 last term.

Monthly total budget: $22,000.00 - 25.42% reduction from $29,500.00 last term.

6 month USDC budget: $97,501.20

6 month FOX budget: $34,498.80

6 month Total budget: $132,000.00

Full budget details

Operations would account for ~8.3% of the total DAO monthly stable spend if this proposal were to be passed:
Current monthly USDC spend: 203,550 - Marketing renewal USDC savings: $2300 - Operations renewal USDC savings: $7625 = Operations New monthly USDC spend: $16250/New monthly USDC spend $193,625

The budget has been reduced in $USDC spend to continue to keep a conscious effort in reducing the footprint the Runway. This tighter budget removes one contributor role in the budget and maintains an agile and intimate team of Operations contributors that can collaborate across time zones to provide adequate coverage for support, triage, testing, and all other outlined needs of other workstreams, the DAO, and its product suite. This budget has a reduced team of 2 full time contributors as opposed to the staffing room for 3 approved in the previous term. All test and misc funds are now budgeted in FOX and reduced by 50% from the previous term’s budget.

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 maintaining 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


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.


99% uptime of the product suite and services:

August: 98.9%

September 100%

October: 100%

November: 100%

December: 100%

January: 100% (so far)

Average 6 month uptime: 99.81% (98.29% last term)

<8 Production Issue Escalations per Quarter - 0 Escalations in Q3, 0 Escalations in Q4, 0 in Q1 so far.

<50 Total Combined DAO Contributor hours dedicated to Production Issue Resolutions Per Quarter: 0 hours dedicated.

Triage Management


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.


Greater than 80% resolution rate goal: 75.3 Resolution rate this term, 71% Resolution rate last term, 66% resolution rate previous term.

This goal was not hit this term again overall. Operations is improving our overall resolution rate term over term and aim to be able to exceed this KPI in this proposed term with improvements and optimizations to the Triage process and ticket review/clean up practices as a new focus this term

Deployment and Regression Testing


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 once a week by an Operations Workstream contributor to complete a full monthly regression testing schedule in accordance with regression testing best practices.

Operations prioritize blocking bugs, supporting engineers, and efficiency in the processes already in place over chasing non-blocking bugs for a ‘perfected’ release.

In the 129 releases deployed since August 1, 2023, 0 total prod issues were experienced. 0 Production issue bugs in 129 releases = 100%


<2 Cadences missed per quarter due to bugs overlooked in Ops Testing (0 cadence missed last term)

<2 Rollbacks during releases per quarter due to bugs overlooked in Ops Testing (0 Rollbacks occurred last term)

DAO Admin Procedures and Practices


To organize successful DAO meetings related to Goat/No Goat, Retros, Ops Sprints, and AllFoxes.

To track, organize, record, and optimize DAO repos keeping them current and relevant. To help in cross workstream collaboration projects that optimize efficiency and collaborative, transparent communication.

To provide assistance in projects that require support in generating procedures to be completed for the DAO or other workstreams.


Keep All Workstream leaders and key contributors informed and involved in contributions to all Ops Sprints, Governance Calls, AllFoxes Slide decks, Go/No Gos, and Retros.


If this proposal passes, the DAO will continue to fund the Operations workstream budget to meet the deliverables and services outlined which are integral to the DAO’s success and current practices. Coverage for Prod Issue escalations, Triage Management, Regularly scheduled regression and deployment testing, Customer Support, Cross workstream alignment and stakeholder resources would all be focused, maintained and improved upon by the workstream.

Passing this proposal will continue uninterrupted support and services offered from the Operations workstream to the DAO.


Funding this workstream costs the DAO stablecoins and FOX during the duration of the proposed term. This workstream would cost the DAO treasury potentially $132,000 over 6 months ($22,000/month) if all funds are needed and exhausted in the budget costing the DAO $ from the stablecoin runway.


Well-crafted proposal. I applaud your efforts to keep working with and running a lean and mean operations team with runway longevity in mind.

Thanks for coordinating all the things like All-fox, retro’s, ops sprints, etc. It’s often unsung praise, but you and your team have done a great job keeping things going there!

You have my vote of support :slight_smile:

1 Like