What If Your Inputs Could Vouch for You?

Vera's current proof model is built around one question: what was running on your system during gameplay?

It is a narrow question, deliberately. We record processes, drivers, and system integrity signals. The stuff that would tell you whether cheat software was present. We do not analyze your play. We do not evaluate whether your shots were too good. We are not in the business of judging outcomes, because outcomes are a terrible proxy for integrity.

A world champion hitting impossible shots is still clean. A mediocre player missing everything could still be cheating. Stats do not tell the story. Evidence does.

That is where Vera sits today. System state. Clean signal. Inspectable by anyone.

But there is a question we keep coming back to, and it is the one this piece is about: what if the inputs themselves could vouch for you?

This is a long one. It is written for the people who want the mechanism, not the metaphor. If you build anti-cheat, train models, or have simply wondered whether "too consistent to be human" can be made rigorous, this is for you.

---

The Fingerprint in Your Hands

Every competitive player builds something over thousands of hours of practice: a physical vocabulary. A set of reflexes and micro-habits so deeply ingrained that they happen below conscious thought. That vocabulary lives in your hands, in how you grip, how you move, when you commit, and how you recover from mistakes.

That vocabulary is also measurable. And it is specific to you in ways that are genuinely hard to fake.

The reason it is hard to fake is not mystical. It is that human motor control is noisy in structured ways. Your nervous system does not produce a clean trajectory to a target. It produces an initial ballistic movement that overshoots or undershoots, followed by one or more corrective submovements that home in. That two-phase structure has been studied since the 1980s, and the math behind it is well understood. A model that respects it will land softly. A model that ignores it looks mechanically perfect, and mechanical perfection is exactly the artifact we are looking for.

---

What the Signal Actually Looks Like

Strip the romance out of it and a session of aim is a time series. Position samples at the device's polling rate (1000 Hz is common for a modern mouse), each with a timestamp. From that raw stream you derive the things that carry identity.

Kinematics. Differentiate position to get velocity, again for acceleration, again for jerk. A flick is not one motion. It is a ballistic launch with a characteristic peak velocity and time-to-peak-velocity, followed by a settling phase. Two players can land on the same pixel and have completely different velocity curves getting there. The ratio of gross movement to the corrective micro-movements that follow is a per-player constant far more stable than accuracy.

Submovement structure. Decompose a flick into its component submovements and count them. Measure the speed-versus-accuracy tradeoff against Fitts's law and read off an effective throughput in bits per second. Elite players are not just faster. They reach a given accuracy with fewer corrective submovements, and their throughput sits in a tight band session to session.

Tremor. Hold your crosshair "still" on an angle and your hand still moves. Physiological tremor sits in a roughly 8 to 12 Hz band, and its spectral peak, amplitude, and directional bias are close to a signature. Run a power spectral density on the micro-movement during hold frames and that peak is either there or it is not. Injected "human-like" motion almost never reproduces it correctly, because nobody bothers to model the tremor of a tired wrist.

Timing. Reaction time is not a number, it is a distribution, and its shape is the tell. Human reaction times fit an ex-Gaussian: a Gaussian component plus an exponential tail (the parameters are usually written mu, sigma, tau). The tail, tau, is the human part. It is your attention wandering, your read being a beat late, your nervous system being biological. A humanized aimbot can match your mean reaction time and still produce a distribution with almost no tail, because it does not get distracted. Too little tau is as suspicious as too little variance.

Concretely, a per-engagement feature vector starts to look like this:

features = {
  flick_peak_velocity,        # deg/s
  time_to_peak_velocity,      # ms
  submovement_count,          # corrective phases per flick
  fitts_throughput,           # bits/s
  tremor_peak_hz,             # spectral peak of hold-frame micro-motion
  tremor_power,               # amplitude in that band
  reaction_mu, reaction_sigma, reaction_tau,   # ex-Gaussian fit
  ttk_jitter,                 # variance of crosshair-on-target -> fire
  micro_to_gross_ratio,       # fine adjustments vs large sweeps
}

None of these is identifying on its own. Together, across hundreds of sessions, they define an envelope: a behavioral baseline that any single session can be scored against.

Controller Players

The same principle applies completely. It is just a different vocabulary, sampled at the controller's poll rate.

A controller fingerprint lives in thumbstick dynamics: the pressure curves, how the player navigates the dead zone, how far they push the stick during a strafe versus a fine aim adjustment, the response-curve shape they have unconsciously calibrated around. It lives in trigger timing, how long they hold before a shot, how they sequence the aim input against the fire input. It lives in the micro-oscillation of their aim while holding an angle, which is the controller analogue of mouse tremor.

Elite controller players have something even more distinctive: the interplay between both thumbs. Moving while aiming creates a predictable interference pattern between the left and right sticks, specific to how a given player's brain runs movement and aim correction in parallel. Two players can post identical aim stats and produce completely different joint stick dynamics.

And there is a hardware layer. Every controller has its own sensitivity profile, calibration offset, and firmware-level input handling. A player who has been on the same pad for two years has their mechanics tuned around its specific dead zones and response curves. Change the controller and the fingerprint shifts in detectable ways, which is itself a useful signal.

---

Why This Changes the Detection Problem

The classic problem with statistical aimbot detection is not that aimbots are invisible. It is that by the time you flag one from outcomes, you are working from outcomes, and outcomes can always be argued. Everyone has one incredible game. Everyone has a session that looks weird in hindsight. Outcome-based flags are forever contested.

Input-based analysis is a different kind of evidence, for two reasons.

First, the inputs carry artifacts that outcomes hide. An aimbot, however sophisticated, leaves a signature in the raw stream. The tracking is too smooth, with velocity discontinuities at the exact frame it snaps. The corrections arrive at frame-perfect intervals. The reaction-time distribution is impossibly narrow in the tail. You are not arguing about whether a clip looks fishy. You are measuring whether a distribution has the shape biology produces.

Mechanically, you are running per-player anomaly detection. Fit a baseline distribution over a player's historical feature vectors. Score a new session by how far it sits outside that envelope. Two-sample tests like Kolmogorov-Smirnov, or an earth-mover (Wasserstein) distance on the reaction-time or velocity distributions, give you a principled "how different is this session from this player" number instead of a vibe.

Second, you can correlate inputs against game state, which is where it gets genuinely hard to beat:

• Did movement begin toward an enemy position before that enemy was visible on screen? That is a wallhack signal, and it lives in the timestamp delta between input and line-of-sight, not in any VOD.
• Did a trigger fire at frame-perfect timing relative to a crosshair crossing a hitbox? That is a triggerbot or macro.
• Is reaction time effectively identical across hundreds of engagements? Inhuman consistency is its own flag.

A cheater produces superhuman outcomes from suspiciously mechanical inputs. A legitimate world-class player produces superhuman outcomes from demonstrably complex, consistent, human inputs. The outcomes look the same from the outside. The inputs do not.

This holds for both input types. Whether the cheat is a mouse aimbot, a controller-side aim-assist exploit, or a macro firing on a gamepad, the principle is identical: mechanical perfection that does not match biological reality.

---

The Adversarial Problem, Taken Seriously

Any behavioral system has to assume someone will try to defeat it. If we are honest, this is the part that decides whether the whole idea is worth building. Three attacks matter.

Input injection. Synthesize mouse or stick events that mimic human curves and feed them to the game. The countermeasure pairs directly with what Vera already does: capture as close to the hardware as possible, below the layer where software injects. Injected events also tend to betray themselves through quantization, timestamps that snap to frame or poll boundaries with a regularity real hardware interrupts do not have. Genuine human input is jittery at the microsecond level. Synthetic input usually is not, unless the attacker goes out of their way to add noise that itself has to be modeled correctly.

Replay. Record a legitimate player's inputs and play them back. The countermeasure is session-specific entropy: bind the input stream to this match's state. Replayed inputs will not correlate with the enemy positions, round timing, and recoil patterns of a game they were not recorded in. The moment you require inputs to be consistent with game events, a generic replay falls apart.

ML-generated humanized inputs. This is the real frontier. Train a model on legitimate player data to emit cheat outputs that reproduce human kinematics, including the tremor band and the ex-Gaussian tail. It is coming whether we like it or not.

Our honest position: behavioral space is high-dimensional, and a forged session has to be self-consistent across all of it at once. Match the tremor and you still have to match the submovement structure, the Fitts throughput, the dual-thumb interference, the way the signature drifts as a real player tilts and fatigues across a session, and the correlation to game state, all simultaneously and all consistent with one specific person's history. The bar also rises as you collect more genuine baseline data. But high-dimensional is not the same as unbeatable, and we are not going to pretend otherwise. Instinct is a starting point, not a proof.

---

What Vera Would Publish, and What It Never Would

If this layer ever ships, it ships inside the same constraint as everything else we build: neutral observation, no verdicts. We wrote about why in Neutrality Is a Product Decision, and behavioral data makes that discipline more important, not less.

What Vera would publish is inspectable evidence:

• Reaction-time distribution this session: mu 197 ms, sigma 24 ms, tau 41 ms. Consistent with this player's 142-session baseline.
• Input entropy: 94th percentile for verified humans at this rank.
• Crosshair-to-target correlation with enemy positions: within expected range for this experience level.
• Three sessions this month fell outside this player's established envelope. Linked here for inspection.

What Vera would never publish is a guilt score or an accusation. The whole point is to hand communities, organizers, and players themselves something they can read and argue with, not a verdict from a black box. A flag is an invitation to look, never a sentence.

---

The Part That Actually Excites Us

It is not the detection story. It is the verification story.

Think about what a verified behavioral profile would mean for a pro: hundreds of sessions of recorded input, cross-referenced with game history, publicly inspectable. That is not just proof they were not cheating in one match. It is proof the mechanics are real. That the thousands of hours exist in the data. That the skill is demonstrably theirs.

A rising talent could show their mechanical profile is elite before they have won anything. An accused player could point to years of consistent behavioral data, data that existed before anyone accused them of anything, instead of arguing against a narrative in a forum thread. We have written about how expensive that fight is in The Accusation Economy. A sponsor could look at something deeper than a highlight reel.

That fight is not hypothetical. In a $110,000 Call of Duty: Vanguard tournament, the Warzone pro Flxnked was nearly disqualified after a rival submitted a clip that appeared to show wallhack overlays on his stream. Admins ruled it photoshopped after analysis, but he spent the event answering a doctored few seconds instead of competing. A single artifact is cheap to fake and easy to weaponize. A deep record that already existed, public and inspectable, before anyone was angry, is far harder to wave away.

You can picture the structure as tiers:

• Self-comparison. Is this session consistent with this player's own history?
• Cohort comparison. Does this player's input complexity match others at their stated rank? A Radiant outcome from Silver-tier input complexity is worth a look.
• Population baseline. What does "human" look like across tens of thousands of verified sessions?
• Elite reference anchors. With consent, pros submit reference sessions that become the gold standard for what legitimately elite play looks like in the data.

That last tier is the one that turns detection into something better: the ability to prove your mechanics live in the same behavioral space as people we already know are clean.

We called Vera's first layer a reputation ledger written in cryptographic receipts. This second layer would be something else: a reputation ledger written in muscle memory. And muscle memory is one of the hardest things to fake, because you cannot shortcut the hours that built it. Not impossible, nothing is, but expensive, and measurable.

That is true whether those hours were spent dragging a mouse across a mousepad or grinding thumbstick adjustments until the movement becomes automatic. The controller-native pro scene has historically had fewer verification tools, and cross-platform titles are a growing share of organized play. The players competing there deserve the same quality of evidence as anyone else.

---

Where This Sits for Vera Right Now

This is exploratory. We are not announcing a product. We are thinking out loud, in public, because the people this would affect most should help decide whether it is worth building at all.

The open questions are real. Privacy is the obvious one. System-state recording is bounded: we look at what is running, not at what you are doing. Your input signature is more personal than that. How it is stored, who can touch it, and what else it could be used for are central questions, not footnotes. Baseline complexity is another, especially on controller, where hardware varies enormously and a model has to account for the device before it can characterize the human behind it. And the adversarial arms race does not stop because you changed the battlefield.

We have made the broader case for why proof beats reputation in Reputation Shouldn't Need a Publicist, and sketched the system-profile side of all this in What Your Setup Says About You. This piece is the input layer of that same argument.

---

We Want to Know What You Think

We are genuinely uncertain how much competitive players want this, and we want to know.

If you have ever been falsely accused, or watched someone you know go through it, would behavioral data to point to change anything? Is the privacy tradeoff worth it to you? Would you join a verified reference program, submitting sessions that could become the baseline for what legitimate elite play looks like?

Or does this feel like overreach? The cure being worse than the disease?

We are not going to build this if the community does not see the value. The whole point of Vera is to serve competitive integrity, and that means listening to the people competing, on every platform, with every input device.

If you have thoughts, we want them. Hit the Share an Idea button. Tell us what you would build, and tell us what you are worried about. We read everything.

This is your ecosystem. This proof layer, if it ever gets built, should be built for you, whether your hands are on a mouse or a controller.

---

Vera's current platform, system-state recording and public proof profiles, is available now. If you are competing seriously and want to start building a verifiable record, you can get started at veraproject.xyz.