RociFi

RociFi protocol is a DeFi primitive for permissionless under-collateralized lending. Built on Ethereum, RociFi is launched on Polygon.

RociFi is reinventing credit to be more inclusive while increasing capital efficiency in DeFi by leveraging on-chain behavior and reputation to issue under-collateralized loans.

As the protocol grows in adoption, it will function similarly to a Layer 1 whereby DeFi and TradFi firms can build new capital markets services atop RociFi, thus creating a decentralized credit economy.

RociFi enables borrowers with clean EVM-compatible on-chain history and reputation to borrow with reduced or zero collateral while offering lenders a high, stable deposit yield. RociFi V2 uses USDC, USDT, Matic and WETH for lending and collateral.

Here you can find recent versions of the contracts: https://github.com/RociFi/Roci-Smart-Contracts-v2

All of them are verified and can be seen on Polygon.

For more information about RociFi, please visit https://v2.roci.fi/app/markets

Rewards are distributed according to the impact of the vulnerability based on the 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 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.

Payouts are handled by the RociFi team directly and are denominated in USD. However, payouts are done in USDC.

Smart Contract

For proxy contracts, only the current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.

All smart contracts of RociFi can be found at https://github.com/RociFi/Roci-Smart-Contracts-v2. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

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
• Centralization risks

The following activities are prohibited by this 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