SCP-217 (Amendment): Engineering Workstream Contributor Addition, June 1 – September 30, 2026

Proposal Discussion
1

After a day to think about the vote outcome, I realized just lowering the ask is probably best. We’re about to integrate on Venice, which will give us our first real opportunity to get exposure and grow from there. Everyone on both sides is excited about this integration, and now I can sell more. I also heard from a couple of voters that they were out of town when my proposal was up, they were excited to actually vote for growing sales, but they didn’t have their wallets with them. I think trying for more participation is worth it. So I submit again.
One more opportunity for people to give me feedback if they haven’t had the chance yet.

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 did not renew the Product Lite Workstream (SCP-210). 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 where his work has impact. This keeps BD and partner velocity intact, supports the DAO’s API revenue priority, and limits governance overhead. Compensation is 100% FOX ($5,800/month). Zero USDC burn, preserving DAO runway.

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 (teller, 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

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, Twitter/LinkedIn posts

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

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.

  1. Operations

    • Custom automation tool: building and maintaining the Twitter/Telegram/CRM 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: $5,800 (100% FOX)

  • 4-month total: $23,200

  • 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.

image
image1628×1218 178 KB

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.

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.

1 Like
2

Thanks for resubmitting this with some adjustments! I hadn’t noticed that the “Drawbacks” section completely disappeared after the first ideation, was that intentional?

I still support this proposal. The business opportunities you have developed will benefit the DAO, and without your participation they are unlikely to materialize. This would harm the DAO’s future and waste the resources already spent/invested in the work you completed over the past months.

The downward trend in our revenues, while partially linked to a disastrous market, still makes me think we do need invest in marketing/sales initiatives. You are motivated to provide them for the DAO at a reasonable and FOX-only cost, so I feel it would be a strategic mistake to pass on this.

As I said before, I really wish that those who are against this would voice their own business strategy for the DAO in the coming months, and explain how slightly prolonging the runaway by cutting more people/initiatives (especially ones that could potentially generate revenue in the short term) is going to help the DAO.

1 Like
3

Thanks Firebomb for pointing out the drawbacks, they were fair points.

On the language side, I’m not a native English speaker, which is why Apo joined to handle partner calls directly.

On the pipeline, we already have partners ready to integrate. Some are already in the process (Venice, Teller). The biggest risk right now is having nobody to manage the cycle and losing those integrations.

I’d like to hear from people voting against this proposal.
I want to understand where you’re coming from and how you see things moving forward with the projects that already spent time going through our docs and started integration work.

Thanks again to everyone giving real feedback.