Skip to main content

Bot prevention and anti-cheating measures

Learn about our view on bots and cheating, and how we protect race integrity with locked inputs, tamper-evident logs, and verification.

Written by VPR
Updated over a week ago

In competitive online games, “bots” usually means automated scripts that try to gain an unfair advantage. VPR is primarily a strategy game built around choosing pigeons, reading conditions, and making long-term decisions through racing and breeding, so automation does not let someone “force” a win.

At the same time, like any online platform, we cannot promise that nobody will ever attempt automation. What matters is what automation could realistically achieve in VPR, and what it cannot.

Why bots and cheating are limited in VPR

Pigeons are real, owned assets

Every pigeon in VPR is an NFT owned by a wallet, with verifiable ownership and a permanent history. This means you cannot generate unlimited “fake” pigeons through automation, because ownership and supply are enforced.

Race outcomes are protected from manipulation

Even if someone tries to automate actions around the platform, the race result itself is designed to be tamper-resistant and verifiable after the race.

How we protect races from manipulation

VPR uses a fairness system that locks race inputs before the race and records a verifiable race timeline.

  • Randomness and weather are locked upfront using a commit–reveal approach and a weather snapshot, so inputs cannot be rerolled or quietly changed mid-race.

  • Race events are logged and cryptographically chained, so changes after the finish would be detectable.

  • Deterministic replay and verification: the same event log, seed, and engine version reproduce the same result, and a verification tool is planned so players can independently validate outcomes.

If you want the deeper technical explanation, see: Fairness and competitive integrity

What to do if something looks suspicious

If something feels off, contact us via the Help Center chat or email us at [email protected]. Share as much context as possible (race ID, time, usernames, screenshots).

Did this answer your question?