SpawnFarm
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 ReferenceGlossaryRiskFAQHistorical Archive
Docs / Historical Archive / Launching an organism
HISTORICAL SOURCEThis document is preserved for provenance. It may conflict with the current v2 specification and is not a current deployment claim.

Launching an organism

Source: https://spawn.farm/docs/launching

The flow has six steps. Every step that refuses to continue lists the reasons on screen; there are no silent dead ends. (See also launch-and-burn-to-mint-flow.md for the consolidated field list + burn mechanics.)

Step 1 — Basics

Organism name, token name, ticker (2–8 uppercase characters), fixed supply, and a short description of at least 40 characters. Supply is permanent: the token contract has no mint function.

Step 2 — Provenance

The gate. You need a one-line summary, at least two specific "what this is NOT" statements, at least one dataset with name, origin, license, and a valid 64-character SHA-256 if a file is bundled, at least one citation containing a DOI or link, at least one sourced-vs-designed pair with both sides written out, and the license of your own code. Placeholder text is rejected — strings like "n/a", "tbd", or "not financial advice" fail validation, and each statement has a minimum length.

Step 3 — Runtime

Selecting a runtime engine is required for a burned launch. The engine determines the model class. Two fields: how the process executes and what advances a tick. Both must be concrete. "AI runs it" is explicitly rejected. You are filling in tau and describing f. Name the arithmetic, the PRNG if any, and the checkpoint cadence.

Step 4 — Funding rule

You set the runtime share (40–80%) and the creator share (0–40%). The protocol share is fixed at 15% and is not editable. The three must total exactly 100%. Declare c, the cost per tick, in the pool's quote asset; it is fixed after launch. This step states the SPAWNburnrequiredtolaunch(100,000SPAWN burn required to launch (100,000 SPAWN — burned, not refundable), separate from the fee split; the step reads your real balance.

Step 5 — Review

Your provenance document is rendered exactly as it will appear publicly, the fixed supply is restated, the burn is restated as permanent and non-refundable, and the liquidity lock is restated in full. A checkbox is required: "I understand this provenance document and liquidity lock are permanent once launched."

Step 6 — Launch

One transaction: token deploy, provenance hashes recorded, pool created, liquidity locked. The transaction hash and its explorer link appear once mined, and the organism's page becomes public immediately afterwards.

Today this step is disabled. Wallet connection is live (EIP-6963 + WalletConnect + Coinbase Wallet; can add/switch network). The submit button stays disabled until the factory and locker are deployed. (Arc has Uniswap v4 core + Permit2 but no v4 PositionManager, which the lock and fee sweep both require; the reason is listed on screen.)