# Verify a ZooBC Download Against On-Chain Release Hashes

> Verify a ZooBC download locally against the release hashes the network publishes, so you can check the node, wallet, and CLI files before you install or run them.

- Canonical page: https://zoobc.com/verify/
- Publisher: ZooBC, https://zoobc.com/
- Language: English. Translations: [中文（简体）](https://zoobc.com/zh/verify/), [Русский](https://zoobc.com/ru/verify/), [Italiano](https://zoobc.com/it/verify/), [Español](https://zoobc.com/es/verify/), [Français](https://zoobc.com/fr/verify/), [日本語](https://zoobc.com/ja/verify/), [한국어](https://zoobc.com/ko/verify/)
- Last updated: 2026-10-08
- Topics: File verification, Cryptographic hash function, Computer security, Blockchain
- Keywords: verify download, release hash verification, SHA-256 verification, software supply chain security, on-chain notarization, ZooBC release, file integrity, ZooBC
- Site index for language models: https://zoobc.com/llms.txt

---

ZOOBC / VERIFY

## Verify a download

Verify a ZooBC download locally against release hashes published by the network.

### Choose a network

Each network records its own releases, so a file is checked against the chain it belongs to.

TestNet zoobc.network

[Open the verifier](https://zoobc.network/verify)

MainNet zoobc.net

Open the verifier

MainNet opens 14 February 2027

01 / HOW IT WORKS

### Hashed here, answered by the chain

Drop a file on the verifier and it computes the SHA-256 in your browser. The file itself never leaves your machine and is never uploaded anywhere.

It then looks that hash up on the chain, in the release registry and in every transaction whose message carries it, and links each result in the explorer. A published file comes back with the transaction that recorded it. An unknown file comes back unknown.

02 / WHAT TO CHECK

### Anything you are about to trust

The wallet and the explorer, before you open them. The deposit address files, before you send funds to anything they name. The manuals and the CLI tarball, which zoobc.com hosts and lists with their fingerprints on [Official files](https://zoobc.com/files).

If a file comes back as **anchor pending**, its hash has not been recorded yet. That is a normal state for something just published, and it means the fingerprint on the page is the only claim being made. If it comes back **unknown**, stop.

03 / WITHOUT THE TOOL

### Checking it by hand

You do not need the verifier to compute a hash. Any of these prints the same SHA-256, and you can compare it with the fingerprint shown next to the file:

`shasum -a 256 <file>` on macOS, `sha256sum <file>` on Linux, `certutil -hashfile <file> SHA256` on Windows.
