Azuro utilizes smart-contracts to build a decentralized betting protocol deploying an innovative solution for liquidity provision and allocation. Instead of prediction markets’ rather simple p2p model, Azuro uses a peer-to-pool model.
In that model a novel liquidity pool design called “The Liquidity Tree” is introduced.
As a result betting becomes transparent and trustless, while depth of betting events, markets and UX remains as good as it gets. For more information about Azuro Protocol, please visit https://azuro.org/.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.1. This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All Critical and High Smart Contract bug reports require a suggestion for a fix to be eligible for a reward.
The following vulnerabilities are not eligible for a reward:
- Oracles/Maintainer manipulation, for example: choosing the wrong outcome as a winner or incorrect odds. It is solved separately by Azuro’s governance contracts
- Gas efficiency improvements
- Limited number of deposits in Liquidity Pool
- All vulnerabilities marked in Pessimistic security review are not eligible for a reward.
- All vulnerabilities in the Azuro V1 Audit Report are not eligible for a reward.
Payouts are handled by the Azuro Protocol team directly and are denominated in USD. However, payouts are done in USDT.
- USD $21,500
- USD $7,000
- USD $2,000
- USD $1,000
Assets in scope
- Smart Contract - Core ProxyType
- Smart Contract - Core ImplementationType
- Smart Contract - LP ProxyType
- Smart Contract - LP implementationType
- Smart Contract - AzuroBet ProxyType
- Smart Contract - AzuroBet ImplementationType
All smart contracts of Azuro Protocol can be found at https://github.com/Azuro-protocol/Bug-Bounty/tree/2cb0c6a1b49954cf523f49a74b05b6a58c5317ff. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If an impact can be caused to any other asset managed by Azuro Protocol that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.
Impacts in scope
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Unfair distribution of profit between Liquidity ProvidersHighImpact
- Smart contract unable to operate due to lack of fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Unbounded gas consumptionMediumImpact
- Smart contract fails to deliver promised returns, but doesn’t lose valueLowImpact
Out of Scope & Rules
The following vulnerabilities are excluded from the rewards for this bug bounty program:
- 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)
Smart Contracts and Blockchain
- Incorrect data supplied by third party oracles
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
- Centralization risks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- Any testing with pricing oracles or third party smart contracts
- 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