# 🐛 | Bug Bounties

<figure><img src="/files/4wRx2r4zdg23IkHZaOOz" alt=""><figcaption></figcaption></figure>

The <mark style="color:green;">**EasyX**</mark> bug bounty programs primarily concentrate on identifying vulnerabilities in our smart contracts, websites, and apps. Our main objective is to prevent any potential loss of user funds, whether it's through direct draining of locked funds or social engineering attacks that manipulate users into redirecting or signing malicious transactions.

### **Website and Apps** (Level - Payout)

| Bug Level                                    | Payout                 |
| -------------------------------------------- | ---------------------- |
| <mark style="color:red;">**Critical**</mark> | Up to **$10,000** USDС |
| <mark style="color:orange;">**High**</mark>  | Up to **$5,000** USDС  |
| <mark style="color:yellow;">**Low**</mark>   | Up to **$500** USDС    |

{% hint style="success" %} <mark style="color:green;">**Bug Levels explained**</mark>

<mark style="color:red;">**Critical**</mark>

* The bug causes a potential & notable loss of funds for the user and/or the platform.

<mark style="color:orange;">**High**</mark>

* Serious impact on the usage of the product.
* A large number of users, products, or items is concerned.
* Non-trivial functionality is broken or unavailable, and no workaround exists.

<mark style="color:yellow;">**Low**</mark>

* Minimal impact on the usage of the product.
* The product shows unintended behavior, but the general usage is not affected.
* Few users, products, or items are concerned.
* A feature/piece of functionality is broken or unavailable, but an easy workaround solves the problem.
  {% endhint %}

### **Out of Scope Bounties & Rules**

{% hint style="warning" %}
The following vulnerabilities are <mark style="color:orange;">**excluded**</mark> from the rewards for this Bug Bounty program:
{% endhint %}

* Attacks that the reporter has already exploited themselves, leading to damage
* Attacks requiring access to leaked keys/credentials
* Attacks requiring access to privileged addresses (governance, strategist)
* Any testing with mainnet or public contracts; all testing should be done on private testnets
* Attempting phishing or other social engineering attacks against our employees and/or customers
* Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
* Any denial of service attacks
* Automated testing of services that generates significant amounts of traffic
* Public disclosure of an unpatched vulnerability in an embargoed bounty

### Websites and Apps

* Theoretical vulnerabilities without any proof or demonstration
* Content spoofing / Text injection issues
* Captcha bypass using OCR
* CSRF with no security impact (logout CSRF, change language, etc.)
* Server-side information disclosure such as IPs, server names, and most stack traces
* Vulnerabilities used to enumerate or confirm the existence of users or tenants
* Vulnerabilities requiring unlikely user actions
* Vulnerabilities primarily caused by browser/plugin defects
* Any vulnerability exploit requiring CSP bypass resulting from a browser bug
* URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
* Attacks requiring privileged access from within the organization

### **Bounty Links**

{% hint style="success" %}
Please submit any of the bugs you find on <mark style="color:green;">**EasyX**</mark> using this link [<mark style="color:green;">**here**</mark>](https://docs.google.com/forms/d/e/1FAIpQLSdIwcdBHc8Z-2r2g8kwDaycWIqJU5-hX-oQmILxPvf2azWbjA/viewform).
{% endhint %}


---

# 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.easyx.trade/easyx/developers/or-bug-bounties.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.