At Integral, our goal is to build the Last Exchange. We have gone through 9 months of careful research & development and 3 completed audits. However, as any of you in development would know, this is never enough! We would benefit from community feedback and scrutiny. Therefore, we partner with immunefi for the Integral Bug Bounty Program (the "Program") incentivizing those dedicated security engineers who can help make Integral safer.
If you have found a vulnerability in our project, it must be submitted through Immunefi's platform. Immunefi will handle bug bounty communications.
See the bounty page at Immunefi for more details on accepted vulnerabilities, payout amounts, and rules of participation.
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.
Smart Contracts and Blockchain
Critical: USD $50,000.
High: USD $10,000.
Medium: USD $2,000.
Low: USD $1,000.
In order to be considered for a reward, all bug reports must include as much information about the vulnerability including:
The conditions on which reproducing the bug is contingent.
The steps needed to reproduce the bug or, preferably, a proof of concept.
The potential implications of the vulnerability being abused.
Payouts are handled by the Integral team directly and are denominated in USD. However, payouts can be done as per the bug bounty hunter’s preference in ETH, stablecoins (e.g DAI, USDT, USDC), or ITGR with vesting.
We are especially interested in receiving and rewarding vulnerabilities of the following types:
including user authentication errors
Solidity/EVM details not considered
including integer over-/under-flow
including unhandled exceptions
Trusting trust/dependency vulnerabilities
including composability vulnerabilities
Novel governance attacks
including flash loan attacks
Congestion and scalability
including running out of gas
including block stuffing
including susceptibility to front-running
Susceptibility to replay attacks
Susceptibility to block timestamp manipulation
Missing access controls / unprotected internal or debugging interfaces
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
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