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

Issues that are not directly caused by bugs in Burrow’s smart contracts should be considered out of scope. This includes:
1. bad debt due to rapid changing market conditions
2. price manipulation due to external data source exploit

Burrow is a decentralized, non-custodial pool-based interest rates platform that enables users to supply assets to earn interest, and to borrow against them to unlock liquidity. Burrow is similar in nature to Aave, Compound, and other pool-based protocols. Burrow runs natively on the NEAR blockchain, a layer 1, proof-of-stake, sharded blockchain with a WebAssembly runtime.

Smart contract fails to deliver promised returns, but doesn’t lose value

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for at least 24 hours

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Burrow Smart Contracts

Rewards are distributed according to the impact of the vulnerability based on the [ Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. 

All Critical, High, and Medium bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. In addition, all bug reports must come with a suggestion for a fix in order to be considered for a reward. 

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 25 000 for Critical smart contract bug reports.

High smart contract vulnerabilities are capped at 10% of economic damage, primarily based on value at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward for high vulnerabilities of __USD 5 000__.

Medium smart contract vulnerabilities are capped at 10% of economic damage, primarily based on value at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward for medium vulnerabilities of __USD 1 000__.

Known issues highlighted in the following audit reports are considered out of scope:
- [https://docs.burrow.cash/product-docs/introduction/audits-and-risks](https://docs.burrow.cash/product-docs/introduction/audits-and-risks)

Burrow requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. For individuals, the information needed is proof of address and government-issued photo ID for each authorized representative. For companies, the requirements will vary based on the type of the entity. 
Payouts are handled by the __Burrow__ team directly and are denominated in USD. However, payouts are done in __USDC__ or __USDT__.

Burrow

Codebase