[Ideation] SCP-215 (Amendment): Engineering Workstream Contributor Addition, June 1 – September 30, 2026

Status: Revised version of SCP-215 after community feedback.
Parent proposal: SCP-212 (Engineering Workstream Renewal: April 1, 2026 to September 30, 2026)
Supersedes: SCP-215 (abandoned following community feedback)

Abstract

This proposal adds discostu as a fractional contributor to the Engineering Workstream for four months (June 1, 2026 through September 30, 2026). Responsibilities cover BD, partner-facing product work, marketing and comms, and targeted engineering contributions with Kev.

FBL is stepping down from the Product Lite Workstream (SCP-210) at the end of May 2026. Discostu's existing BD scope under that workstream needs a new home. Rather than creating a separate workstream, this amendment places his work under Engineering. This keeps BD and partner velocity intact, supports the DAO's API revenue priority, and limits governance overhead.

Compensation is 100% FOX ($6,500/month). Zero USDC burn, preserving DAO runway.

This is a revised version of SCP-215 after community feedback: compensation reduced from $9,500/mo (USDC + FOX mix) to $6,500/mo (100% FOX), and scope trimmed (Telegram management removed, Roadmap prioritization downgraded to input, Linear management removed from scope).

---

Motivation

Main objective

• Reduce the gap with competitors

• Build long-term relationships with chains and projects approached

• Work on continuous API/Widget improvement with Kev

• Once enough chain contacts have been established and the API/Widget is fully polished, launch a coordinated marketing campaign promoting the API/Widget to builders, with chain partners actively amplifying the campaign across their channels for maximum reach

Why absorb into Engineering rather than create a separate workstream

• This role requires close, ongoing collaboration with the Engineering team. Placing it under the Engineering Workstream simplifies that coordination.

• Lean governance: one workstream, one budget, one contributor amendment, instead of creating multiple parallel proposals.

• Continuity: avoids disruption to active integrations and communications with current partners (Bob, MegaEth, pait.fi, Brila, and others).

---

Specification

Team addition

• discostu: Contributor (BD, light Product, Marketing/comms), reporting into the Engineering Workstream.

Scope: what discostu owns

Chain relations

• Chain listings: getting ShapeShift listed on relevant chain ecosystems

• Chain co-marketing: X posts, blog articles, LinkedIn posts coordinated with chain partners

• Chain integration: getting ShapeShift featured on chain landing pages alongside other bridges

• Chain analysis: providing the Engineering team with complete analyses of high-potential chains and their ecosystems
  Partner integration (API/Widget)

• Continued outbound to projects for ShapeShift's API/Widget

• Closing API partners and managing the BD pipeline

• API partner onboarding: documentation, technical integration, and support, with Kev

• Co-marketing management with projects integrating ShapeShift: X posts, blog articles, LinkedIn posts
  Product

• Input on roadmap prioritization: providing competitive analysis and partner pipeline signal to inform Engineering's decisions on shipping order. Engineering retains decision authority.

• API / Widget landing page redesign: improving conversion and lead quality, directly aligned with outbound BD.

• Partner portal page: improving the partner portal to make registration and follow-up more intuitive for projects integrating ShapeShift.
  Engineering contribution

• Competitive intelligence and targeted PR contribution: analyzing opportunities identified in research, and opening targeted PRs to help Kev close gaps with competitors.
  Operations

• Custom automation tool: building and maintaining the Twitter/Telegram/Salesforce tool for partner follow-ups and lead tracking.

• Marketing and comms: managing partner-facing comms (blog articles, Twitter/LinkedIn posts) and partner communication.

• Cross-workstream coordination: async with Tokenomics, Operations, and other workstreams via DMs and writing.

• Weekly written reports: continuation of existing cadence.

Scope: explicitly NOT covered

• Hosting shapeshift.com and Railway migration: remains with Engineering core.

• Public positioning (Spaces, podcasts): not within this scope.

• Telegram management: not within this scope.

---

Coordination with Engineering

• Reporting: discostu's weekly written reports continue, integrated with Engineering's existing cadence.

---

Period

June 1, 2026 – September 30, 2026 (4 months)

---

KPIs

Outbound and pipeline

• Continued outbound to chains and projects throughout the period, focused on quality of relationships. Closes are subject to the API/Widget reaching a polished, sellable state.
  Chain relations

• Secure ShapeShift listings on 80%+ of newly integrated chains

• Deliver a co-marketing plan for each chain integration
  Product

• Ship the API / Widget landing page redesign during the period

• Weekly written reports delivered on the existing cadence

---

Budget

Compensation structure (discostu)

• Monthly FOX: $6,500 (100% FOX)

• 4-month total: $26,000

• Zero USDC burn
  Note: Apotheosis's weekly hours under SCP-212 are increased from 6 to 8 hours/week to support discostu on calls and weekly check-ins. Monthly compensation goes from $2,688 to $3,583 USDC.

https://docs.google.com/spreadsheets/d/1vkx8ncUDW0sJIATWrujIc2_onCZR_Q5Yr69B5smkCAc/edit?usp=sharing

---

Benefits

• Resources the API revenue path: drives outbound to chains and projects, owns the landing page redesign, and frees Kev to focus on technical readiness.

• Keeps BD and partner velocity going through FBL's transition without a governance gap.

• Tighter loop between BD/Marketing wins and Engineering shipping (less context-switching).

• 100% FOX compensation: zero USDC burn, preserves DAO runway during austerity, aligns contributor incentives with DAO success.

• Lean governance: one consolidated proposal instead of two parallel workstreams.

• Continuity for active partner relationships already created (Katana, MegaEth, Starknet, BOB and in-flight API customers).

• Discostu retains direct collaboration with Kev for technical work on competitive PRs.

---

Drawbacks

• BD sales cycles are long. Partner deals (chain integrations, API customers) take months from initial contact to close.

• Discostu is not a native English speaker. Some high-stakes partner calls may benefit from backup, which Apotheosis has offered to provide.

---

Vote

• For: Approve the addition of discostu to the Engineering Workstream as a fractional contributor for the period June 1 to September 30, 2026, with the scope and compensation outlined above.

• For with changes: Approve with the following modifications: {X, Y, Z}.

• Against: Do not add discostu to the Engineering Workstream.