# Violation Tolerance

Each slashable offense has its own tolerance levels as follows:

<table><thead><tr><th width="305">Offense</th><th width="117">Tolerance</th><th>Note</th></tr></thead><tbody><tr><td><strong>Exact duplicate posts</strong></td><td>5</td><td>Leads to progressive bans after tolerance is reached</td></tr><tr><td><strong>User-Level duplicates</strong></td><td>5</td><td>Violation counter resets upon slashing</td></tr><tr><td><strong>Network-Level duplicates</strong></td><td>10</td><td>Violation counter resets upon slashing</td></tr><tr><td><strong>Non-original content</strong></td><td>5</td><td>Violation counter resets upon slashing</td></tr><tr><td><strong>AI-Generated content</strong></td><td>3</td><td>Violation counter resets upon slashing</td></tr></tbody></table>

All of these stats are visible on the user profile page under **Violations.** Your stats will look something like this:

<figure><img src="/files/6fOeK6WqfJwcNWPN4btj" alt="" width="212"><figcaption><p>Sample Violations count</p></figcaption></figure>

## Exact Duplicate Case

We have a very low tolerance for exact duplicates. This means uploading the exact same piece of data more than once either on a single account or across multiple accounts.

Unlike other offenses, exact duplicate posts do not lead to slashing right after the tolerance is reached. Instead, further offenses lead directly to progressive time bans culminating in a permanent ban from the network.

#### Example

Say a malicious user takes a photo of a brick and tries uploading it twice for different tasks. While the first image will be accepted, the second image will be rejected and the user's exact match violation  count will increase by 1.&#x20;

If they continue to engage in this behavior - either with the same image or different images - their violation count will continue to increase until it reaches the limit.

When the limit is reached, further offenses trigger the following cases:

* **1st offense above tolerance:** 24-hour ban
* **2d offense above tolerance:** 48-hour ban
* **3rd offense above tolerance:** Permanent ban


---

# Agent Instructions: 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:

```
GET https://docs.eidon.ai/the-network/slashing-mechanism/violation-tolerance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.