Browse documentation
WORKINGv2.0

Who Participates

Designers, Launchers, Players, Traders, LPs, Runtime Providers, Verifiers, and Spawn.

Updated 2026-09-23 · Canonical at www.spawnfarm.com · Status labels describe evidence, not marketing readiness

Designer

Creates reusable Blueprints/engines. Entry cost can be low: time, expertise, development compute, and data work. A Designer may build for curiosity, for their own future World, for reputation, or to earn royalties if Launchers use the Blueprint.

Economic opportunity: Blueprint usage royalties and possibly eligible descendant fee share.
Primary risk: development time with no adoption.
Primary quality axis: usefulness, fidelity, verifiability, compute efficiency, documentation.

Launcher

Creates a World from a Blueprint or a custom engine. Funds the disclosed creation requirement and initial runtime; funds initial liquidity only when the World uses a transferable token. Configures the World within the Blueprint's permitted surface and builds the product/community.

Economic opportunity: optional World Token exposure, disclosed World action/usage fees, potential eligible trading-fee share, premium World services.
Primary risk: launch costs and ongoing operating costs with insufficient usage.

Player

Uses a named World Token to perform in-World actions only when the World has one. In a future eligible competitive template, a Player may additionally lock $SPAWN as collateral under verified vault and settlement rules.

Economic opportunity: $SPAWN settlement from pooled participant capital and/or prefunded prize reserves.
Primary risk: local-token action cost plus some/all competitive capital.

Trader

Buys/sells World Token assets based on adoption, narrative, usage, liquidity, or speculation. Does not need to understand or play the simulation.

Economic opportunity/risk: market price movement.

Liquidity Provider

Provides market liquidity for World Token markets and receives venue/AMM economics subject to the actual market implementation.

Runtime Provider

Supplies CPU/GPU/memory/storage execution. v1 begins with Spawn-managed or approved infrastructure; long-term providers compete for jobs.

Critical boundary: runtime provider computes candidate state; it does not control player funds.

Verifier

Independently recomputes or checks state transitions and attests to checkpoint correctness. May be bonded and rewarded from verification budgets.

Spawn / Spawn Labs

Provides protocol infrastructure, standards, launch flow, registry, economic rails, verification/finality rules, Model Store, user interfaces, and early runtime orchestration. Spawn Labs may additionally help build custom models and Worlds.