SCP-217 (Amendment): Engineering Workstream Contributor Addition, June 1

Source Information

URL: https://snapshot.org/#/s:shapeshiftdao.eth/proposal/0xc8c9aa7f04cf1f28821cacc4b3f41306af462e0a88ce062da12c092e7cb3fc96

Fetched at: 18.06.2026, 05:17:08

Source type: snapshot

Extracted Data

SCP-217 (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 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.
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.

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: Do not add discostu to the Engineering Workstream.

Voting Options

For
Against

Metadata

{
  "proposal_id": "0xc8c9aa7f04cf1f28821cacc4b3f41306af462e0a88ce062da12c092e7cb3fc96",
  "space_id": "shapeshiftdao.eth",
  "space_name": "ShapeShift",
  "author": "0xff75E131c711e4310C045317779d39B3B4f718C4",
  "start": 1781208000,
  "end": 1781640000,
  "state": "closed",
  "type": "basic",
  "quorum": 4000000
}

Analysis

Summary

This proposal adds discostu as a fractional contributor to the Engineering Workstream for 4 months (June 1–September 30, 2026) at $5,800/month in 100% FOX ($23,200 total). The role absorbs BD, partner-facing product, marketing/comms, and targeted engineering work previously under the discontinued Product Lite Workstream (SCP-210). It also increases Apotheosis's hours from 6 to 8/week (adding ~$895/month USDC) to support coordination.

Key Changes

Add discostu as a fractional contributor to the Engineering Workstream for June 1–September 30, 2026
Compensate discostu at $5,800/month in 100% FOX (no USDC), totaling $23,200 over 4 months
Increase Apotheosis's weekly hours from 6 to 8 under SCP-212, raising monthly USDC compensation from $2,688 to $3,583
Transfer discostu's BD, partner-facing product, marketing/comms, and targeted engineering scope from the discontinued Product Lite Workstream (SCP-210) into Engineering

⚠️ Risks

Scope breadth: discostu's responsibilities span five domains (BD, chain relations, product, engineering contribution, operations), which may reduce execution quality across any single domain
KPI escape hatch: the proposal states 'Closes are subject to the API/Widget reaching a polished, sellable state,' meaning the primary BD output metric is contingent on engineering deliverables outside discostu's control, reducing accountability
Additional USDC burn: Apotheosis's hours increase adds approximately $3,580 USDC over 4 months, which partially offsets the 'zero USDC burn' framing of the proposal
FOX price volatility: $5,800/month denominated in FOX means actual token quantity varies with market price; if FOX appreciates significantly, the DAO issues more value than budgeted
Single point of failure for partner relationships: discostu owns all active partner integrations and chain relations; if he underperforms or leaves, continuity for partners (Katana, MegaEth, Starknet, BOB, in-flight API customers) is disrupted

⚠️ Benefits

Zero USDC burn for discostu's compensation: 100% FOX preserves DAO USDC runway during austerity
FOX compensation aligns contributor incentives with DAO token value
Consolidates BD/marketing scope under one workstream rather than requiring a separate governance proposal, reducing governance overhead
Maintains continuity of active partner relationships (Katana, MegaEth, Starknet, BOB, in-flight API customers) that would otherwise be disrupted by the SCP-210 non-renewal
Co-locating discostu with the Engineering team simplifies coordination on API/Widget technical integration and partner onboarding
Frees Kev to focus on technical readiness while discostu handles BD and partner-facing work
Landing page redesign has a concrete, measurable KPI: ship it during the 4-month period

❓ Unknown Factors

Unclear: the proposal describes discostu as a 'fractional contributor' but never specifies hours per week or full-time equivalent percentage
Unclear: the total Engineering Workstream budget before and after this amendment is not provided, making it impossible to assess proportional budget impact
Unclear: what happens after September 30, 2026 — whether a renewal proposal is expected or partner relationships will be handed off
Unclear: the expected revenue impact from API/Widget BD pipeline is not quantified, so ROI on the $23,200 + $3,580 spend cannot be assessed
Unclear: whether the $5,800/month FOX rate is fixed at a specific FOX price or calculated dynamically, affecting actual token issuance

Evidence Quotes

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

Closes are subject to the API/Widget reaching a polished, sellable state.

Secure ShapeShift listings on 80%+ of newly integrated chains

Ship the API / Widget landing page redesign during the period

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.

FBL did not renew the Product Lite Workstream (SCP-210). Discostu's existing BD scope under that workstream needs a new home.

4-month total: $23,200

Recommendation

Suggested option: For

Confidence level: low

Reasoning

The proposal preserves DAO USDC runway by compensating discostu entirely in FOX, which aligns with high treasury risk sensitivity. It provides continuity for active partner relationships and avoids governance overhead by consolidating under an existing workstream. However, confidence is low because the 'fractional' commitment is never quantified in hours, the primary BD KPI is explicitly contingent on external engineering deliverables, the additional USDC cost for Apotheosis partially undermines the 'zero USDC burn' claim, and no revenue projections are provided to assess ROI. Given the user's preference for strict specification, these gaps are material but not disqualifying since the scope is bounded in time (4 months) and budget ($23,200 FOX + $3,580 USDC).

⚠️ Conflicts with user principles

needs_strict_spec: the proposal uses 'fractional contributor' without specifying hours per week or FTE percentage, conflicting with the requirement for strict specification
treasury_risk_sensitivity: the additional $3,580 USDC for Apotheosis is a secondary budget impact not reflected in the headline 'zero USDC burn' framing, creating incomplete treasury visibility

Multi-Agent Council

Workflow: research_agent → risk_analysis_agent → decision_agent → verification_agent

Agent count: 4

Facts collected

{"key":"title","value":"SCP-217 (Amendment): Engineering Workstream Contributor Addition, June 1 – September 30, 2026","source":"proposal.title"}
{"key":"amount","value":"5,800","source":"proposal/report text"}
{"key":"voting_options","value":["For","Against"],"source":"proposal.options"}

Risk summary

Council decision

Suggested option: For

Confidence level: low

No high-severity blocker was found by the deterministic council, so the council preserves the primary report recommendation and confidence.

Council verification

Status: verified

research facts are stored in shared memory
risk agent reads research facts before decision
decision blockers include high-severity risks
verification hash covers facts risks and decision

Embedded deterministic multi-agent review over the primary governance report. Pageserver can display this alongside the model analysis.

⚠️ Limitations and Warnings

This is not legal or financial advice.
The tool may have failed to extract all proposal parameters.
Critical parameters must be checked manually.

Verification

Verified: Yes

Merkle root: e7cd022bdbc50d680e35c721b13c02623fac679d06f7a2f59c182604f3b889bd

Request ID: fbde8ddf725d466d84f91bb8738f15d5

Verification Boundary

Deterministic (verifiable)

analysis.summary
analysis.key_changes[0]
analysis.key_changes[1]
analysis.key_changes[2]
analysis.key_changes[3]

Interpretive (requires review)

analysis.risks[0] (interpretive) "Scope breadth: discostu's responsibilities span five domains (BD, chain relations, product, engineer..."
analysis.risks[1] (interpretive) "KPI escape hatch: the proposal states 'Closes are subject to the API/Widget reaching a polished, sel..."
analysis.risks[2] (interpretive) "Additional USDC burn: Apotheosis's hours increase adds approximately $3,580 USDC over 4 months, whic..."
analysis.risks[3] (interpretive) "FOX price volatility: $5,800/month denominated in FOX means actual token quantity varies with market..."
analysis.risks[4] (interpretive) "Single point of failure for partner relationships: discostu owns all active partner integrations and..."
analysis.benefits[0] (interpretive) "Zero USDC burn for discostu's compensation: 100% FOX preserves DAO USDC runway during austerity..."
analysis.benefits[1] (interpretive) "FOX compensation aligns contributor incentives with DAO token value..."
analysis.benefits[2] (interpretive) "Consolidates BD/marketing scope under one workstream rather than requiring a separate governance pro..."
analysis.benefits[3] (interpretive) "Maintains continuity of active partner relationships (Katana, MegaEth, Starknet, BOB, in-flight API ..."
analysis.benefits[4] (interpretive) "Co-locating discostu with the Engineering team simplifies coordination on API/Widget technical integ..."
analysis.benefits[5] (interpretive) "Frees Kev to focus on technical readiness while discostu handles BD and partner-facing work..."
analysis.benefits[6] (interpretive) "Landing page redesign has a concrete, measurable KPI: ship it during the 4-month period..."
analysis.unknowns[0] (uncertainty) "Unclear: the proposal describes discostu as a 'fractional contributor' but never specifies hours per..."
analysis.unknowns[1] (uncertainty) "Unclear: the total Engineering Workstream budget before and after this amendment is not provided, ma..."
analysis.unknowns[2] (uncertainty) "Unclear: what happens after September 30, 2026 — whether a renewal proposal is expected or partner r..."
analysis.unknowns[3] (uncertainty) "Unclear: the expected revenue impact from API/Widget BD pipeline is not quantified, so ROI on the $2..."
analysis.unknowns[4] (uncertainty) "Unclear: whether the $5,800/month FOX rate is fixed at a specific FOX price or calculated dynamicall..."
recommendation.reasoning (interpretive) "The proposal preserves DAO USDC runway by compensating discostu entirely in FOX, which aligns with h..."
recommendation.conflicts_with_user_principles[0] (interpretive) "needs_strict_spec: the proposal uses 'fractional contributor' without specifying hours per week or F..."
recommendation.conflicts_with_user_principles[1] (interpretive) "treasury_risk_sensitivity: the additional $3,580 USDC for Apotheosis is a secondary budget impact no..."

Uncertainty Flags

unknowns:Unclear: the proposal describes discostu as a 'f...
unknowns:Unclear: the total Engineering Workstream budget...
unknowns:Unclear: what happens after September 30, 2026 —...
unknowns:Unclear: the expected revenue impact from API/Wi...
unknowns:Unclear: whether the $5,800/month FOX rate is fi...
confidence:low

Method

Kind: heuristic

Version: 2

Deterministic layer is based on direct matching to extracted fields and evidence_quotes, plus presence of hard literals (numbers, addresses, option strings).
Interpretive layer includes summary, risks, benefits, and recommendation reasoning.
This is a boundary labeling aid, not a proof of truth.

Week 9 - Verification Hooks

Mixed categories detected: false

Requires separation: false

Strict mode: false

Strict rejection triggered: false

Routing action: WARN

Segments

analysis.summary deterministic
This proposal adds discostu as a fractional contributor to the Engineering Workstream for 4 months (June 1–September 30, 2026) at $5,800/month in 100% FOX ($23,200 total).
Reasons: contains_hard_literal
analysis.summary deterministic
The role absorbs BD, partner-facing product, marketing/comms, and targeted engineering work previously under the discontinued Product Lite Workstream (SCP-210).
Reasons: contains_hard_literal
analysis.summary deterministic
It also increases Apotheosis's hours from 6 to 8/week (adding ~$895/month USDC) to support coordination.
Reasons: contains_hard_literal
analysis.key_changes[0] deterministic
Add discostu as a fractional contributor to the Engineering Workstream for June 1–September 30, 2026
Reasons: contains_hard_literal
analysis.key_changes[1] deterministic
Compensate discostu at $5,800/month in 100% FOX (no USDC), totaling $23,200 over 4 months
Reasons: contains_hard_literal
analysis.key_changes[2] deterministic
Increase Apotheosis's weekly hours from 6 to 8 under SCP-212, raising monthly USDC compensation from $2,688 to $3,583
Reasons: contains_hard_literal
analysis.key_changes[3] deterministic
Transfer discostu's BD, partner-facing product, marketing/comms, and targeted engineering scope from the discontinued Product Lite Workstream (SCP-210) into Engineering
Reasons: contains_hard_literal
analysis.risks[0] probabilistic
Scope breadth: discostu's responsibilities span five domains (BD, chain relations, product, engineering contribution, operations), which may reduce execution quality across any single domain
Reasons: contains_inference_language interpretive_field
analysis.risks[1] probabilistic
KPI escape hatch: the proposal states 'Closes are subject to the API/Widget reaching a polished, sellable state,' meaning the primary BD output metric is contingent on engineering deliverables outside discostu's control, reducing accountability
Reasons: interpretive_field
analysis.risks[2] probabilistic
Additional USDC burn: Apotheosis's hours increase adds approximately $3,580 USDC over 4 months, which partially offsets the 'zero USDC burn' framing of the proposal
Reasons: contains_hard_literal interpretive_field
analysis.risks[3] probabilistic
FOX price volatility: $5,800/month denominated in FOX means actual token quantity varies with market price
Reasons: contains_hard_literal interpretive_field
analysis.risks[3] probabilistic
if FOX appreciates significantly, the DAO issues more value than budgeted
Reasons: interpretive_field
analysis.risks[4] probabilistic
Single point of failure for partner relationships: discostu owns all active partner integrations and chain relations
Reasons: interpretive_field
analysis.risks[4] probabilistic
if he underperforms or leaves, continuity for partners (Katana, MegaEth, Starknet, BOB, in-flight API customers) is disrupted
Reasons: interpretive_field
analysis.benefits[0] probabilistic
Zero USDC burn for discostu's compensation: 100% FOX preserves DAO USDC runway during austerity
Reasons: contains_hard_literal interpretive_field
analysis.benefits[1] probabilistic
FOX compensation aligns contributor incentives with DAO token value
Reasons: interpretive_field
analysis.benefits[2] probabilistic
Consolidates BD/marketing scope under one workstream rather than requiring a separate governance proposal, reducing governance overhead
Reasons: interpretive_field
analysis.benefits[3] probabilistic
Maintains continuity of active partner relationships (Katana, MegaEth, Starknet, BOB, in-flight API customers) that would otherwise be disrupted by the SCP-210 non-renewal
Reasons: contains_hard_literal interpretive_field
analysis.benefits[4] probabilistic
Co-locating discostu with the Engineering team simplifies coordination on API/Widget technical integration and partner onboarding
Reasons: interpretive_field
analysis.benefits[5] probabilistic
Frees Kev to focus on technical readiness while discostu handles BD and partner-facing work
Reasons: interpretive_field
analysis.benefits[6] probabilistic
Landing page redesign has a concrete, measurable KPI: ship it during the 4-month period
Reasons: contains_hard_literal interpretive_field
analysis.unknowns[0] unverifiable
Unclear: the proposal describes discostu as a 'fractional contributor' but never specifies hours per week or full-time equivalent percentage
Reasons: uncertainty_language unknown_field_requires_external_evidence
analysis.unknowns[1] unverifiable
Unclear: the total Engineering Workstream budget before and after this amendment is not provided, making it impossible to assess proportional budget impact
Reasons: uncertainty_language unknown_field_requires_external_evidence
analysis.unknowns[2] unverifiable
Unclear: what happens after September 30, 2026 — whether a renewal proposal is expected or partner relationships will be handed off
Reasons: contains_hard_literal uncertainty_language unknown_field_requires_external_evidence
analysis.unknowns[3] unverifiable
Unclear: the expected revenue impact from API/Widget BD pipeline is not quantified, so ROI on the $23,200 + $3,580 spend cannot be assessed
Reasons: contains_hard_literal uncertainty_language unknown_field_requires_external_evidence
analysis.unknowns[4] unverifiable
Unclear: whether the $5,800/month FOX rate is fixed at a specific FOX price or calculated dynamically, affecting actual token issuance
Reasons: contains_hard_literal uncertainty_language unknown_field_requires_external_evidence
recommendation.reasoning probabilistic
The proposal preserves DAO USDC runway by compensating discostu entirely in FOX, which aligns with high treasury risk sensitivity.
Reasons: contains_inference_language interpretive_field
recommendation.reasoning probabilistic
It provides continuity for active partner relationships and avoids governance overhead by consolidating under an existing workstream.
Reasons: interpretive_field
recommendation.reasoning probabilistic
However, confidence is low because the 'fractional' commitment is never quantified in hours, the primary BD KPI is explicitly contingent on external engineering deliverables, the additional USDC cost for Apotheosis partially undermines the 'zero USDC burn' claim, and no revenue projections are provided to assess ROI.
Reasons: contains_inference_language interpretive_field
recommendation.reasoning probabilistic
Given the user's preference for strict specification, these gaps are material but not disqualifying since the scope is bounded in time (4 months) and budget ($23,200 FOX + $3,580 USDC).
Reasons: contains_hard_literal interpretive_field
recommendation.conflicts_with_user_principles[0] probabilistic
needs_strict_spec: the proposal uses 'fractional contributor' without specifying hours per week or FTE percentage, conflicting with the requirement for strict specification
Reasons: interpretive_field
recommendation.conflicts_with_user_principles[1] probabilistic
treasury_risk_sensitivity: the additional $3,580 USDC for Apotheosis is a secondary budget impact not reflected in the headline 'zero USDC burn' framing, creating incomplete treasury visibility
Reasons: contains_hard_literal interpretive_field

Method

Kind: heuristic

Version: 1

Deterministic segments are anchored to extracted title/body/options, evidence quotes, or hard literals.
Probabilistic segments include recommendation, risk, benefit, and uncertainty language.
Unverifiable segments are vague or unsupported without clear anchors.

Refusal Handling

Refusal Detected: No

Signals

confidence_low
unknowns_present:5

Routed To: HUMAN_REVIEW

Refusal detection is heuristic and conservative. Uncertainty can require human review without being labeled as a model refusal.

Prompt Used

Structured governance analysis prompt. Must output ONLY valid JSON. Must not guess missing options/results; use UNKNOWN.


You are given:

URL:
https://snapshot.org/#/s:shapeshiftdao.eth/proposal/0xc8c9aa7f04cf1f28821cacc4b3f41306af462e0a88ce062da12c092e7cb3fc96

EXTRACTED_DATA (may be incomplete):
{
  "source_type": "snapshot",
  "fetched_at": "2026-06-18T05:17:08.338Z",
  "title": "SCP-217 (Amendment): Engineering Workstream Contributor Addition, June 1 – September 30, 2026",
  "body": "Abstract\nThis proposal adds discostu as a fractional contributor to the Engineering Workstream for four months (June 1, 2026 th...

Model: ambient/large