Downloads

tanba-verify

tanba-verify is the command-line checker for everything the platform signs: an approval against its media file, the revocation list, the daily audit anchors, the public ledger and the daily seals of the received statistics. It needs no account and no network, except for the optional block explorer check of the ledger. It is a single file with no installer. Use the build for your system:

SHA-256 list of all files (SHA256SUMS)

Check the download

Compare the hash of the file with the SHA-256 in the table or in SHA256SUMS before you run it.

On Linux:

sha256sum -c SHA256SUMS --ignore-missing

On macOS:

grep tanba-verify-darwin-arm64 SHA256SUMS | shasum -a 256 -c -

On Windows, in PowerShell, then compare the printed value by eye:

Get-FileHash .\tanba-verify-windows-amd64.exe -Algorithm SHA256

The files are built from the source of the platform release that this site belongs to. They are part of that release: the host checks the signature of the release and the hash of every file in it, these files included, before it serves any of them. A separate signature file for each download is not published yet, so the SHA-256 list is the check for now.

Use

tanba-verify spot.mp4 spot.mp4.p7s --roots root.pem
tanba-verify revocations list.p7s --ca root.pem
tanba-verify anchor anchor.p7s --ca root.pem
tanba-verify seal seal.json --ca root.pem
tanba-verify ledger --day 2026-10-14 --ots ledger-2026-10-14.ots --inputs ledger-2026-10-14.json
tanba-verify inclusion --proof ledger-proof.json --approval TNB-2026-000123

root.pem is the platform root certificate that the approvals, lists, anchors and seals chain to. The root for the test contour comes with the test environment. The set of root certificates, and the source archive of the tool, are added to this page when they are published.

Every command prints the result and ends with an exit code, so a script can use it: 0 is good, 2 is a bad signature or inconsistent input, and the other codes name the case (3 hash mismatch, 4 expired, 5 not yet valid, 6 pending or not checked, 7 outer signature invalid, 64 wrong command or unreadable file). The steps with real addresses are in Read a statement and check its evidence.

Use the build that belongs to the current release. An earlier build reports a ledger day that holds a daily seal as inconsistent, because it does not know the newer format of the inputs.