> For the complete documentation index, see [llms.txt](https://moow.gitbook.io/moow-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moow.gitbook.io/moow-whitepaper/infrastructure/anti-cheating.md).

# Anti-cheating

{% hint style="info" %}
MOOW is a heart rate based game that aims to promote physical activity and healthy lifestyles. However, cheating undermines the spirit of fair play and can have a detrimental effect on the integrity of the game. 
{% endhint %}

## Strategies that MOOW uses to prevent cheating

### Unique Device Identifiers

MOOW uses unique device identifiers, such as IMEI numbers and IP addresses, to identify and track each user. This strategy helps to prevent users from using the same device to create multiple accounts, ensuring that each account represents a unique player.

### Heart Rate Data Validation

Heart rate data validation is essential to ensure the authenticity of the data and prevent artificially generated data from being used to gain an unfair advantage. MOOW validates heart rate data by comparing it against a baseline or expected range of values for a given activity level.

### Monitoring User Behavior

Monitoring user behavior helps detect fraudulent patterns or anomalies within the game. MOOW monitors user behavior to identify users who consistently achieve unusually long eligible pulse zones.

### Machine Learning Algorithms 

Machine learning algorithms helps prevent cheating by analyzing heart rate data and identifying patterns that may indicate fraudulent behavior. These algorithms detects anomalies in heart rate data, identify patterns in user behavior, and predict the likelihood of fraud based on historical data.

### Punishment

{% hint style="info" %} <mark style="color:red;">Any kind of use of multiple accounts is prohibited!</mark>
{% endhint %}

{% hint style="info" %} <mark style="color:red;">Any kind of manual heart rate data reporting is prohibited!</mark>
{% endhint %}

{% hint style="info" %} <mark style="color:red;">It's easy to connect multiple accounts to one heart rate data set.</mark> \ <mark style="color:red;">But just as easy to do, it's just as easy to catch.</mark>\ <mark style="color:red;">**If you get caught, you are banned permanently, and your assets will be confiscated.**</mark>
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://moow.gitbook.io/moow-whitepaper/infrastructure/anti-cheating.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.