Published on 2026-08-26
Every leaderboard on WikiRacing is public, and public leaderboards invite an obvious question: what's actually stopping someone from typing a fake time straight into the database? The honest answer is a mix of hard technical checks and a few places where the site deliberately settles for good-enough rather than airtight.
A finished race isn't just a click count and a duration — it's saved with the full article-by-article path you actually took. Before any run is accepted, the server checks that the path's length actually matches the claimed click count, that the first and last articles in that path match the start and target you were racing, and that the total time is realistic for that many clicks — under half a second flat, or barely 150 milliseconds a click, and the run is rejected outright. Someone would have to fabricate a consistent, timed path through real Wikipedia articles, not just submit a number.
Casual and daily runs get the path-consistency check above. Ranked duels get something stronger, because ELO is the one number on the site that actually costs someone else something when it moves. Before a ranked win can be applied, the host has to have already recorded that the match happened, and the guest has to independently confirm it from their own side. Neither player alone can push a rating change through — it takes both.
Every write to the database — a finished game, a daily run, a themed-challenge result — is throttled per IP address in the background. A real player racing at normal human speed never gets anywhere near the limit; a script trying to flood the leaderboards with fabricated entries hits a wall fast. The throttling is deliberately built to fail open rather than closed, so a glitch in that system can only ever let a few extra writes through — it can never accidentally block a legitimate player mid-race.
Not everything is locked down equally, on purpose. Badges are awarded based on a client-reported result rather than an independently re-verified one — a soft progression layer, not a leaderboard position, so the cost of getting that wrong is low. Casual and daily leaderboards accept that a genuinely determined player could replay a real, legitimate path with artificially realistic timing to inflate a result — but ranked, the one place where a fake number actively takes something from another player, is the one held to a strict, two-party standard.
Every name above yours on a pair leaderboard, a daily ranking, or the ELO ladder got there by racing the same real Wikipedia everyone else races, with a route that actually holds up when checked. That's the whole point of building the checks in the first place — a podium finish should mean something.