Stellar Speedrun Platform

Open-source, gamified onboarding that takes Rust developers from zero to a production-deployed Soroban contract in under 8 hours.

Track: Open Round: SCF #44 Deadline: Jun 14, 2026 Ask: $95,000 USD in XLM Duration: 22 weeks

⚠ Pre-submission gap analysis — read this first

This is the same project that received a prior-round rejection citing "concept and design stage with no prototype or active development." The proposal below is written as strongly as possible, but submitting as-is will likely receive the same rejection unless the items below are closed first.

Required before pressing submit:

Sections 1. One-liner 2. Track 3. Why Stellar 4. Problem 5. Solution 6. Traction 7. Architecture 8. Milestones 9. Budget 10. Team 11. Risks 12. Open source 13. Why now 14. Prior feedback SCF form mapping

§1Project name & one-liner

Stellar Speedrun Platform — an open-source, gamified onboarding platform that takes Rust developers from zero to production-deployed Soroban smart contracts in under 8 hours, modeled on Speedrun Ethereum but built natively for Stellar.

§2Track justification — Open

This is a novel developer-tooling primitive. Stellar has Stellar Quest for protocol fundamentals and Soroban Docs for reference, but no end-to-end project-based learning platform that walks a developer through deploying production-style contracts (NFT, AMM, multi-sig, etc.) the way Speedrun Ethereum does for the EVM. This is an Open-track build because it creates a new resource, not an integration of an existing one.

§3Why Stellar / Soroban (not chain-agnostic)

Three Stellar-specific reasons this can only work here:

  1. Soroban is new. The Stellar developer base has grown materially since Soroban mainnet, but most onboarding content still teaches Stellar Classic / Horizon. There is no "Speedrun"-style platform for the Soroban era. Speedrun Ethereum took years to build out its current curriculum — Stellar can compress that with a focused build today and capture the next wave of devs entering the ecosystem.
  2. Built-in faucet + low cost. Stellar's testnet faucet and sub-cent transaction fees mean a learner can run a full challenge end-to-end without funding friction. The same flow on Ethereum L1 requires us to provide gas reimbursement; on most L2s we hit RPC rate limits during workshops. Stellar makes the teaching itself cheaper to operate.
  3. XLM rewards are practical. Distributing $0.50–$2 in XLM for completed challenges is feasible because of the low fee structure. The same model on Ethereum costs more in gas than the reward. This unlocks a gamification mechanic other ecosystems can't sustainably copy.

§4Problem (with evidence)

Soroban developer onboarding has a documented friction problem. Three concrete data points:

The cost of this friction: Stellar loses developers to chains with smoother onboarding. Solving it directly grows the active builder base — the bottleneck for everything else SCF is trying to fund.

§5Solution

A learn-by-deploying platform with five core pieces:

  1. Preconfigured dev environment. A single git clone && cd && make setup reproducibly installs Rust, soroban-cli, node, and configures testnet. Tested on macOS, Linux, and WSL2.
  2. Six gamified challenges, ordered by difficulty:
    • NFT Minting (week 1) — the warm-up. Deploy a Soroban NFT contract, mint from a frontend, see the token in Freighter.
    • Token Vending Machine — accept XLM, dispense a custom token. Teaches contract-to-account flows.
    • Multi-Sig Wallet — Stellar's native multisig wrapped in a learner-friendly contract.
    • Decentralized Staking — time-locked rewards. Teaches state and time logic.
    • On-chain Voting — challenge with verifiable outcomes.
    • Optional bonus: ZK demo using Soroban's emerging crypto primitives.
  3. Frontend scaffolds built on soroban-react + Freighter wallet, so each challenge ships with a working dApp UI the learner extends.
  4. On-chain verification. Each challenge has an automated checker that confirms the learner's deployed contract meets the spec (correct events emitted, correct state transitions). Verification happens on testnet — no manual review.
  5. Leaderboard + XLM micro-rewards. Public leaderboard ranks completions; passing each challenge auto-distributes a small XLM reward (5–20 XLM tier) from a community pool. Gamifies progress and recirculates XLM through the ecosystem.

All code MIT/Apache-licensed in the public stellar-speedrun GitHub org. Try the interactive demo →

§6Current traction

Fill in honestly with what's actually shipped by submission day — DO NOT inflate. Reviewers cross-check.

§7Technical architecture

┌────────────────────────────────────────────────────┐
│  GitHub: stellar-speedrun/                          │
│  ├─ challenges/                                     │
│  │  ├─ 01-nft-mint/        (Soroban contract + UI) │
│  │  ├─ 02-token-vending/                            │
│  │  └─ ...                                          │
│  ├─ scaffold/              (shared dev env)         │
│  │  ├─ soroban-cli setup                            │
│  │  ├─ Rust toolchain pin                           │
│  │  └─ docker-compose for verifier                  │
│  └─ platform/              (web app)                │
│     ├─ Next.js + soroban-react                      │
│     ├─ Freighter wallet connector                   │
│     └─ Leaderboard (Cloudflare D1 / Workers)        │
└────────────────────────────────────────────────────┘
                     ↓ deploys to
┌────────────────────────────────────────────────────┐
│  Stellar Testnet                                    │
│  ├─ Per-learner challenge contracts                 │
│  ├─ Reward distribution contract (community pool)   │
│  └─ Verifier reads contract state via RPC           │
└────────────────────────────────────────────────────┘

Stack

§8Milestones & deliverables

Total ask: $95,000 USD in XLM — paid in 4 tranches (10% / 20% / 30% / 40%).

M1 — Foundation & Proof of Intent

$9,500 (10%)
Due 3 weeks after award

M2 — Three challenges + platform skeleton

$19,000 (20%)
Due 8 weeks after award

M3 — Full curriculum + leaderboard

$28,500 (30%)
Due 16 weeks after award

M4 — Mainnet-ready + adoption

$38,000 (40%)
Due 22 weeks after award

§9Budget breakdown

We're asking $95,000 (not the $150K cap) to right-size to deliverables and leave room for follow-on funding once we have shipped traction.

Category Hours Rate Cost
Soroban contract development (6 challenges × ~30h)180$80$14,400
Frontend / soroban-react integration320$65$20,800
Verifier infrastructure (Workers + D1)80$70$5,600
Tutorial writing + technical content160$60$9,600
External Rust contractor (advanced challenge + audit)100$90$9,000
Project lead / DevRel / community240$60$14,400
Design + UI assets60$55$3,300
External alpha testing incentives (10 × $100)$1,000
Reward pool seed (XLM for first 250 learners)$7,500
Domain, infra, third-party tools$1,400
Buffer for contingency (~10%)$8,000
Total$95,000

Total dev hours = ~1,140 across 22 weeks for a 2-person core team plus contracted Rust engineer. Reasonable, not aggressive.

§10Team

Harry Phan Project Lead & Developer Advocate

Tung Lee Full-Stack Developer

Soroban / Rust contractor to be engaged on award

What we're explicitly not doing: taking on infrastructure beyond our scope. The platform runs on Cloudflare's free / low-cost tier; we are not building our own RPC layer, indexer, or wallet — we are using Stellar's primitives and existing tooling as designed.

§11Risks & mitigations

RiskMitigation
Soroban-react / SDK breaking changesPin SDK versions per challenge. Each challenge has its own lockfile so older challenges keep working as SDKs evolve.
Sybil attack on XLM rewardsCap rewards at low value (5–20 XLM); require unique testnet addresses with non-trivial setup; manual review on top leaderboard slots.
Maintenance burden post-grantBuild with contribution-friendliness from M1 (clear CONTRIBUTING.md, modular challenge format). Plan handoff conversation with SDF / Stellar Foundation in M4.
Contractor availabilityBackup candidates identified. If primary unavailable, narrow M4 scope rather than miss the milestone.
Demand validationWaitlist running before submission, not after. If signups stall below 50 at M2, pivot challenge ordering toward what waitlist users said they wanted.

§12Open-source commitment

§13Why now

Stellar is in the middle of a Soroban developer onboarding wave. SCF 7.0 explicitly calls out execution-ready teams that grow the ecosystem. Speedrun Ethereum took the EVM ecosystem from "you should learn Solidity" to "complete this 6-week speedrun and you're ship-ready" — and there's no equivalent on Stellar. This is a 6-month build that compounds as more developers pass through; if it ships in 2026, every Stellar hackathon after H2 2026 has a structured prep path.

§14Acknowledging prior feedback

A previous version of this concept was reviewed in an earlier SCF round and received feedback that the project was at concept stage without a working prototype. That feedback was correct, and it's the reason this submission includes [working NFT mint contract on testnet / live frontend / waitlist of N / GitHub commits over the past N weeks]. The concept hasn't changed — but the project now ships code. We'd appreciate the panel comparing this submission against the prior one as evidence of execution.

Suggested SCF form section mapping

Form fieldThis page
Project Name§1
Tagline / Short description§1
Track (Open / Integration / RFP)§2
Why Stellar§3
Problem§4
Solution§5
Current Status / Traction§6
Technical Approach§7
Milestones§8
Budget§9
Team§10
Risks§11
Licensing / Open source§12
Referral code(paste at top of form)

Good luck. Ship the M1 artifacts first, then this writeup will land very differently.