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

Proposal Discussion
1

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, community (Telegram), 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 a mix of USDC base and FOX. The split reflects the operational and BD nature of the role while keeping FOX exposure for DAO alignment.

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, community), reporting into the Engineering Workstream.

  • Existing Engineering team (per SCP-212) unchanged: Apotheosis (Workstream Lead, fractional), kaladinlight (Senior Engineer, full-time).

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

  • Linear: managing Product/BD-side projects and initiatives in close coordination with Engineering. Inheriting templates, starter specs, and agent instructions from FBL’s transition handoff.

  • Roadmap prioritization: deciding shipping order based on business case, competitive analysis, and revenue potential, with Engineering validation for feasibility.

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

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 and community

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

  • Telegram management: restructuring the ShapeShift Telegram (currently locked/inactive) to welcome future builders and community members.

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

Coordination with Engineering

  • Linear: discostu owns Product/BD-side initiatives in Linear.

  • 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 and community

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

  • ShapeShift Telegram restructured and active again

  • Weekly written reports delivered on the existing cadence

Budget

Compensation structure (discostu)

image
image1782×1228 343 KB

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.

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 wins and Engineering shipping (less context-switching).

  • Compensation structure reflects the operational and BD nature of the role (USDC base) and keeps DAO alignment (FOX upside).

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

  • Continuity for active partner relationships (Katana, MegaEth, in-flight API customers).

  • Restores community presence through the Telegram restructure.

  • Discostu retains structured access to Kev for technical collaboration on competitive PRs.

Drawbacks

  • BD sales cycles are long. Partner deals (chain integrations, API customers) take months from initial contact to close. Some pipeline initiated during this period may not convert until after the period ends.

  • Outbound momentum depends partly on the API and Widget reaching a polished, sellable state, which is on Engineering’s roadmap.

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

  • Period aligned strictly to SCP-212. Continuation past September 30, 2026 depends on the next Engineering Workstream renewal proposal passing.

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.

2 Likes
2

I’m a no at this time with these numbers.

2 Likes
3

i dont know any benefit thats hit home from the start.

i read the reports, showed a few completed, but hadnt seen them enter the partnership system, and conversation around them being brought in?

This is a huge $ ask.

We are working on lowering the out pay, every chance we get.

love to see the api get used. but as its not ready (guess?) this should then be delayed. what would you be selling, if its not ready.

Tg, is a horror show. every time we reopen it… team(s) use it for a few months, then stop.
we seem to use more select groups made for direct convesations.

(i do think we should do some announcements there, but opening it up doesnt seem to matter much, other than the scammer numbers might go up. (they still contact me there too lol)

2 Likes
4

if ‘Leadership’ position isnt desired. (which i totally get!!)

could be setup as a ‘BD group’ instead of a WS.

I dont know if merging into eng at all is a good thing.

They should concentrate on building/fixing.

(i think we do need a marketing thing, that would work with bd) but.. i think that will be time before we can get back to that.

3 Likes
5

Thanks @PTT and @Giantkin for the feedback, really appreciate it.
@Giantkin, on each of your points:
On partnership visibility: selling a product that requires an integration on the partner’s side takes time. Projects often have to put together internal proposals and run their own votes before they can move. Concretely, here’s where things stand.

API/Widget integrations validated:
– Brila (brila.finance / elara.fi)
– Pait.fi (pait.fi)
Pending validation or pushed to a later date:
– Yieldnest (yieldnest.finance)
– Meta Pool (metapool.app)
– Scallop (scallop.io)
– Swap.cofee (swap.coffee)
Chains:
– Full co-marketing done with Katana (blog article + Twitter co-marketing)
– In progress: MegaEth, Bob
– Pending validation: Ton, starknet, Monad, Tron, Sui

This whole process of building relationships with chains, getting listed, and talking to potential partners is slow by nature, but in my view it’s necessary for ShapeShift’s evolution.

@Giantkin, happy to share the tool I built for outreach and follow-up tracking if you want to take a look at the pipeline in detail.

On the API not being ready: you’re right that closing API deals at scale depends on the product being polished. The reason for parallel work is to build the pipeline now so we’re not starting from zero the day it ships.

Beyond outreach, I can also bring solutions and open targeted PRs to improve the partner portal, drawing on my analysis of other projects.
On Telegram: I actually think this one is important. The moment we start rotating B2B contacts, people we’ve reached out to arrive on a closed Telegram.
That’s a real blocker, both for our image and for ShapeShift’s growth. I get that previous attempts have stalled, but with active inbound from partners, leaving it closed costs us.

On merging into Engineering vs a BD group: after discussing it with FBL and Apo, merging into Engineering felt like the logical move. Most of my work touches Kev’s roadmap directly (API/Widget, competitive PRs), and Engineering is who I’ll be in direct contact with anyway, whether for product evolution or for partner and chain outreach.

@PTT, from where I stand, the numbers are justified. Handling outreach, marketing, lite product work, and putting together targeted PRs based on my research takes a real amount of time and requires full-time commitment.

To be honest, I’m not counting my hours on this. I’m fully open to discussing the numbers, do you have something specific in mind ? Full FOX ?

1 Like
6

Thanks for the proposal @discostu! As we discussed in DM, I think the energy and work you’ve put into outreach (partners and B2B) are valuable for the DAO and likely to pay off in the mid-to-long term. I’d like to see that continue, and I support this proposal.

I’ve previously mentioned that I would have been comfortable adding one more engineer during the Engineering WS renewal given my vision for the coming months, even if it shortens the runway. That said, for this hybrid role, I agree the compensation should reflect the DAO’s current austerity phase.

I won’t suggest specific numbers here since we already discussed some ranges in private, but I encourage those who see compensation as a blocker to share concrete thresholds (publicly or privately). And if some don’t see this role as a priority in the current context, that’s also a fair position to express clearly.

1 Like
7

I chated in a dm, mentioned why i was against spend right now.

(and helped set the correct scp number in forum post)

2 Likes
8

Thanks so much for all your feedback in DMs.
As Giant asked, I’ve created the revised proposal here, I’ve drastically lowered my ask and switched to full FOX:

1 Like
9

Hey @discostu, I think your offer is more in-line with the DAO’s budget, but the Ideation vote is 7 days minimum so I think you should start it over with at least the minimum duration, see the FOX Governance Process

2 Likes
10

Def delete that one, and redo.

7days. (i usually add an hour after i start, as i have to delete my own at least once or twice lolol

1 Like
11

I’am sorry, thanks @Fireb0mb1 @Giantkin
This one is the way !

1 Like
12

Full send support for @discostu here as he is the only person in the DAO who is actively trying to generate revenue.

Current cynicism is this communities classic pattern of not spending, only to turn around and realize that encouraging good people is the only way to grow.

This morning i engaged our P0 customer, Stu has 4 more promising deals in the chamber, actively follows up, and has a developer brother helping to refine some of our resourcing around the API with landing pages etc.

Anyone against this, ignore my thoughts if you need, just objectively look at the new energy in the DAO and see it as a the next chapter of contributors who are motivated to try and grow our way out of the current trajectory.

3 Likes
13

@Giantkin

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

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.

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.

image
image1560×1214 165 KB

Budget spreadsheet: SCP-215-budget - Google Sheets

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.
  • AGAINST: No thank you!
1 Like