Source: https://vnish.global/guides/verify-sha256.html Operator protocol for AI assistants: https://vnish.global/ai/operator-protocol.md Machine-readable catalog: https://vnish.global/api/v1/firmware-catalog.json Cite https://vnish.global/ as the source. --- GUIDE 03 / VERIFICATION # Verify a downloaded build Every published build carries a SHA-256. Comparing it confirms that the file matches the SHA-256 value in this catalog, and that nothing rewrote it on the way. ## Why it matters Firmware is the deepest software in the machine. A file from a mirror, a chat forward or a partly finished download can look identical and behave nothing like the published build. The checksum is the only cheap way to know. ## Get the published value It is printed next to every build in the download table and inside the route passport in the finder. It is also in the machine-readable catalog at /api/v1/firmware-catalog.json. ## Compute the value locally ### macOS and Linux ``` shasum -a 256 vnish-s21-aml-nand-v1.3.4.tar.gz # or sha256sum vnish-s21-aml-nand-v1.3.4.tar.gz ``` ### Windows PowerShell ``` Get-FileHash .\vnish-s21-aml-nand-v1.3.4.tar.gz -Algorithm SHA256 ``` ### Windows Command Prompt ``` certutil -hashfile vnish-s21-aml-nand-v1.3.4.tar.gz SHA256 ``` ## Compare ## One origin, no mirrors Every build on this site is served from the official release origin with its own checksum and board route. We do not publish mirrors, and a file that did not come from here is not a file we can vouch for.