Runtime Battery

v1 target

Spawn-managed or explicitly approved infrastructure executes off-chain simulation jobs in pinned environments.

Runtime job

A job contains:

• World/Season/tick range;
• previous finalized state commitment;
• exact ordered input commitment;
• Blueprint/runtime/code hash;
• configuration hash;
• data manifest/version;
• maximum resource budget;
• expected checkpoint output format.

Runtime Battery

$ETH-funded contract/accounting module exposes at least:

• fund/top-up;
• runtime balance;
• committed/paid runtime obligations;
• ticks remaining estimate when cost is fixed enough to express;
• authorized post-finality payment path.

Payment timing

For purely on-chain deterministic ticks, an immediate keeper reward after successful transition may be acceptable.

For off-chain computation, a runner should not receive the full reward simply for posting a hash. Recommended order:

execute → submit candidate + bond → verify/finalize → pay runner + return bond.

Later marketplace

Qualified providers compete on cost, latency, reliability, deterministic compatibility, hardware fit, and reputation. Verification remains independent of provider selection.