Checkpoints

Compact state commitments for off-chain execution.

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

Principle

Complex simulations should not put every cell/agent/data byte on-chain.

Instead:

execute off-chain → commit compact state on-chain.

Canonical checkpoint

A checkpoint should commit to at least:

World ID;
Season ID;
tick/epoch;
previous state root;
new state root;
input root;
code hash;
runtime/environment hash;
relevant data-manifest version;
submitter;
bond/status.

State roots

Historical Spawn used SHA-256(serialise(state)). This remains useful as an archival/replay fingerprint.

For efficient partial-state proofs later, a Merkleized state root may be added. This is NEEDS PROOF; do not represent it as selected until state layout/proof costs are tested.

Hash limitation

A hash proves commitment to a value, not execution correctness. A malicious operator can hash a fabricated state perfectly.

Therefore checkpoint commitment must be followed by verification/finality before economic settlement.