AssetShop · receipts

Verify this release

Every release of this estate is content addressed and carries a fingerprint over every file. What you are looking at right now:

Check it yourself

1. Open deploy-verify.json and pin-manifest.json; the fingerprint and file count are printed there.

2. Anyone with the release folder can recompute the fingerprint: sha256 over every file path and content hash, sorted, as documented in the release notes. The operator tool pin-check.sh fetches every page, script and stylesheet through the gateway and compares each to the build.

3. The pin itself is a public content identifier; the ENS name assetshop.eth points at it. Any gateway serving that identifier serves the same bytes.

Why this exists

AssetShop’s promise is that claims come with receipts. The release you are reading is the first receipt.