All smart contracts of Silo Finance can be found at [https://github.com/silo-finance/silo-core-v1](https://github.com/silo-finance/silo-core-v1). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Silo is a non-custodial lending protocol that implements risk-isolated money markets on Ethereum and Arbitrum where any crypto asset can be borrowed with another.

Any governance voting result manipulation

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

Permanent freezing of funds

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds

Injecting/modifying the static content on the target application without Javascript (Persistent) such as HTML injection without Javascript, replacing existing text with arbitrary text, arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Miner-extractable value (MEV)

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)

Theft of gas

Unbounded gas consumption

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or en/disabling notification

Redirecting users to malicious websites (Open Redirect)

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 web/app bug reports and all Critical/High severity smart contract 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.

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 30 000__ and a maximum of __USD 100 000__ for Critical smart contract bug reports.

Critical website and application bug reports will be rewarded with __USD 20 000__ only if the impact leads to a direct loss in funds or a manipulation of the votes or the voting result, as well as the modification of its display leading to a misrepresentation of the result or vote. All other impacts that would be classified as Critical would be rewarded no more than __USD 10 000__.

The following impacts/vulnerabilities are considered out of scope: 
  - Attacks caused by rebase tokens, fee-on-transfer tokens or non-standard ERC20 tokens are out of scope unless such token has deployed and configured Silo with user funds or has a pending DAO proposal for its Silo.
  - On-chain oracle manipulation attacks (BalV2 TWAP, UniV3 TWAP and future integrations).
  - Interest rate manipulation caused by lack of liquidity.
  - Liquidation front-running.

In addition, known issues highlighted in audits or disclosure reports are considered out of scope: 
  - [ChainSecurity Audit](https://drive.google.com/file/d/1h-vjVceL2k03jXAN_mBcEmeUbATcrrEt/view?usp=sharing)
  - [Vulnerability Disclosure June 6, 2023](https://github.com/silo-finance/silo-core-v1/blob/master/certora/reports/06_2023_silo_certora_IRMv2.pdf)
  - [Certora Formal Verification](https://drive.google.com/file/d/1D2EIOb0XaRov5Ph2AE0DTfIsMISd7UXG/view?usp=sharing)
  - [ABDK Audit](https://drive.google.com/file/d/1WXaB3ICLv4rSEX86POK3-NaOIxXwyq9l/view?usp=sharing)
  - [Quantstamp Audit](https://drive.google.com/file/d/10GyfA-nBJ5jqLWW9LEYJQeFem8qSgNH6/view?usp=sharing)

Payouts are handled by the __Silo Finance__ team directly and are denominated in USD. However, payouts are done in __USDC__.

Silo Finance

Resources & Documentation