Verify

Verify a Release (simple)

Using the public key file (recommended):

minisign -Vm hash_manifest.txt -p pubkey.txt
# or verify a single file + its .minisig
minisign -Vm RAG_systems_prototype.mp4 -p pubkey.txt

Using the inline -P form (no file needed):

minisign -Vm hash_manifest.txt \
  -P "RWRRud/h10tLY/tq1TOly33agV47Pg59+bPKQIZeT3+4BXcpaIYm28R4"

Verify Hashes (optional, defense-in-depth)

After verifying the signed manifest, confirm file checksums match:

shasum -a 256 RAG_systems_prototype.mp4
shasum -a 256 "Stanford AI Protocol.mp4"

If you publish a hash_manifest_release.txt, users can verify it the same way with minisign.

Troubleshooting

• Key mismatch: “Signature key id … but the key id in the public key is …” means the signature was made with a different key. Use the published key above or re-sign with the matching secret key.
• No such file: Ensure you’re pointing to the correct pubkey.txt path, or use the inline -P form.