Gamble Client
Sign in

Loader transparency

Check the file.
Know the limits.

Check a loader’s signed release record and executable core before you use it. A valid signature establishes integrity against a signing key; it does not prove that software is safe.

Loading release records…

01 / Release records

Compare the release.

The browser checks each record’s signature using the public key returned by Gamble’s API. This relies on the website and API you loaded; it is not an independent security audit.

WINDOWS / X64Verifying…
Version
—
Release SHA-256
—
Core SHA-256
—
Source commit
—
LINUX / X86-64Verifying…
Version
—
Release SHA-256
—
Core SHA-256
—
Source commit
—
Signing key 617acff9930c4e68 Loading public key…

Release SHA-256 identifies the published file. Core SHA-256 covers the immutable loader entries. Personalized files can have a different whole-file hash. If records are unavailable, no successful check is implied.

02 / Your loader

Check your JAR.

Your file never leaves this browser through this verifier. Select a loader JAR to compare its executable core with its embedded signed release record.

  • Checks the signature and immutable loader entries.
  • Excludes personalization: mod metadata, icon, enrollment data, and the provenance record itself.
  • Does not scan behavior, check the downloaded client payload, or establish that this is the newest release.

Ready when you are

Select a file to begin. Release records must load first.

03 / Make an informed choice

Integrity has limits.

A signed file can still contain unwanted behavior. Consider the source, the permissions it needs, and any scanner findings alongside the checks above.

If a scanner raises an alert

Keep the exact file hash, scanner name, and report. Findings about another version do not establish the safety of your file. This page does not provide a current independent malware assessment.

If verification fails

Stop before running the file. A failure can mean a changed file, unsupported format, or unavailable release data. Get a fresh copy from the download page and ask for help if the result remains unclear.

Need help interpreting a result? Open a ticket in the Gamble Client Discord with the version, file hash, and error or scanner report. Do not share login tokens or enrollment credentials.