Snapshots on chain

A snapshot is built in your browser. For every file, sorted by path, the studio writes one line: the SHA-256 of its content, its size in bytes and its path. The snapshot hash is keccak256 of that text.

<sha256 hex> <size> <path>\n   (one line per file, sorted by path)
snapshot hash = keccak256(all lines)

The first anchor creates a project (title up to 64 plain characters) and its version 1 in one transaction. Later anchors add versions 2, 3 and so on. Only the wallet that created a project can add versions to it, and a version identical to the latest one is refused.

What it proves, and what it does not

It proves that this wallet anchored these exact files at this block. It does not prove who wrote them, that they work or that they are safe. Your code is never sent anywhere: only the hash, the file count, the total size and an optional label go on chain, and blockchain data is public.

Until the contract address is published, anchoring runs in practice mode: you sign a message, nothing is sent and the record stays in this browser.