How to Check a License Agreement's SHA-256 Fingerprint, Step by Step

What a SHA-256 fingerprint tells you

A SHA-256 fingerprint is a 64-character value computed from the contents of a file. Delithius Labs publishes the SHA-256 of each License Agreement file. A reviewer computes the same value on the downloaded file and compares the two, which shows that the agreement they read is the agreement published.

Check it in three steps

You will use three things: a downloaded copy of the agreement file, a terminal on your computer, and the published fingerprint to compare against. The check takes a few minutes, and it runs on your own machine.

1. Download the agreement file from its stable address

Each agreement file is served at a stable address. The Czo License Agreement page links its file, LICENSE_AGREEMENT_v1.8.md, and the QC Fix Engine and LagZero pages link theirs. Download the file to your computer and leave it unedited. Save it under the file name the site gives it, so the command and the published list use the same name.

2. Run the checksum command on your computer

Run this command in a terminal, with the name of the file you downloaded:

sha256sum FILE

For example, sha256sum LICENSE_AGREEMENT_v1.8.md prints a 64-character value followed by the file name. The plain-text file hashes.txt on the site also lists the commands for macOS (shasum -a 256 FILE) and Windows (certutil -hashfile FILE SHA256).

3. Compare the result with the fingerprint on the page

Compare your value with the fingerprint published on the Delithius Labs home page and on the agreement page. If the two values match character for character, the file you downloaded is the file Delithius Labs published.

Where the three current fingerprints live

The fingerprints appear in the Agreement fingerprints block on the home page, on each agreement page, and in one plain file, hashes.txt. Each fingerprint below is the SHA-256 of the agreement file served at its stable address, as published on October 16, 2026.

Each new agreement version carries its own version number and its own line in hashes.txt.

Why published versions matter to a reviewer

License Agreements are published with version numbers and SHA-256 hashes, and acceptance is recorded before checkout. A reviewer in legal, security or engineering can read a specific version, record its fingerprint, and later confirm that the version on file is the version that was published. The trust and security page explains more about how Delithius Labs handles what matters.

Read the agreements and their fingerprints at delithiuslabs.com/license-terms/.

Quick answers

How do I verify a Delithius Labs license agreement?

Download the agreement file from its stable address, run sha256sum FILE, and compare the result with the fingerprint published on the site. The same values sit in one plain file, hashes.txt.

What is a SHA-256 fingerprint?

A SHA-256 fingerprint is a 64-character value computed from the contents of a file. Delithius Labs publishes the SHA-256 of each agreement file, and you compare your computed value with the published one.

Where can I find the agreement fingerprints?

Find them in the Agreement fingerprints block on the home page, on each agreement page, and in the plain file hashes.txt.

Which agreement versions are current?

The current versions are the Czo IP License Agreement v1.8 (2026-10-08), the QC Fix Engine License Agreement QC-v1.8 (2026-10-08) and the LagZero Platform License Agreement LZ-v1.8 (2026-10-08).

Delithius Labs LLC, Goldsboro, North Carolina. Written and checked against the live site on October 16, 2026; prices on the product pages control.