What Is Spawn
The complete product overview, participant roles, and current platform status.
Spawn is a marketplace and launch system for simulations. Designers publish reusable Models. Launchers turn those Models into configured Worlds. Players, researchers, students, communities, and businesses use those Worlds to explore outcomes.
Spawn supports real and imagined systems. The same infrastructure could support a hurricane model, a sports simulator, a war game, an economic laboratory, a marble race, or a persistent fictional universe.
Core objects
Model
A Model is the simulation logic: state, rules, inputs, outputs, and update process.
Blueprint
A Blueprint is a versioned Model package that has enough documentation, tests, provenance, and runtime information to be evaluated for launch.
World
A World is a configured deployment of a Blueprint. It has a specific identity, parameters, interface, runtime plan, and economic policy.
Season
A Season is a bounded run or competition inside a World. A World can have one Season, many Seasons, or no Seasons at all.
Position
A Position records a participant's entry, actions, rights, or capital at risk in a Season. The exact meaning depends on the World.
Who participates
Designers
Designers turn expertise or imagination into reusable Blueprints. They define the system, document its sources and assumptions, establish its configuration limits, and provide the tests required to evaluate it.
If a Blueprint is accepted into the Model Store, its Designer can earn disclosed royalties or usage fees when Launchers build eligible Worlds from it. Publishing a Blueprint does not guarantee adoption or income.
Launchers
Launchers build products and communities from Blueprints. They select or commission a Model, configure a World, fund its initial runtime, build its interface, and operate the experience.
Launchers can earn through disclosed World fees, premium services, token exposure, sponsorships, licensing, or other permitted business models. They also carry launch costs and continuing operating risk.
Players
Players use Worlds. They may compete, experiment, learn, forecast, trade, create, or simply observe. In competitive Worlds, a Player may put $SPAWN or another disclosed asset at risk under rules fixed before the Season begins.
Winning is never guaranteed. Simulation results, strategy, market prices, and technical failures can all cause loss.
Runtime providers and verifiers
Runtime providers supply the CPU, GPU, memory, storage, and network resources needed to execute Worlds. Verifiers independently replay or check results when the World requires verification.
The runtime computes candidate results. It must not directly control participant funds.
Community members
Community members can propose ideas, review Models, test Worlds, contribute code or research, and help decide what Spawn builds next.
The three asset roles
Spawn separates local utility, shared capital, and compute funding.
| Asset | Primary role |
|---|---|
| World Token | Optional, named utility asset for defined actions inside one World |
$SPAWN | Existing token; proposed near-term roles are World creation and optional eligible collateral |
| $ETH | Blockchain gas and runtime funding |
A World does not need to use every asset. Its economic design must state which assets it uses and why.
Spawn Labs
Spawn Labs is the development layer for Designers and Launchers.
For Designers, it helps turn a rough idea into a structured Model: research plan, state definition, transition rules, inputs, data sources, tests, benchmarks, and documentation.
For Launchers, it helps configure a World, build its interface, estimate runtime cost, prepare contracts, create visualizations, and test the complete experience before launch.
AI can assist with this work. It cannot establish scientific validity, remove economic risk, or replace independent review.
Current status
LIVE: $SPAWN exists on Robinhood Chain and was launched through Pons.
IN DEVELOPMENT / NEEDS PROOF: the Model Store, Launchpad, Spawn Labs workflows, World contracts, runtime funding, verification, and settlement architecture.
CONCEPTUAL: open runtime-provider markets, bonded verification, ZK validity systems, complex Blueprint composition, and cross-World economic features.
Until production contracts are deployed and verified, the website describes the Launchpad and related protocol components as planned infrastructure rather than live functionality.