Balanced is a DAO (Decentralized Autonomous Organization) consisting of a decentralized balance sheet of ICX collateral, with the vision of creating a vibrant ecosystem of tokens pegged to the value of real-world assets. It allows users to mint, borrow, and retire pegged assets, while also providing market makers with clearly defined arbitrage opportunities. The initial iteration of Balanced will support the minting and retiring of USD-pegged assets referred to as Balance Dollars (bnUSD).
For further information about Balanced, you can check their white paper here: https://docs.balanced.network/technical/white-paper.
The bug bounty program is focused around their smart contracts and is mostly concerned with the loss of user funds and the shutdown of the contracts.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
In addition to the Immunefi Severity Classification System, the Balanced Bug Bounty Program considers any vulnerability resulting in the cessation of functionality of a smart contract to be of high severity. In the event of conflict between this rule and the Immunefi Severity Classification System, this rule will prevail.
Critical vulnerabilities are further capped at 10% of economic damage, primarily focusing on the funds at risk, though consideration for branding and PR may also be applied, only at the discretion of the team. However, there is a minimum reward of USD 50 000.
Payouts are handled by the Balanced team directly and are denominated in USD. However, payouts are done in ICX. In the event of multiple submissions of the same vulnerability, the first complete bug report is the only one that shall receive a reward.
- Up to USD $200,000
- USD $2,000
Assets in scope
- Smart Contract - Balanced GovernanceType
- Smart Contract - Balanced LoansType
- Smart Contract - Balanced DEXType
- Smart Contract - Balanced RewardsType
- Smart Contract - Balanced ReserveType
- Smart Contract - Balanced DividendsType
- Smart Contract - Balanced DAOfundType
- Smart Contract - Balanced RebalancingType
- Smart Contract - Balanced DollarType
- Smart Contract - Balance TokenType
Only the development branch is within the scope of this bug bounty program. Bug reports in any other branch will not be accepted.
We are especially interested in receiving and rewarding vulnerabilities of the following types:
- Logic errors
- including user authentication errors
- Solidity/EVM details not considered
- including integer over-/under-flow
- including unhandled exceptions
- Trusting trust/dependency vulnerabilities
- including composability vulnerabilities
- Oracle failure/manipulation
- Novel governance attacks
- Economic/financial attacks
- including flash loan attacks
- Congestion and scalability
- including running out of gas
- including block stuffing
- including susceptibility to frontrunning
- Consensus failures
- Cryptography problems
- Signature malleability
- Susceptibility to replay attacks
- Weak randomness
- Weak encryption
- Susceptibility to block timestamp manipulation
- Missing access controls / unprotected internal or debugging interfaces
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)
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Basic economic governance attacks (e.g. 51% attack)
- Lack of liquidity
- Best practice critiques
- Sybil attacks
The following activities are prohibited by 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