Belt Finance

Submit a Bug
14 July 2021
Live since
No
KYC required
$200,000
Maximum bounty

Program Overview

Belt.fi is a stableswap AMM protocol that incorporates multi-strategy yield optimizing on Binance Smart Chain (BSC) and HECO Chain with low fees/slippage that also provides aggregation through vault compounding, lending and yield generation for maximum returns.

Belt Finance’s stableswap AMM offers users the most efficient way to swap their stablecoins by offering significantly lower slippage than alternative swap protocols. Belt Finance is also focused on giving users the best yield through a combination of trading fee rewards and a multi-strategy optimization vault system. By utilizing multiple strategies simultaneously, Belt.fi minimizes dependence on any one protocol while generating users the best possible yield rates in DeFi. This also protects users from low-liquidity withdrawal issues.

For more information about Belt Finance, please visit their website at https://belt.fi/.

The bug bounty program covers its smart contracts and website and is focused on the prevention of:

  • Miscalculating/misjudging asset values stored in various protocols
  • Loss of user funds staked (principal) by freezing and/or theft
  • Flashloan attack activity
  • Thefts of unclaimed yield of any amount
  • Website is unresponsive/ taken over
  • Access to sensitive user information without authorization
  • Temporary freezing of funds through exploits/attacks for any amount of time
  • Unable to call smart contract
  • Smart contract fails to function as intended

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.

Bug reports must come with the following in order to be considered for a reward:

  • Proof of Concept (PoC) - All bug reports
  • Suggestions for a fix - Critical reports only

Critical smart contract vulnerabilities are further capped at 10% of economic damage, primarily taking into consideration the funds at risk, though other considerations may also be accounted for, such as branding and PR, under the discretion of the Belt Finance team.

High smart contract vulnerabilities involving theft of yield are further capped at 10% of economic damage, but with a minimum reward of USD 6,000. For vulnerabilities involving temporary freezing of funds, the full reward is only paid out if the funds are locked for at least 30 minutes. For temporary freezing below that, the reward is adjusted pro rata rounded up to the nearest minute. However, there is also a minimum reward of USD 6,000.

Web and app vulnerabilities will be counted as critical if they achieve any of the impacts listed in the Impacts in Scope section below. The reward amount is dependent on the economic damage that could be inflicted.

Payouts are handled by the Belt Finance team directly and are denominated in USD. All payouts are done in USDT.

Smart Contract

Critical
Level
Up to USD $200,000
Payout
PoC Required
High
Level
Up to USD $40,000
Payout
PoC Required
Medium
Level
USD $3,000
Payout
PoC Required

Websites and Applications

Critical
Level
Up to USD $50,000
Payout
PoC Required

Assets in scope

SingleStrategyToken = SST in short

SingleStrategyToken2 = SST2 in short

VoidStrategyTokenV2 = VST in short

Only web/app vulnerabilities that affect the homepage as well as the pages explicitly listed in the assets in the scope table are considered as in-scope of the bug bounty program.

For further reference, the GitHub of BeltFinance containing the smart contracts listed here are found on https://github.com/BeltFi/belt-contract.git. However, only the smart contracts explicitly listed in the table are considered as in-scope of the bug bounty program.

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 Contract

  • Any governance voting result manipulation
    Critical
    Impact
  • Permanent freezing of funds
    Critical
    Impact
  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
    Critical
    Impact
  • Protocol Insolvency
    Critical
    Impact
  • Miner-extractable value (MEV)
    Critical
    Impact
  • Theft of unclaimed yield
    High
    Impact
  • Permanent freezing of unclaimed yield
    High
    Impact
  • Temporary freezing of funds
    High
    Impact
  • Smart contract unable to operate due to lack of token funds
    Medium
    Impact
  • Block stuffing for profit
    Medium
    Impact
  • Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
    Medium
    Impact
  • Theft of gas
    Medium
    Impact
  • Unbounded gas consumption
    Medium
    Impact

Websites and Applications

  • Ability to execute system commands
    Critical
    Impact
  • Extract Sensitive data/files from the server such as /etc/passwd
    Critical
    Impact
  • Taking Down the application/website
    Critical
    Impact
  • Stealing User Cookies
    Critical
    Impact
  • Signing transactions for other users
    Critical
    Impact
  • Bypassing Authentication
    Critical
    Impact
  • Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)
    Critical
    Impact
  • Redirection of user deposits and withdrawals
    Critical
    Impact
  • Direct theft of user funds
    Critical
    Impact
  • Wallet interaction modification resulting in financial loss
    Critical
    Impact
  • Tampering with transactions submitted to the user’s wallet
    Critical
    Impact
  • Submitting malicious transactions to an already-connected wallet
    Critical
    Impact

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)

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

Websites and Apps

  • Theoretical vulnerabilities without any proof or demonstration
  • Content spoofing / Text injection issues
  • Self-XSS
  • Captcha bypass using OCR
  • CSRF with no security impact (logout CSRF, change language, etc.)
  • Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
  • Server-side information disclosure such as IPs, server names, and most stack traces
  • Vulnerabilities used to enumerate or confirm the existence of users or tenants
  • Vulnerabilities requiring unlikely user actions
  • URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
  • Lack of SSL/TLS best practices
  • DDoS vulnerabilities
  • Attacks requiring privileged access from within the organization
  • Feature requests
  • Best practices

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