QX Pathway

A scan is a moment. A pathway is a record of progress.

Every scan can just be a scan, a number you check and move on from. Or it can become part of a pathway: a track built around a real target, a tier that marks where you stand, and a certificate that proves it, backed by an instructor's name and a tamper-evident hash.

Tracks

Tracks built around real targets.

QX Federal
The flagship track, built around the FBI QIT-99 target and a civilian performance ladder. Seven tiers, Bronze through Black.
QX Core
Everyday practice on the B8c bullseye target, built for steady progression at low cost.
QX Defense
Defensive accuracy on the B27 silhouette.
QX Rimfire
Low-cost .22 LR practice, good for frequent range days and family sessions.
USPSA & IDPA
Run on each sport's own real classifications, GM through D, Master through Novice, straight from USPSA and IDPA's own rulebooks.
Moving through a tier
01

Find an instructor

In person or remote, whichever fits your schedule.

02

Get a code

Tied to the exact track and tier you're attempting.

03

Run the course, scan the target

The same scan you already know, this time tied to a locked, published standard.

04

The instructor signs it

Their name, their judgment, on the record.

05

It's sealed and yours

Permanent, exportable, and yours to show anywhere.

The proof

A real QX Core certificate.

A QX Core Bronze Level certificate lays out the shooter's name and date at the top, the final score and target type in the center, the firearm and ammunition used just below it, and the instructor's name and signature alongside the review method, in person or submitted footage. A verification hash prints at the bottom, tying the whole record to the moment it was sealed.

Score, equipment, review method, and a hash, all printed directly on the certificate.
Every result is hashed

Every scan, sealed the same way.

The moment a target is scanned, the result is sealed with a cryptographic hash. If a score is later validated by an instructor and turned into a certification, a second hash locks the finished record. Either way, the seal works the same: anyone can check a certificate's hash against the public verification link and confirm it matches, exactly as it was the moment it was created.

SHA-256: 7b2e4a9c1f6d8e3b5a0c7f2d4e9b1a6c3d8f5e2a0b7c4d1e9f6b3a8c5d2e7f4b