ZetaChain Blockchain Software: Program info

The list is not limited to the following submissions but it gives an overview of what issues we care about:

• Protocol insolvency
• Compromise of the “TSS Address” that leads to unauthorized transactions
• Unintended minting of ZETA token.
• Stealing or loss of funds
• Unauthorized transaction
• Transaction manipulation
• Price manipulation
• Fee payment bypass
• Balance manipulation
• Contracts execution flows
• Consensus flaws
• Peer-to-peer network flaws
• Cryptographic flaws

Rewards for critical vulnerabilities are capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team.

• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• All testing should be done on private testnets
• 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 break any law and stay in the defined scope
• 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

• 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.

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