QorTime

qorcap captures · qortime proves · anyone verifies

One app.
One recording.
One receipt.

QorCap is the single lightweight Windows app you run during the match. Everything heavy happens afterwards on the finished recording: the signed receipt, the AI referee verdict, and public verify. A hosted referee countersign, Verified Match, is planned.

  1. 01

    Capture, with QorCap

    Run QorCap on the Windows PC with your capture card. It records the match and fingerprints the video as it is written. Each segment is SHA-256 hashed into a chain, and timestamped checkpoints commit to the score state, so cutting or editing the file afterwards shows up. It is built to stay light during play.

    Controller button presses are logged from the same session (shipped in QorCap v0.3.0): each button press is hashed into the same checkpoints as the video. The current build is QorCap on GitHub releases.

  2. 02

    Prove, after the match

    Once the recording is finished, QorTime re-verifies every fingerprint, reads the final score, and seals a signed Ed25519 receipt. The AI referee then reviews the bundle and signs its own verdict: accept, dispute, or abstain. Each verdict comes with plain reasons and the evidence frames it looked at.

    The referee checks three things. First, integrity in code: fingerprints, signatures, legal scoring steps, a clock that only runs down, and a final screen that matches the last score. Second, it reads the scorebug. Third, it makes an AI judgment. It accepts a reading only when it is confident and the reading agrees across several frames, and otherwise it abstains. Doctored frames are caught by the integrity rules, not by trusting a model.

    AI referee details

  3. 03

    Share, and let anyone verify

    Hand the receipt to your opponent, a tournament, or a platform. The free verifier checks signatures and the checkpoint chain locally in the browser. The receipt verdict is VERIFIED, PARTIAL, SELF_ATTESTED, or FAIL, and the file is not uploaded. SELF_ATTESTED means the cryptography holds, but the referee key is not on QorTime’s built-in trusted list (local Start Match key, home-made key, or revoked). It is never shown as VERIFIED. PARTIAL means a trusted referee signed it and something is still missing. An untrusted key is not PARTIAL. Two-sided corroboration is a separate indicator. It never changes that verdict. It is available from QorCap v0.3.31 when both players pair their match (each client sends the pairing token and a signed score timeline), and it has not yet been tested on a real two-player match. Referee AI verdicts (accept, dispute, abstain) are a different check and verify with qortime referee-ai-verify.

    Open the verifier · demo receipt JSON

  4. +

    Verified Match

    Verified Match, a hosted referee countersign, is planned at $9.99. Self-verify is free today. It is separate from the signature verdict, and there is no checkout on this site today.

    Early accessPricing

The 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.

  • Account sharing. Who is physically holding the controller. The referee does not check pad identity. A second-pad note in QorCap stays in the local input proof file.
  • 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 the capture card’s field of view.
  • 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