# Bug Bounty

## Program Overview

The bug bounty program covers the Suilend smart contracts (no UI bugs) and is focused on preventing thefts and freezing of funds.

The Suilend smart contracts are fully open-source: [suilend-integration-links](https://docs.suilend.fi/ecosystem/suilend-integration-links "mention").

## Rewards <a href="#rewards" id="rewards"></a>

Rewards are distributed according to the following classifications:

| Severity | Max Prize                                |
| -------- | ---------------------------------------- |
| Critical | 10% of value at risk, up to $250,000 USD |
| High     | $50,000 USD                              |
| Medium   | $10,000 USD                              |

Severity is classified by the following:

| Severity | Description                                                                                                                                                                                             |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Critical | <p></p><ul><li>Empty or freeze the contract's holdings (e.g. economic attacks, flash loans, reentrancy, MEV, logic errors, integer over-/under-flow)</li><li>Cryptographic flaws</li></ul>              |
| High     | <p></p><ul><li>Token holders temporarily unable to transfer holdings</li><li>Users spoof each other</li><li>Theft of yield</li><li>Transient consensus failures</li></ul>                               |
| Medium   | <p></p><ul><li>Contract consumes unbounded gas</li><li>Block stuffing</li><li>Griefing denial of service (i.e. attacker spends as much in gas as damage to the contract)</li><li>Gas griefing</li></ul> |

\
The actual prize amount is determined by a combination of factors including but not limited to severity, value at risk, and likelihood of being exploited.

Payouts are done in vesting SEND on Sui. This is anon-friendly (no KYC required).

## Reporting <a href="#reporting" id="reporting"></a>

Email us a detailed description of the attack at [security@solend.f](mailto:security@solend.fi)i. Critical and High bug reports must come with a proof of concept.

**Assets in Scope**

Suilend smart contract code can be found here: [suilend-integration-links](https://docs.suilend.fi/ecosystem/suilend-integration-links "mention")

**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 the assets in the scope table.

**Smart Contracts**

* 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 at least 1 hour
* Unable to call smart contract

**Known Issues (not qualified)**

Bug reports involving position limit, where a user can only have so many positions before actions fail due to the computation limit, are not accepted in this bug bounty program.

Bug reports involving borrow limit, where a user can borrow even when the limit is set, are not accepted in this bug bounty program.

**Prioritized Vulnerabilities**

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
* Trust/dependency vulnerabilities
  * Composability vulnerabilities
* Oracle failure/manipulation
* Novel governance attacks
* Economic/financial attacks
  * Flash loan attacks
* Congestion and scalability
  * Running out of gas
  * Block stuffing
  * Susceptibility to front-running
* 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 <a href="#out-of-scope-rules" id="out-of-scope-rules"></a>

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

The following activities are prohibited by this bug bounty program:

* Any testing with mainnet contracts; all testing should be done on devnet or private testnets
* Any testing with live pricing oracles or live 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.suilend.fi/security/bug-bounty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.