Integral

At Integral we build products that rival those of centralized exchanges, in service of our self-custodial decentralized homeland and its users. Most importantly, we address these economic injustices by distributing the upside of network effects to our community of users so that using the product means owning the product. Each new product we build creates on-chain stickiness that further counters the centralized exchange product lines.

Further information about Integral can be found here

The bug bounty program is focused around its smart contracts and is mostly concerned with the loss of user funds in their pools.

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

The final reward for critical bounty payouts is capped at 10% of economic damage up to USD 250 000, primarily based on the funds at risk, but with potentially some additional considerations for PR and branding reasons, at the discretion of the team. However, the minimum reward is USD 50 000.

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.

Smart Contract

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