[New Bug Bounty] Exzo Network Has Launched Bug Bounty With Up to $100,000 Reward Per Critical Vulnerability

Alex Horlan
СТО HackenProof
2 Minutes Read

Meet Exzo Network

Exzo Network is a web3 infrastructure protocol with the mission of being the go to blockchain solution for enterprises, Web3 gaming, and DeFi.

Check Out The Rewards

If you find a vulnerability according to the bounty rules, Exzo Network will reward you:

  • Critical: $25,000 – $100,000
  • High: $10,000 – $20,000
  • Medium: $500 – $2,500
  • Low: $100 – $500

Join The Bounty Hunt

There are 3 asset types to scope!

  • Web
  • API
  • Protocol

Make sure your reports contain info about these incidents:

P4:

A vulnerability that could compromise the safety of any user’s or validator’s funds or fees. Subversion of the DEX trading logic A vulnerability that could severely undermine the token economy or trading. Key generation, encryption, signing, and verification-related security vulnerabilities. The malleability of transactions or spoofing of transaction origins. Merkle proof vulnerability Manipulation of blockchain validator Remote code execution on any Exzo Network Chain Vulnerabilities that could disrupt the Exzo Network’s blockchain Vulnerabilities that could disrupt users staked or delegated funds towards node validators or while operating a node Any vulnerabilities in smart contracts that could lead to loss of funds

P3:

Denial of service of any Exzo Network blockchain Vulnerabilities that could disrupt Blockchain validator and its performances. Vulnerabilities that cause Exzo Network to be unable to respond to users’ queries on orders, transactions, balance etc. Access to disable channels of cross-chain bridge. Denial of service of cross-chain bridge.

P2:

Denial of service of any Exzo Network chain

P1:

Vulnerabilities that could affect Exzo Network related node on stability or availability

To increase your chances of finding a critical bug, read Exzo Network whitepaper here.

Once you’re ready, click here to join the bounty hunt!

Read more on HackenProof Blog