Brink

Brink is a fully permissionless, non-custodial, and decentralized network that provides automated execution of transactions to the DeFi community. For more information about Brink, please visit our developer documentation and our website.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

• Potential theft or loss of value for all proxy accounts. This would be any attack that affects all accounts created in the system.

• Potential theft or loss of value for an individual proxy account. This would be any attack that affects a single account based on an individual account owner action, such as signing a message to one of the Brink verifiers that allows the account to be compromised.

• An attack that invalidates signed orders, but does not result in any direct theft or loss of value.

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 Immunefi’s Vulnerability Severity Classification System, Brink classifies the following vulnerabilities as follows. In case of discrepancy, the one below will be followed.

• Critical

  • Potential theft or loss of value for all proxy accounts. This would be any attack that affects all accounts created in the system.

• High

  • Potential theft or loss of value for an individual proxy account. This would be any attack that affects a single account based on an individual account owner action, such as signing a message to one of the Brink verifiers that allows the account to be compromised.

• Medium

  • An attack that invalidates signed orders, but does not result in any direct theft or loss of value.

• Low

  • An attack with some level of consequence, and is one of the three:
    • highly unlikely
    • low impact on users
    • bug in brink-sdk that results in an unintended user action

Special Rewards : Gas improvements

• $1 per gas saved or any smart contract change that doesn’t affect functionality or compromise security. This only applies to changes in brink-core and the “limit swap” verifiers in brink-verifiers

Payouts are handled by the Brink team directly and are denominated in USD. However, payouts are done in ETH or USDC/DAI at the discretion of the team.

Please note that only low severity vulnerabilities will be considered for https://github.com/brinktrade/brink-sdk

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

All folders with “Test” or “Dummy”, https://github.com/brinktrade/brink-verifiers/blob/master/contracts/Verifiers/CancelVerifier.sol and https://github.com/brinktrade/brink-verifiers/blob/master/contracts/Verifiers/TransferVerifier.sol are out of scope.

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.

Smart Contracts/Blockchain

• Loss of user funds staked (principal) by freezing or theft
• Loss of governance funds
• Theft of unclaimed yield
• Freezing of unclaimed yield
• Temporary freezing of funds for any amount of minutes/hours/days
• Unable to call smart contract
• Smart contract gas drainage
• Smart contract fails to deliver promised returns
• Vote manipulation
• Incorrect polling actions

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • 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

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
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Potential theft or loss of value for all proxy accounts. This would be any attack that affects all accounts created in the system.
• Potential theft or loss of value for an individual proxy account. This would be any attack that affects a single account based on an individual account owner action, such as signing a message to one of the Brink verifiers that allows the account to be compromised.
• An attack that invalidates signed orders, but does not result in any direct theft or loss of value.
• An attack with some level of consequence, and is one of the three:
  • highly unlikely
  • low impact on users
  • bug in brink-sdk that results in an unintended user action

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