Understand exactly how Spawn works.
From Models and Worlds to runtime, token economics, verification, settlement, and the contracts underneath them.
What is live today?
Read the full status →$SPAWN is an existing Robinhood Chain token. The v2 platform is a public working specification under active development.
The Model Library, Launchpad, registries, vaults, replay client, and runtime system must not be treated as deployed until their addresses, code, controls, and required evidence are published.
Canonical website: www.spawnfarm.com. The legacy domain spawn.farm is not controlled by the current community-led team and may contain outdated or conflicting claims.
Protocol Status
View the evidence ledger →
The official $SPAWN token for the Spawn ecosystem.
The system in one line.
From a Model to a participant’s Position, Spawn defines a path for building testable simulations. The production system remains under development.
Start here.
New to Spawn? These are the most important documents to understand the protocol.
The big picture in plain English.
5 MIN READOptional World Tokens, $SPAWN, and $ETH.
8 MIN READHow it all fits together.
6 MIN READCompute, costs and providers.
8 MIN READFrom execution to settlement.
10 MIN READStep-by-step guide.
12 MIN READThree economic layers.
Different assets. Different roles. A more resilient system.
WORLD TOKEN = OPTIONAL UTILITY
- Used only when a World needs transferable utility
- Receives its own name and ticker
- Requires disclosed supply, sinks, and permissions
$SPAWN = PROPOSED NETWORK CAPITAL
- Near-term design: published World-creation gate
- Optional collateral only for approved, lawful Seasons
- No production utility exists without deployed contracts
$ETH = COMPUTE
- Funds runtime: compute, storage, data
- Pays verified runtime obligations
- Scales with measured compute needs
What we claim — and what we do not.
Transparency builds trust. Here’s how a simulation result moves from execution to settlement.
Status labels.
You’ll see these throughout the docs. They indicate the current state of each component.
Implemented, publicly identified, and tested to the stated Spawn standard.
Specified architecture that is not production-ready until its implementation and evidence are published.
Longer-term research direction; not part of the near-term product.
Current v2 language or product direction; documentation is not deployment evidence.