Spawn
Join the waitlist →
Browse documentation
START HEREWhat is Spawn?60-Second ExplanationHow Spawn WorksKey TermsWho Participates
PRODUCTModels & BlueprintsWorldsSeasonsPositionsModel StoreLauncher Configuration
ECONOMICSThree-Asset Architecture$SPAWNOptional World TokensLaunch EconomicsPlayer EconomicsEconomic LineageFeesLiquidity
RUNTIMERuntime OverviewCompute ProfilesRuntime CostRuntime BatteryRuntime DepletionRuntime ProvidersLarge Data
VERIFICATIONDeterministic ExecutionCheckpointsVerification ClassesVerification & ReplayFinality & SettlementData AvailabilityRandomnessVaults & SettlementThreat ModelProtocol Invariants
BUILD ON SPAWNBuild a ModelModel SpecificationBlueprint StatusSpawn LabsLaunch a WorldWorld Creation FlowWorld ConfigurationOptional Token Design
REFERENCEOfficial $SPAWNProtocol StatusTrust ModelContractsChain CompatibilityFormula ReferenceGlossaryRiskFAQ
Docs / REFERENCE / Contracts
WORKINGv2.0

Contracts

Original token and proposed pons integration components.

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

Canonical protocol token

$SPAWN: 0x41080c9d7908CE567eFe239042c49D8159a2A3bb on Robinhood Chain.

Proposed roles

  • LaunchRouter: model/quote validation, token retirement, pons launch, splitter, runtime deposit and World registration in one transaction.
  • FeeSplitter: creator proceeds split 2/7 to Spawn and 5/7 to creator wallets.
  • RuntimeEscrow: separate per-World ETH funding and authorized service payments.
  • WorldRegistry: pinned model/configuration, token identity and execution commitments.
  • pons: token factory, trading and liquidity-lock machinery for the selected deployed version.

No unverified production address is invented here. Exact factory version, contract-call permissions, creator rights, required ETH, initial buy, fee recipient controls, payout assets and the original token's burn interface require deployment verification. See World Creation Flow.