SCP-212: Engineering Workstream Renewal: April 1, 2026 – September 30, 2026

Abstract

This proposal seeks continued funding for the Engineering Workstream for six months (April 1, 2026 through September 30, 2026).

In line with the DAO’s transition to a lean operating model, the Engineering team has been significantly restructured — reducing headcount from five full-time engineers to one full-time engineer and one fractional contributor (~15% capacity).

The primary objective is to provide the DAO with sufficient engineering capacity to maintain its existing products and ensure current revenue streams remain unaffected. Where capacity permits, the team will continue to drive product development so the DAO’s products can continue to evolve.

This proposal represents an approximately 73% reduction in total engineering spend compared to the previous period ($770,250 over six months).

tl;dr Kev (full-time) manages infrastructure, addresses production issues, handles prioritized bug fixes, and drives forward product development. Apotheosis (fractional, ~15% capacity) serves as the primary point of contact for Engineering, handles account administration (service configuration, API key management, access controls), manages vendor relationships, and handles bill payments.

Motivation

The DAO’s existing products currently generate approximately $35,000 per month in revenue. Continued engineering support is essential to protect this revenue stream — without it, production issues would go unresolved, infrastructure would go unmanaged, and revenue-generating products would degrade. This proposal ensures continuity of operations with a lean team at a fraction of the previous cost, while preserving capacity for forward progress on the product roadmap.

Specification

Team

  • Apotheosis — Workstream Leader & Senior Engineer (fractional, ~15% of previous capacity). Primary point of contact for Engineering. Responsible for account administration including service configuration, API key management, and access controls. Manages vendor relationships and bill payments. Coordinates with other workstreams and external contributors on engineering matters. Available for critical engineering support as needed.
  • kaladinlight — Senior Engineer (full-time). Manages infrastructure, addresses production issues, and handles prioritized bug fixes and product development.

The two contributors operate across significantly different time zones, providing broader coverage for critical engineering support and reducing the window during which no engineer is available to respond to production issues.

Mandate

No changes to the previous mandate, restated below for reference:

This proposal seeks to have the Engineering Workstream be the sole maintainers with discretion over CODEOWNERS, permissions and administrative rights of the ShapeShift GitHub namespace.

This is to ensure the DAO maintains a high standard of code quality, velocity, reduced regressions, and has a single core team acting as maintainers responsible for the codebase.

The Engineering Workstream will work with external contributors to ensure contributions can be made expeditiously while not compromising quality, patterns or stability.

Budget

The details below expand upon the budget spreadsheet.

  • Monthly labor: $20,188 USDC
  • Monthly infrastructure: $15,000 USDC

Recurring Costs

Labor

This proposal reduces headcount from five full-time engineers to one full-time (Kev) and one fractional contributor at approximately 15% of previous capacity (Apotheosis).

Infrastructure

Over the past 12 months, the Engineering team has absorbed most ongoing infrastructure expenses from the Foundation. The previous proposal allocated $20,000/month for node expenses; we have since reduced these costs to approximately $11,500/month, with plans to achieve a further 20–30% reduction through strategic vendor agreements expected to be in production by end of April 2026.

In addition to node providers (Liquify and Moralis), the Engineering Workstream now manages the following services: Railway, Sentry, Vercel, GitHub, Alchemy, Helius, Zerion, Pinata, and Exchange Rate Host. The combined cost of these ancillary services is variable but totalled $1,523.50 for the most recent billing cycle.

This proposal includes a line item for up to $15,000 USDC per month to cover ongoing infrastructure costs. All unspent funds from this line item will be returned to the DAO.

Non-Recurring Costs

Miscellaneous

The budget includes a $5,000 USDC discretionary allocation, available for use at Engineering’s discretion for unforeseen needs. Any unspent funds will be returned to the DAO.

Contingency

Present in all previous Engineering Workstream proposals, the contingency line item has been removed in this proposal.

Variance

Unused funds from any budget category will be returned to the DAO at the end of the budget cycle. In the event that the Engineering Workstream requires additional funds, a separate governance proposal will be raised.

Benefits

  • Maintains and stabilizes the existing product suite, protecting approximately $35,000/month in revenue
  • Retains capacity for product development where bandwidth permits
  • Funds the infrastructure required to keep ShapeShift’s products operational
  • Distributed time zones between contributors provide broader coverage for critical engineering support
  • Represents an approximately 73% reduction in engineering spend compared to the previous period while retaining critical capabilities

Drawbacks

  • Reduced team capacity will result in slower roadmap progression
  • Reduced capacity to sustain parallel workstreams
  • Single points of failure with only two contributors
2 Likes

Snapshot ideation posted here.

1 Like

Thanks for writing this proposal and attempting to preserve a functional Engineering team for the DAO in these times. I’m still not fully convinced this early maintenance mode strategy will help, but it seems to be the consensus in the DAO.

With the team reduced to only two contributors, what contingency plans are in place if both people are temporarily unavailable? In such a scenario, would it be possible for Operations to restore or stabilize degraded services using documented processes and existing tooling?

If no such measures currently exist, would it make sense to include the creation of minimal contingency documentation (covering critical systems, credentials, and recovery procedures) in this proposal as a potential mitigation to this “drawback”?

1 Like

Likewise, but that is the sentiment of our milieu.

I suspect not for core technical issues, though for others (e.g. API keys needing additional funds due to overuse) we could ensure 3rd party service usage and access is documented to share the knowledge.

Agree, a very reasonable thing to do.

2 Likes

Thanks for your answers!

For what it’s worth, I would support a proposal that funds two full-time Engineers even if it implies less runway in “maintenance mode” for the DAO, as long as it strengthens both our product innovation pace and the stability of our services.

But obviously I’m just one voter and I’m not privy to all the internal discussions within the Engineering WS and Leadership about this which led to the current proposal. That’s just my perspective based on the DAO treasury and my contributions for the DAO which make me follow the devs’ work / code base and occasionally work with them on it.

I’ve included this in my “For with changes” vote then :+1:

2 Likes

it looks like this is going positive…

so it feels like its safe for me to vote.

2 Likes

I think you might have posted this on the wrong forum post, @Fireb0mb1!

1 Like

Indeed… wrong tab and not enough sleep :laughing: Will post it in the right thread.

Snapshot Full Proposal

ideation past with no opposing.

Thanks for the changes, good luck in the Final Vote!

1 Like