Browse documentation
WORKINGv2.0

Runtime Battery

The proposed World-specific ETH runtime ledger.

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

Simulation runtime is funded separately in ETH on Robinhood Chain. Trading fees are allocated to creator wallets, Spawn and pons; no automatic trading-fee contribution to runtime is assumed.

Before launch

The submitted model is validated and benchmarked in a sandbox. A quote covers a defined model version, parameter limits, tick cadence, duration or service budget, storage, checkpoint publication and selected visual services. AI can help explain the quote, while measured workload supplies the resource estimate.

Tick count, simulated time per tick, real-time execution cadence and rendering cadence are independent. Generated video is optional and separately metered; one simulation tick does not automatically imply one generated video.

The launcher receives a quoted n ETH amount and an expiration. A one-month initial funding window is a proposal that still needs a product decision. A fixed quote in ETH covers a defined budget; changing ETH prices do not authorize unlimited work or silent deductions.

Ledger and metering

For each World, record deposits, authorized debits, and remaining balance independently. A proposed RuntimeEscrow accepts launch funding and top-ups and restricts withdrawals to an explicitly defined service payment policy. It does not hold creator trading fees.

Each debit identifies the work and authorization that justifies it. A checkpoint hash by itself proves neither execution correctness nor entitlement to payment. Define the initial operator, maximum charge, nonce/replay protection, evidence requirements, and policy for unused funds before deployment.

Pause and resume

If the remaining balance cannot pay for the next authorized work, execution pauses. Preserve complete state, accepted inputs, model version and checkpoint history. After sufficient top-up, resume from the retained state. Do not invent missed tick states. Wall-clock catch-up, queued player actions, retention costs and external-data collection while paused require declared rules.

Finite runs need a bounded funding plan. Open-ended runs use a renewable budget; nobody promises perpetual execution. Pending policy decisions include the initial budget window, top-up threshold, price revisions, refund rights, retention costs and operator replacement.