Browse documentation
WORKINGv2.0

Risk

Contract, market, runtime and verification risks.

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

Spawn Worlds combine token markets, simulation software and external infrastructure. Their risks are distinct, and a successful model review does not certify the token or promise financial returns.

Contracts and payments

Contract bugs can cause loss or inaccessible funds. Integration must verify the original $SPAWN token, selected pons factory, creator recipient controls, launch router, fee splitter and runtime escrow. A website cannot enforce a fee allocation that underlying contracts allow another caller to bypass.

The proposed combined launch reverts financial effects on failure, but transaction gas remains spent. A prior token allowance can remain. Retirement is permanent once the launch succeeds; the exact burn or dead-address mechanism must be disclosed. Native ETH on another chain does not satisfy a Robinhood Chain payment.

Token and liquidity markets

Token holders can sell, trading volume can stop, prices can fall substantially and liquidity can be insufficient for an exit. A lock constrains specified withdrawal paths; it does not guarantee value, market depth or correct model behavior. pons policies and deployed versions must be read precisely.

Runtime and presentation

Funding is finite. Runtime pauses when its declared budget cannot pay for the next work. Storage retention, refunds, catch-up and operator replacement need explicit policies. Compute estimates, gas, ETH prices and video service availability can change. A generated video is presentation rather than execution evidence.

Models and verification

Rules may be unbalanced, uninteresting or scientifically inaccurate. AI-assisted creation and review can make mistakes. Checkpoint hashes do not establish correctness without replay or another implemented verifier. External data must be available to reproduce a run; a missing input archive can prevent verification.

Version transitions and player actions need clear authorization and effective-tick rules. A deterministic outcome does not by itself establish any legal classification for paid participation or rewards; those product mechanics require separate review before being offered.

Infrastructure

Wallets, Robinhood Chain, RPCs, indexers, pons contracts and compute providers may fail or change. Display actual deployment and verification status. No specific token price, yield or perpetual runtime is promised.