Sector Finance

Submit a Bug
11 May 2023
Live since
KYC required
Maximum bounty
12 July 2023
Last updated

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

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.

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 5 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.

Smart Contract

USD $5,000 to USD $25,000
PoC Required

Assets in scope

Only those listed in the Assets in Scope table are considered to be in-scope of the bug bounty program.

Vulnerabilities found in code used by multiple contracts (ex: proxy contracts or multi-chain deployments) will count as a single submission. In other words, if one vulnerability can be executed on the same identical code over multiple contracts, this would count as a single report. When submitting such a report select one of the affected contracts and add links to others in the body of the report.

Smart Contracts

Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Dev Environment and Documentation

Sector Finance has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:

Impacts in Scope

(For Blockchain/DLT and Smart Contracts Only) This program is considered to be governed by Primacy of Rules. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.

Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.

At Immunefi, we classify bugs on a simplified 5-level scale:

  • Critical
  • High
  • Medium
  • Low
  • None

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

Smart Contract

  • Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
  • Permanent freezing of funds
  • Protocol insolvency

Out of Scope & Rules

The following impacts and attack vectors are excluded from rewards by default for all Immunefi bug bounty programs:

  • 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), except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
  • Broken link hijacking is out of scope

Smart Contracts and Blockchain/DLT

  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Centralization risks

Prohibited Activities

The following activities are prohibited by this bug bounty program. Violation of these rules can result in a temporary suspension or permanent ban from the Immunefi platform at the sole discretion of the Immunefi team, which may also result in: 1) the forfeiture and loss of access to all bug submissions, and 2) zero payout.

Please note that Immunefi has no tolerance for spam/low-quality/incomplete bug reports, “beg bounty” behavior, and misrepresentation of assets and severity. Immunefi exists to protect the global crypto community, not facilitate grift.


  • Any testing with mainnet or public testnet deployed code; all testing should be done on private testnets
  • 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
  • Any other actions prohibited by the Immunefi Rules. These rules are subject to change at any time.