What is Spawn

Source: https://spawn.farm/docs

Spawn is a launchpad where anyone can be the scientist: write a small model that actually runs, launch it with its own token in one transaction, and let the pool that people trade and farm pay for it to keep stepping.

Whitepaper

The technical whitepaper is the full document: specification, model classes, escrow accounting, the hash chain, the challenge protocol, invariants, threat model, and references, with every section tagged as live, proposed, or not deployed.

The two halves

DeSci. The specification defines the state and step function; provenance separates sourced material from engineering choices; checkpoints let anyone replay the execution and challenge a mismatch.

DeFi. The token, trading pool, farming positions, and runtime escrow form the funding loop. Swaps produce both LP fees and the escrow share that pays for ticks.

The mechanic, in order

1. A creator writes a small model — a neural circuit from a published connectome, a reaction–diffusion field, an oscillator network — plus a concrete description of how it executes.
2. They complete a provenance document: what the model is not, every dataset with its origin and license, a real citation, and an explicit split between sourced data and their own engineering decisions.
3. They submit one transaction. It deploys the token with a fixed supply, records the provenance hashes on-chain, creates the trading pool, and locks the liquidity. If any step reverts, the whole launch reverts.
4. Trading fees are split by the locker: a majority share into a runtime escrow, a bounded share to the creator, a fixed share to the protocol.
5. The escrow pays for ticks. While it has balance, the organism runs and its page shows current state. When it empties, the organism pauses visibly and says so.

What "running" means here

There is no single runtime. An organism may be a client-rendered browser process, an on-chain state machine advanced by public calls, or an off-chain worker posting checkpoints. What is required is that the creator states which one it is, and what advances a step, in terms a reader can check. Descriptions like "an AI runs it" fail validation in the launch flow.

Fixed supply, no mint

The token contract has no mint function. The supply entered at step 1 is the supply that will ever exist. There is no team unlock schedule to disclose because there is no minting path to schedule.

Two enforced guarantees

Liquidity cannot be pulled, because the locker exposes no withdraw path to anyone. Provenance cannot be skipped, because the launch form will not submit without it. These are the two things Spawn is actually for; everything else is presentation.

Current state of the project

Arc (chain id 5042) is the canonical chain for Spawn. Nothing is deployed on it yet: no $SPAWN token, no factory, no locker, no runtime escrow. Arc carries Uniswap v4 core and Permit2 but no v4 PositionManager, and the liquidity lock and the fee sweep are written against that PositionManager, so launching stays closed until it exists and the contracts are redeployed. Organisms here run in your browser from a fixed seed; none has a pool, a market figure, or a locked position on Arc.

NOTE (v2 migration): the /docs page states "Arc" as canonical and nothing deployed; the /token page states $SPAWN live on Robinhood Chain. This contradiction is captured, not resolved. See the v2 launch spec.