Work in progress

Work in progress: we are building this site ahead of MainNet. Details will change.

This site is still being built

ZooBC is building in the open. What you see here is current and honest, but it is not finished: read it as where we are today, not as a final statement.

Between now and MainNet, things will change: wording, structure, images, and figures. Some pages are placeholders.

The wider ZooBC ecosystem arrives in stages. The wallet, the explorer, and the community channels each come online as MainNet approaches, and this site grows alongside them.

If something reads wrong, looks broken, or seems misleading, tell us. Feedback now is worth more to us than a polished launch later.

Additional languages will be enabled after the site is complete.

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.

TestNetzoobc.network
Open the verifier
MainNetzoobc.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.

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.