LEVEL is a decentralized and non-custodial perpetual DEX on BNB Chain focused on delivering highly effective risk management along with first of a kind liquidity solution for LPs using original code designed from the ground up. LEVEL's architecture facilitates direct market access to programmatic pools of liquidity, enabling capital-efficient hedging with near-zero market impact for traders looking to protect their gains while seamlessly creating a yield-bearing instrument for asset owners looking to earn passive income on their crypto holdings.
For more information about LEVEL, please visit https://app.level.finance/
LEVEL provides rewards in USDT. For more details about the payment process, please view the Rewards by Threat Level section further below.
LEVEL adheres to category Publication Category 2: Notice Required. 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.
Primacy of Impact vs Primacy of Rules
LEVEL adheres to the Primacy of Impact for the following severity levels:
- Smart Contract - Critical
- Smart Contract - High
- Smart Contract - Medium
If a category’s severity level is covered within the Primacy of Impact, it means that even if the impacted asset is not in-scope but is owned by the project, then it would be considered as in-scope of the bug bounty program as long as it involves an impact under that respective severity level. When submitting a report, just select the Primacy of Impact asset placeholder. If the team behind this project has multiple projects, those other projects are not covered under the Primacy of Impact of this program. Instead, check if those other projects have a bug bounty program on Immunefi.
Testnet and mock files are not covered under the Primacy of Impact.
All other severity levels not listed here are considered under the Primacy of Rules, which means that they are bound by the terms of the bug bounty program.
Known Issue Assurance
LEVEL commits to providing Known Issue Assurance to bug submissions through their program. This means that LEVEL will either disclose known issues publicly or at the very least privately via a self-reported bug submission in order to allow for a more objective and streamlined mediation process to prove that an issue is known. Otherwise, assuming the bug report itself is valid, it would result in the bug report being considered in-scope and due 100% of the reward with respect to the bug bounty program terms.
Immunefi Standard Badge
LEVEL has satisfied the requirements for the Immunefi Standard Badge, which is given to projects that adhere to our best practices.
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Reward Calculation for Critical Level Reports
For critical Smart Contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 1 000 000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 200 000 is to be rewarded in order to incentivize security researchers against withholding a bug report.
LEVEL has provided these completed audit review reports for reference. Any unfixed vulnerability mentioned in these reports are not eligible for a reward.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Smart Contract - Critical Severity
- Smart Contract - High Severity
- Smart Contract - Medium Severity
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
Reward Payment Terms
Payouts are handled by the LEVEL team directly and are denominated in USD. However, payments are done in USDT.
- Up to USD $1,000,000
- USD $25,000
- USD $10,000
Assets in scope
- Smart Contract - LiquidityPoolType
- Smart Contract - Senior LLPType
- Smart Contract - Mezzanine LLPType
- Smart Contract - Junior LLPType
- Smart Contract - LiquidityRouterType
- Smart Contract - OrderManagerType
- Smart Contract - LevelOracleType
- Smart Contract - PriceReporterType
- Smart Contract - TradeExecutorType
- Smart Contract - ETHUnwrapperType
- Smart Contract - LevelTeamMultisigType
- Smart Contract - Timelock (12hr delay)Type
- Smart Contract - Timelock (48hr delay)Type
- Smart Contract - ProxyAdminType
- Smart Contract - LVL (Level Token)Type
- Smart Contract - LVL Reserve PartnershipType
- Smart Contract - LVL IncentivesType
- Smart Contract - LVL Dev FundType
- Smart Contract - LGO (Level Governance)Type
- Smart Contract - LevelStake (Dao Staking)Type
- Smart Contract - Treasury - ReserveType
- Smart Contract - Treasury - AssetsType
- Smart Contract - FeeDistributorType
- Smart Contract - GovernanceRedemptionPool (Old)Type
- Smart Contract - GovernanceRedemptionPoolV2 (Old)Type
- Smart Contract - VotingPowerViewType
- Smart Contract - LGOStakingViewType
- Smart Contract - LevelMaster (old)Type
- Smart Contract - LevelMasterV2Type
- Smart Contract - LGOStakingType
- Smart Contract - LVLStakingType
- Smart Contract - lylLevelType
- Smart Contract - LevelReferralController (old)Type
- Smart Contract - LevelReferralControllerV2Type
- Smart Contract - LevelReferralRegistryType
- Smart Contract - AuctionTreasuryType
- Smart Contract - LGO Auction FactoryType
- Smart Contract - LVLAuctionFactoryType
- Smart Contract - LVLBatchAuctionTreasuryType
- Smart Contract - LevelZapType
- Smart Contract - Liquidity BootstrappingType
- Smart Contract - LVLOracleType
- TargetSmart Contract - Primacy of ImpactType
All code of LEVEL can be found at https://github.com/level-fi. Documentation for the assets provided in the table can be found at https://docs.level.finance/ and https://docs.level.finance/security-and-contracts/smart-contracts.
Unless explicitly listed, only pages of the web/app assets in addition to the direct link are considered in-scope of the bug bounty program. Other subdomains are not considered as in-scope. However, for subdomain takeovers that lead to an impact on the in-scope asset, please refer to our page about Reported Subdomain Takeovers.
A public testnet of LEVEL can be found at https://test.level.finance/. However, note that testing on the public testnet is prohibited by the program rules. The public testnet is provided for reference only.
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.
- Theft of governance fundsCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Loss of user funds by freezing, theft, or manipulation of the price of LLPCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol insolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
Out of Scope & Rules
These impacts are out of scope 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), 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
The following activities are prohibited by this bug bounty program:
- 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