Belt Finance

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

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 Contracts

• Unintended behavior of gov functions
• Miscalculating/misjudging asset values stored in various protocols
• Loss of user funds staked (principal) by freezing or theft
• Flashloan attack activity
• Thefts and freezing of unclaimed yield of any amount
• Temporary freezing of funds through exploits/attacks for any amount of time
• Unable to call smart contract
• Smart contract fails to function as intended

Websites/Apps

• Transaction issues based on inputted values and actually transacted values via swap (whether the user inputted value accurately is converted to transaction data)
• Whether the accurate, wanted transaction occurs (e.g. the stake button should not call an unstake transaction)
• Redirected funds by address modification
• Users spoofing other users
• Website goes down/ taken over
• Access to sensitive user information without authorization

We are especially interested in receiving and rewarding vulnerabilities of the following types, as long as they result in the impacts highlighted in the Impacts in Scope section:

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

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

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