# SCP-224: Engineering Workstream Renewal: October 1, 2026 – June 30, 2027

- Space: [ShapeShift](https://snapshot.box/s:shapeshiftdao.eth.md)
- Author: 0x96E2cD42DBa2fe7102aca8887A663a0A1F18d293
- State: Passed
- Voting type: Basic
- Start: 2026-09-20 06:47 UTC
- End: 2026-09-25 06:50 UTC
- Votes: 14
- Quorum: 4,000,000 voting power
- Discussion: https://forum.shapeshift.com/t/scp-224-engineering-workstream-renewal-october-1-2026-march-31-2027
- Open in Snapshot: https://snapshot.box/#/s:shapeshiftdao.eth/proposal/0x5138ce866d18844cec8de87b56c22666f3761535efb7f01d654dcd0e9ebfcf7d

## Results

- For: 41,340,058.16 voting power, 100.0%
- Against: 0 voting power, 0.0%

## Proposal

Abstract

This proposal seeks continued funding for the Engineering Workstream for nine months, from October 1, 2026 through June 30, 2027.

It renews the team established under [SCP-212](https://forum.shapeshift.com/t/scp-212-engineering-workstream-renewal-april-1-2026-september-30-2026/3383) and expanded through [SCP-217](https://forum.shapeshift.com/t/scp-217-amendment-engineering-workstream-contributor-addition-june-1-september-30-2026/3457): kaladinlight as a full-time Senior Engineer, Apotheosis as fractional Workstream Leader & Senior Engineer, and discostu as a Business Development & Marketing contributor.

The main change is an increase in Apotheosis’s allocation from one to two days per week, at his current hourly rate. This provides dedicated time to stay across the codebase and contribute development work alongside the workstream’s administrative and leadership responsibilities. kaladinlight remains full-time.

The total requested budget is **$374,200 in USD value** for the nine-month period, including infrastructure and a single one-time discretionary allocation.

## Motivation

This renewal supports new partner acquisition and the engineering work needed to guide partners through technical evaluation, onboarding, and integration, alongside maintaining ShapeShift’s products and continuing development.

## Specification

### Team

**Apotheosis — Workstream Leader & Senior Engineer, two days per week**

Continues to lead the workstream, coordinate engineering priorities, support partner discussions, and manage the administrative responsibilities required to keep services running. The additional day provides regular capacity for code review, codebase familiarity, bug fixes, and product development. Specific development work will be scoped alongside kaladinlight according to current priorities.

**kaladinlight — Senior Engineer, full-time, five days per week**

Continues to lead day-to-day implementation, infrastructure maintenance, production incident resolution, and prioritized development. Works with Apotheosis to distribute suitable engineering tasks and share technical context.

**discostu — BD & Marketing**

Leads API/Widget business development and new partner acquisition, with responsibility for partner onboarding and support, chain relationships, and basic marketing. This includes partner-facing communications, content, and coordinated marketing activities to support outreach and integrations. He also provides product input and targeted technical contributions in coordination with Engineering. Weekly written reporting continues, and Engineering retains authority over implementation priorities.

### Priorities

New partner acquisition and support for that process are explicit engineering priorities. Engineering will work closely with discostu on prospective partner calls, technical questions, integration guidance, and resolving issues that prevent partners from adopting the API/Widget. Partner feedback and integration needs will inform development priorities, with continued support as partners move into production.

Production stability, essential maintenance, and issues affecting existing users and integrations remain core responsibilities. The team will balance these needs with the work required to acquire and onboard new partners.

The team will also maintain practical service and access documentation to make operational handovers easier.

### Mandate

The Engineering Workstream’s existing mandate continues: responsibility for maintaining the ShapeShift GitHub namespace, including CODEOWNERS and administrative permissions, and reviewing external contributions to preserve code quality and stability.

## Budget

The figures below follow the [October 2026–June 2027 budget](https://docs.google.com/spreadsheets/d/1NHHTY2mp7YgwtaVlPIKzI3vgNqIZNoiFlAnWRvOIQFQ/edit?gid=117953929#gid=117953929). Contributor monthly rates are unchanged, with recurring costs extended to nine months to align with future workstreams. The infrastructure ceiling has been reduced to $10,000 per month. Amounts are expressed in USD value; payment assets are identified separately.

### Recurring costs

| Item                         | Allocation      |     Monthly |   Nine months | Payment asset |
| ---------------------------- | --------------- | ----------: | -----------: | ------------- |
| Apotheosis                   | 2 days/week     |      $7,167 |      $64,500 | USDC          |
| kaladinlight                 | Full-time       |     $17,500 |     $157,500 | USDC          |
| discostu                     |                 |      $5,800 |      $52,200 | FOX           |
| **Contributor compensation** |                 | **$30,467** | **$274,200** |               |
| Infrastructure               | Monthly ceiling |     $10,000 |      $90,000 | USDC          |
| **Total recurring**          |                 | **$40,467** | **$364,200** |               |

Infrastructure funding covers the services required to operate ShapeShift’s products. The $10,000 monthly allocation is a spending ceiling, with unused funds returned to the DAO.

### Non-recurring costs

A single **$10,000 USDC discretionary allocation** is requested for the entire Engineering Workstream over the full nine-month term. It covers engineering, marketing, and other unforeseen workstream needs at the workstream’s discretion. This is a one-time allocation, separate from contributor compensation. Unspent funds will be returned to the DAO.

### Total request

discostu’s compensation will be paid 100% in FOX. The funding request is split as follows:

| Payment asset | Monthly recurring | Nine-month request, including discretionary |
| --- | ---: | ---: |
| USDC | $34,667 | $322,000 |
| FOX, expressed in USD value | $5,800 | $52,200 |
| **Total USD value** | **$40,467** | **$374,200** |

The FOX amount above is a dollar-denominated compensation budget, not a fixed number of tokens.

### Changes from the amended budget

This comparison uses the monthly allocations in effect under SCP-212 as amended by SCP-217.

| Item | Previous monthly | Proposed monthly | Change |
| --- | ---: | ---: | ---: |
| Apotheosis | $3,583 | $7,167 | +$3,584 |
| kaladinlight | $17,500 | $17,500 | $0 |
| discostu | $5,800 | $5,800 | $0 |
| Infrastructure | $15,000 | $10,000 | −$5,000 |
| **Total recurring, USD value** | **$41,883** | **$40,467** | **−$1,416** |

The previous compensation figures come from the [SCP-212 budget](https://docs.google.com/spreadsheets/d/1NHHTY2mp7YgwtaVlPIKzI3vgNqIZNoiFlAnWRvOIQFQ/edit?usp=sharing) and the [SCP-217 compensation amendment](https://forum.shapeshift.com/t/scp-217-amendment-engineering-workstream-contributor-addition-june-1-september-30-2026/3457). Comparisons use the published rounded monthly amounts.

### Variance

Unused funds from any budget category will be returned to the DAO at the end of the budget cycle. If additional funding is required, the workstream will raise a separate governance proposal.

## Benefits

- Adds regular engineering capacity and keeps workstream leadership closer to the codebase.
- Broadens the team's ability to review and implement changes, reducing reliance on one engineer.
- Makes new partner acquisition and technical support throughout evaluation, onboarding, and integration explicit engineering priorities.
- Retains engineering, business development, and basic marketing within one workstream.
- Continues discostu’s compensation entirely in FOX.

## Drawbacks

- The proposal funds nine months of operations and includes a $10,000 discretionary allocation for the full term, drawing on the DAO’s treasury.
- The team remains small. Production incidents and maintenance needs may delay planned development.
- Apotheosis remains fractional, so the additional day provides limited capacity and does not remove key-person risk.
- Product and partner work may support revenue growth, but this budget does not guarantee commercial outcomes.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

