This repository is specifically tailored for active development. As a result, scripts and web applications, including testing tools such as Typescripts, are considered out of scope. Only smart contracts fall within the scope of this bug bounty program.

CAVEAT

Vulnerabilities found in pre-release or experimental code, including the ZetaChain toolkit (https://github.com/zeta-chain/toolkit), are generally considered low severity as these are intended for development use only and not deployed in production. Valid reports for critical issues that demonstrate real exploitability in a production context may still be considered at our discretion.

IN-SCOPE: SMART CONTRACT VULNERABILITIES

We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality:

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

OUT OF SCOPE: SMART CONTRACT VULNERABILITIES

• Theoretical vulnerabilities without any proof or demonstration
• Old compiler version
• The compiler version is not locked
• Vulnerabilities in imported contracts
• Code style guide violations
• Redundant code
• Gas optimizations
• Best practice issues
• Testing and development scripts
• Moderately Sensitive Information Disclosure (e.g., non-sensitive logs or generic error stack traces without personal data or credentials)

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• Don’t spam forms or account creation flows using automated scanners
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Risk severity is determined by the likelihood of exploitation, the risk appetite of ZetaChain, and the resulting damage.
• Request amplification and DDoS attack severity is determined by potential disruption to services i.e. if an attack blocks operations for more than two weeks, it is considered high severity otherwise not.
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• If you accidentally access other user data or personal information, stop testing immediately and include full details in your report.
• Your proof-of-concept must demonstrate an actionable scenario that shows real impact or exploitability.
• For vulnerabilities in the ZetaChain protocol, only the single highest severity finding will be rewarded per researcher per round.

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps
• Estimated bounty ranges will depend on severity, impact, and quality of the report.
• Findings must demonstrate a clear understanding of the ZetaChain security architecture. Reports based on partial implementations or unrealistic assumptions that do not reflect how ZetaChain actually works may not be eligible for a reward.
• AI-generated proof-of-concepts (PoCs) that do not include detailed architectural context and clear steps to demonstrate real impact may not qualify for a bounty.
• Submitting repeated low-quality or duplicate reports, or spamming the program with findings that do not meet the scope or quality standards, may result in disqualification from receiving any rewards.

• Report any suspected vulnerability promptly.
• Do not attempt to exploit a vulnerability without prior authorization.
• Do not publicly disclose a vulnerability before it is reported and patched.
• Do not access data or systems beyond the scope of the vulnerability.
• Do not use social engineering techniques.
• Do not attempt to access accounts or personal data of users.