The Seven LayersISSUE #56 of 73

per-user chain blocks · the schema

OMNIVSThe Silent Failure

OMNI saysThe per-user chain (§1d) records every boot as an immutable block with a fixed schema.

Each instance has its own append-only chain — one chain per user. Every version writes a block with the fixed schema (n, version, ts, prev_hash, instance_h, delta_h, meta_sig, hash): a sequence number, version, timestamp, the previous block's hash (the link), instance and delta hashes, the metaSurf signature, and this block's hash. The prev_hash chaining makes tampering evident, exactly like a blockchain — but scoped to one user, locally (e.g. IndexedDB).

Power-ups you unlock

One append-only chain per user
Block schema: n, version, ts, prev_hash, …, hash
prev_hash links → tamper-evident
Local, per-user (not a shared global chain)

The Silent Failure attacks — common mistakes

Skipping schema fields
No prev_hash link (chain not tamper-evident)
Sharing one chain across users

Boss battleWrite a commitBlock that fills the fixed schema and links prev_hash.

Example code

<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>block = { n, version, ts, prev_hash,
          instance_h, delta_h, meta_sig, hash }
hash links to prev → tamper-evident, per user</pre></body></html>

▶ Open the interactive comic issue

‹ Honesty Tags · When To Flag · When To Remove Detect And Rollback · Finding The Bad Block ›