capture · prove · share · Madden NFL 27 first

One app.One recording.One receipt.

Play your match with QorCap, one lightweight Windows app that records the capture card and fingerprints every second of video. When the match is over, QorTime does the heavy lifting on the finished recording: a signed receipt, an AI referee verdict, and a public verify link. Nothing heavy runs while you play.

Stripe test mode · $9.99 USD · not a live charge · early access until KYC

scroll to seal a match

how it works

Capture. Prove. Share.

1 · Capture

QorCap is the one app you run, on Windows, during the match. It records the capture card and fingerprints the video as it is written: every segment is hashed and chained, with timestamped checkpoints. It stays light, so it doesn't strain your laptop.

controller button log in the same session · since v0.3.0

2 · Prove

After the final whistle, QorTime works on the finished recording. It re-checks the fingerprints, reads the score, and seals a signed receipt. The AI referee reviews the evidence and signs a verdict: accept, dispute, or abstain, with plain reasons and the evidence frames.

3 · Share

Send the receipt to your opponent, a tournament, or a platform. Anyone can check it in the free browser verifier, and nothing is uploaded. A hosted referee countersign, Verified Match, is in test-mode early access.

Inside the Prove step

  • Integrity checks in code: video fingerprints, checkpoint chain, and signatures. Scores can only move in legal football steps, never backwards. The clock only runs down within a quarter. The final screen must match the last score.
  • AI referee: reads frames to confirm the score. It only accepts a reading when it is confident and the reading agrees across several frames, and it abstains rather than guessing. Tampering is caught by the integrity checks, not by trusting a model.
  • Honest limit: QorTime proves the footage's integrity and timing. Since QorCap v0.3.0 it also logs controller reports from a pad that enumerated on USB in that session. It does not prove who held the controller, or that the console obeyed that pad.
How it works

01 / capture

The scorebug, read off the screen.

QorTime's scorebug reader reads the final score from the recording, digit by digit, and only locks when consecutive frames agree.

  • frames read from the capture card
  • score locked on frame agreement
  • Madden NFL 27 first, more titles roadmap
HOME
Q40:00FINAL
AWAY
readinglocked ✓
SEALED

Illustrative scorebug, not a real match. No league or publisher marks.

02 / challenge

Prove a human is on the sticks.

Three referee challenges per match: game start, the second half, and the fourth quarter. The player pauses and enters the pattern. On QorCap rule v2 that pause has to show up within 2.5 seconds. A relay under 2.5 seconds is not reliably caught.

QorCap logs the controller since v0.3.0. Since v0.3.11 a challenge only opens when Madden lets you pause: after the kickoff and a play call, never during a kickoff. Receipts with no rule id still use the older 600 ms ceiling.

referee nonce 7f3a·c19e❚❚ PAUSED
OPT←→✕↓○
2.5 s windowpause inside 2.5 s ✓

03 / co-sign

The laptop signs the chain. The referee timestamps it.

Checkpoint countersignatures come from the laptop’s own key. The official referee does not treat those as live: the key sits on the player’s PC. What the official referee does sign is the chain head, about every 60 seconds, plus the three challenges. A receipt forged later cannot invent those timestamps.

KICKOFF00:00:00h0 3c9a…11f0PC ✓
CP 100:00:04h1 a81e…92b4PC ✓
HEAD00:01:00anchor · 60sQOR ✓
CHALLENGE00:07:31nonce 7f3a…c19eQOR ✓
HALFTIME00:14:02h210 e5b2…7d19PC ✓
CP 41100:27:24h411 9c0f…4e8aPC ✓
FINAL00:27:28seal 21–17SEALED

Illustrative values. PC is the laptop key. QOR is an official referee timestamp. It is not proof of a TPM.

04 / seal

The receipt prints. Everyone signs.

At the final whistle the player’s key signs the result. A receipt from one console is the one-player tier. Two-sided corroboration is a separate indicator. It never changes the verdict. It is available from QorCap v0.3.31 when both players pair their match: each client sends the referee’s pairing token and a signed score timeline. It has not yet been tested on a real two-player match.

qor-receipt/v0
match    madden27 · ps5
result   HOME 21 — AWAY 17 · Q4
challenges  3 / 3 passed
checkpoints 412 · laptop key
receipt_hash
sha256:9f3ac41e0b7d52e88a1f64c930de7b21a5c0f8e3d6b94a72e1c907fb
  • sig.homeed25519:9f3a…c41e✓
  • sig.refereeed25519:e1c9…07fb✓
SEALED

Illustrative values, not a real match.

05 / verify

One verdict. In your browser.

Paste the JSON into the verifier. It checks every signature, the checkpoint chain and the challenges locally and returns a verdict. Nothing is uploaded.

VERIFIEDEvery signature, checkpoint, and challenge holds against a referee key on QorTime’s trusted list.
PARTIALSignatures check out against a trusted QorTime referee, but something is missing (a challenge, motion, …). An untrusted key is not PARTIAL.
SELF_ATTESTEDCryptography holds, but the referee key is not on QorTime’s built-in trusted list (local Start Match key, home-made key, or revoked). Never shown as VERIFIED.
FAILA signature, the chain, or a challenge does not hold.
checking 412 signatures…
VERIFIEDtrusted referee key · chain intact · 3/3 challenges
◆ one-player tier · one recordingcorroboration · separate · paired matches

for platforms & sponsors

Release escrow on math, not screenshots.

Verify in one call

The reference verifier ships as a Python CLI and a small browser JS module. Run it on every result before paying out.

qortime verify r.json --referee-pub <hex>hosted verify API · roadmap

Fewer score disputes

A sealed receipt replaces "he lied about the score" tickets with something a machine can check. What it can't see, we list plainly below.

Open format

JSON, canonicalized (JCS), Ed25519 signatures. Spec and schema in the repo, MIT licensed.

TPM device key · claimed, unverified (a checked TPM quote is roadmap)

Honest limits

QorTime proves the footage's integrity and timing. Controller reports from a USB-enumerated pad in the same session are logged by QorCap since v0.3.0. It does not prove:

  • Account sharing: who is physically holding the controller. The referee does not check pad identity. QorCap’s second-pad note, when it exists, stays in the local input_proof.json.
  • Right-stick injection: an inline passthrough adapter can add right-stick input the console obeys while QorCap logs the real pad. Open. Planned checks are an advisory per-axis stick-versus-camera signal first, and hardware such as a sealed tap before any pad-to-console binding.
  • Collusion: both players agreeing to throw or fake a match.
  • Anything outside what the capture card saw.
  • Red team: a virtual capture device was missed. Relays under about 2.5–3 seconds, and a splice that is rehashed and resigned, came out weak. QorCap red-team notes.
Read RISKS.md

test · early access until KYC

Buy the seal. Test money only.

Verified Match is a $9.99 hosted-referee countersign after a completed match. It is early access. The button opens a Stripe test Payment Link. Business KYC is still open, so this is not a live paid product and it does not charge real money.

  • $9.99 USD list price · one-time · test checkout
  • test card 4242 4242 4242 4242
  • free self-verify stays in the browser

A test payment shows a neutral “paid, test mode” tag. Gold appears only after the verifier reports VERIFIED for that receipt. A Payment Link purchase alone has no receipt id.

Check a receipt yourself.

Early prototype. The verifier runs entirely in your browser.