Protocol token

$SPAWN

The $SPAWN token contract is deployed on Robinhood Chain. There is still no market, no allocation table, and no date. The figures below are empty where filling them in would be fabrication. The sections after them describe what the token is intended to do, and state plainly which parts of that design are not yet decided.

StatusLive — contract deployed
Venue at launchPons v2 — pool does not exist yet
Supplynot decided
Trading tax1% on $SPAWN trades — intended; verify in deployed code
Priceno market
Holdersno tracked data
Launch datenot announced

What $SPAWN does

Two mechanics, and only two. They are separate from the fee split that every organism's own token carries. That split — runtime escrow, creator, and a fixed protocol share — is a property of each organism launch and has nothing to do with $SPAWN. It is documented in full under Runtime funding and farming → and is not restated here.

01 · Trading tax on $SPAWN, routed to $SPAWN liquidity

$SPAWN is intended to launch on Pons v2 carrying a 1% tax on trades of $SPAWN itself. The tax accumulates and is periodically injected into $SPAWN's own liquidity pool, deepening that pool over time. Injected liquidity is not withdrawable.

Not yet decided: whether that injection is built into the tax contract, exposed as a function anyone can call, or triggered by a privileged wallet. The contract is deployed, but this site has not verified the trigger mechanism, so the honest answer today is that the trigger is undetermined. We will not call it automatic, permissionless, or admin-free until the deployed code is public and says so. Until then, assume a privileged trigger.

02 · Burning $SPAWN gates organism creation

Launching a new organism is intended to require burning a fixed amount of $SPAWN. The burn is spent, not staked and not refundable, and it is the only role $SPAWN plays in the launch flow.

Burn amount1,000 $SPAWN — burned on launch, not refundable

The launch flow is live and enforces it: the wallet's $SPAWN balance is read from the chain, the burn is submitted as one transaction, and the organism is recorded only after this site reads that transaction back and confirms the tokens left circulation. If the token contract exposes no burn function, the tokens are sent to 0x000000000000000000000000000000000000dEaD instead. The burn creates no organism token, no pool, and no liquidity lock — those contracts are not deployed.

What $SPAWN does not do

It plays no role in verification, replay, or provenance. Every provenance document, dataset hash, citation, seed, and step function is public, and re-running an organism from its seed requires nothing but the published specification. Holding $SPAWN does not grant access, and holding none does not withhold it. Those parts of the protocol are free and open to anyone, permanently, regardless of token balance.

It does not fund any organism's runtime. Runtime is paid from that organism's own trading fees, and when those stop the organism pauses. No amount of $SPAWN changes that.

It confers no governance right, no revenue claim, no share of an organism's fees, and no entitlement of any kind. It does not make an organism's claims more credible; only the provenance document and a reproduced run do that.

A deeper liquidity pool is not a price floor, a yield, or a guarantee. It affects how much a given trade moves the price and nothing else.

Relationship to organism pools
Every organism has its own token and pool. $SPAWN is a separate token with its own pool; the organism-level protocol share exists whether or not $SPAWN ever launches.
Verify the contract address
The only $SPAWN contract address listed by this site is 0x41080c9d7908ce567efe239042c49d8159a2a3bb. No presale, allowlist, or private round exists. Any token, form, or address presented as $SPAWN that does not match this one is not from us.