Segment Finance
Bounty Range
$5,000 - $100,000
external program
Segment Finance
Segment Finance, as a decentralized lending and borrowing platform on the BNB and opBNB Chains, extends its functionalities beyond the framework of the initial Compound Protocol fork. It offers not only the default lending-borrowing pool but also features isolated pools. These isolated pools are designed to offer specialized lending and borrowing services for a variety of assets, enhancing the platform's flexibility and appeal to a diverse user base.
The platform's architecture ensures that these isolated pools operate with distinct risk parameters, allowing for tailored risk management strategies. This design is particularly beneficial for assets with varying risk profiles, ensuring that each pool can maintain its stability and security independently of the others.
Furthermore, Segment Finance integrates advanced smart contract functionalities to automate many of the processes involved in lending and borrowing. This includes automatic interest rate adjustments based on supply and demand dynamics, as well as innovative collateral management systems to protect lenders' assets.
In addition, Segment Finance seeks to innovate in the DeFi space by exploring cross-chain functionalities. This would potentially allow users to lend and borrow assets across different blockchain networks, significantly expanding the platform's utility and reach.
Segment Finance provides rewards in USDT on BNB Chain, denominated in USD.
Smart Contract - Critical
Smart Contract - High
Smart Contract - Medium
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $100,000.
Minimum reward to discourage security researchers from withholding a bug report: $25,000
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Calculation for Critical Level Reports
For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of USD 25,000. This is because there are no actual funds at risk on the testnet, hence limits objective calculation.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attacks within the first hour will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
Reward Payment Terms
Payouts are handled by the Segment Finance team directly and are denominated in USD. However, payments are done in USDT.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Segment Finance will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
The submission of KYC information is a requirement for payout processing.
Segment Finance adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Proof of concept is always required for all severities.
Segment Finance's completed audit reports can be found at https://github.com/verichains/public-audit-reports/blob/main/Verichains%20Public%20Audit%20Report%20-%20Segment%20Finance%20Pool%20Register%20-%20v1.0.pdf
Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
By adhering to Immunefi's best practice recommendations, Segment Finance has satisfied the requirements for the Immunefi Standard Badge.
Category 3: Approval Required
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.
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.