Sector Finance
Sector Finance aims to promote the widespread adoption of digital assets by developing innovative financial products and providing investors with information regarding their risk exposures.
PoC required
Rewards by Threat Level
Please review how rewards are distributed based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale system with separate scales for Smart Contracts and Websites/Apps.
Rewards for critical smart contract bug reports will be further capped at 10% of direct funds at risk if the bug discovered is exploited. However, there is a minimum reward of USD 2 000.
Payouts and Payout Requirements
Payouts are handled by the Sector Finance team directly and are denominated in USD. However, payouts are done in USDC. Sector Finance commits to honoring payouts according to the terms set out in this program at the time of report submission, and to treat this program as the agreement and source of truth concerning bug reports and responsible disclosures.
For the purposes of determining report validity, this is a Primacy of Rules program.
Learn more about report validity best practices here: Best Practice - Primacy of Impact vs Primacy of Rules.
KYC Requirements
Sector Finance does not have a Know Your Customer (KYC) requirement for bug bounty payouts.
Audit Discoveries and Known Issues
Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi.
Previous audits and known issues:
- Sandwich attacks targeting harvests or other deposits that result in griefing or failed transactions (DDOS).
- Depositing into Aggregator vaults when the share price is temporarily deflated and thus getting a better entry price.
- Front-running Aggregator vault harvests by depositing immediately before a profitable harvest and withdrawing funds immediately after.
Program Overview
Transparent Risk, Real Yield. Earn yield based on your own risk preference.
Sector Finance consists of three core products: 1. The risk engine, 2. Single-strategy investments vaults and 3. Aggregator vaults. The risk engine evaluates and organizes the crypto-risk of our single-strategy investment vaults. The platform then creates structured product vaults that aggregate investment strategies to match the exact risk profile of a user.
While risk is an inherent aspect of investing, it is important that both individual and institutional investors are not subjected to the risks associated with poorly constructed products and obscure risk assessment methods. Sector Finance aims to promote the widespread adoption of digital assets by developing innovative financial products and providing investors with information regarding their risk exposures.
For more information about Sector Finance, please visit https://sector.finance/
For Whitehats: It is highly recommended that you review the details of this program in full. Although many Bug Bounty programs have standard terms and conditions, each also has their own unique details that are critical to your success.
Prior to submitting a report please review the Immunefi Bug Report Template and Best Practices.
Responsible Publication
Sector Finance adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.