How Spawn Works

The lifecycle from reusable Model to finalized economic outcome.

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

High-level flow

The diagram below is the target architecture, not a claim that every named registry, vault, or settlement module is deployed.

Designer
  ↓ publishes
Blueprint Registry / Model Store
  ↓ selected by
Launcher
  ↓ proposes/configures
World Registry + World Token + Liquidity + Runtime Battery
  ↓ opens
Season
  ↓ accepts
Player Positions
  ↓ local actions use World Token
  ↓ competitive capital enters SpawnUnitVault in $SPAWN
Runtime executes state transitions
  ↓
CheckpointRegistry receives commitments
  ↓
Verifier layer independently checks
  ↓
Finality layer marks result FINALIZED
  ↓
Settlement contract computes/accepts bounded allocation
  ↓
SpawnUnitVault exposes withdrawable $SPAWN claims

Parallel market path:

Trader / LP ↔ World Token market

Parallel infrastructure path:

RuntimeVault ($ETH) → Runtime Provider / keeper / verifier infrastructure

Security boundary

The simulation controls the World. The vault controls the money.

The simulation can determine state and a terminal result under declared rules. It cannot call arbitrary transfer functions on player principal.

For a LOCAL or RECORDED demo with no participant capital, the flow can stop before vault and settlement steps. Capital-bearing Seasons remain unavailable until the applicable contracts and controls are verified.