OMNI saysSEED — build deterministic state from a seed value (v3.2 genesis verb).
SEED (added v3.2) deterministically constructs state from a seed value — same seed in, same state out, every time. It's the primitive beneath GENESIS and the per-user chain: reproducibility without storing the state itself. SEED is why a user's surface can be regenerated anywhere from their private seed rather than synced from a server. Determinism is the whole point — no randomness sneaks in.
Power-ups you unlock
Build deterministic state from a seed
Same seed → same state, always
Primitive beneath GENESIS
Reproducible without stored state
The Silent Failure attacks — common mistakes
Non-determinism creeping into SEED
Storing state that should be SEED-derived
Confusing SEED with GENESIS (SEED is the primitive)
Boss battleExplain why SEED must be perfectly deterministic.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>seedState(seedValue) → deterministic state
same seed → identical state (no randomness)
basis of reproducible instances</pre></body></html>