Alpha Finance

Submit a Bug
20 April 2021
Live since
KYC required
Maximum bounty

Program Overview

Alpha Finance Lab is building an ecosystem of DeFi products (the Alpha ecosystem), consisting of innovative building blocks that capture unaddressed demand in key pillars of the financial system. These building blocks will interoperate, creating the Alpha ecosystem that will be an innovative and more capital efficient way to banking in DeFi.

Alpha Homora is Alpha Finance Lab’s first product and DeFi’s first leveraged yield farming product that captures the market gap in lending, one of the key pillars of the financial system.

Further information about Alpha Finance can be found here

The bug bounty program is focused around their smart contracts and is mostly concerned with the loss of user funds and is further secured by the Armor Alliance Bug Bounty Challenge.

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.

Critical vulnerabilities are capped at 10% of economic damage. This includes a bounty of up to USD 500,000 from the Alpha Finance team and an additional bounty of up to USD 250,000 from the Armor Alliance Bug Bounty program.

Payouts are handled by the Alpha Finance team directly and are denominated in USD. However, payouts are done in ALPHA for payouts up to USD 500,000. All payments for critical vulnerabilities are capped at 10% of economic damage. For critical level smart contract vulnerabilities, payouts of up to USD 500,000 will take place with an upfront payout of up to USD 100,000 and USD 50,000 monthly vesting thereafter. For payouts above USD 500,000the critical bug report will receive the remaining reward in ARMOR with a vesting period of up to 24 months under the Armor Alliance Bug Bounty Challenge provided by ArmorFi, resulting in a total maximum payout of USD 750,000.

Smart Contracts and Blockchain

up to USD $750,000
USD $20,000
USD $5,000
USD $1,000
USD $0

Assets in Scope

Smart contract - Alpha Homora v1 (ETH)
Smart contract - Alpha Homora v1 (BSC)
Smart Contract - Alpha Staking
Smart Contract - Alpha Homora v2

Prioritized Vulnerabilities

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

Smart Contracts/Blockchain:

  • Re-entrancy
  • 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