In-scope vulnerabilities

The following vulnerabilities are considered in-scope:

• Reentrancy
• Reordering
• Overflows and underflows
• Stealing or loss of funds
• Unauthorized transaction
• Transaction manipulation
• Attacks on logic (behavior of the code is different from the business description)

All in-scope vulnerability reports must include a Proof of Concept (PoC) that demonstrates real-world impact. Submissions without a PoC will not be considered.

Out-of-scope vulnerabilities

Vulnerabilities identified in out-of-scope resources are generally not eligible for rewards unless they present a significant business risk, as determined at our sole discretion.

The following items are generally excluded from reward eligibility due to insufficient severity or lack of relevance to the program’s defined scope:

• Redundant code
• Gas optimizations
• Best practice issues
• Old compiler version
• Code style guide violations
• The compiler version is not locked
• Vulnerabilities in imported contracts
• Theoretical or purely speculative exploits without demonstrated business impact

• Avoid using application scanners that generate massive traffic. Automated scanning results without clear analysis will not be considered
• Avoid causing any disruption to the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Bounty reward is determined by proportion of potential damage and is limited by a severity rewards range
• Non-production vulnerabilities are limited to High severity
• Do not access or modify data belonging to other users
• Perform testing only within the scope described in this program
• Do not exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam methods
• Do not spam forms or account creation flows using automated tools
• Remain compliant with all applicable laws and operate strictly within the defined testing scope
• Do not share details of any vulnerabilities with anyone outside the authorized team without explicit written permission from the organization

• All information related to this program, including any discovered vulnerabilities (resolved or unresolved), must be kept strictly confidential. Public disclosure — including partial disclosure or discussion in any public forum, channel, or platform — is strictly prohibited without the organization's explicit written consent

We value all valid reports that help us strengthen our security. To qualify for a monetary reward, the following eligibility conditions must be fulfilled:

• You must be the first reporter of a vulnerability
• The vulnerability must be a qualifying (in-scope) vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery
• You must send a clear textual description of the report and detailed steps to reproduce the issue. Include attachments such as screenshots or proof-of-concept code if necessary
• You must not be a former or current employee of our company or any of its contractors
• Include clear and concise reproduction steps to help us verify and assess the impact of the reported issue efficiently