Brahma is a non-custodial protocol that activates and manages liquidity across chains and dApps.
For more information about Brahma, please visit https://app.brahma.fi/vault/pmusdc.
Rewards by Threat Level
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 Smart Contract 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.
The bug report must be directly exploitable by a party (i.e the vulnerability must be exploitable directly by a user/party according to the PoC) in order to be valid and eligible for a reward, and not be dependent on external events (i.e An asset price should move by X, or an external protocol the contracts are interacting with needs to malfunction for the issue to be realizes/exploitable)
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 17,500 to 35,000 depending on the type of funds at risk.
Smart Contracts (Critical)
- Loss of user funds:
- 10% of assets at risk, minimum USD 35, 000; maximum USD 150, 000
- Loss of non-user funds (e.g. treasury):
- 10% of assets at risk, minimum USD 17, 500; maximum USD 150, 000
Smart Contracts (High)
- Temporary freezing of funds for more than 7 days (other than unclaimed yield):
- 10% of assets at risk, minimum USD 5, 000; maximum USD 25, 000
- Permanent freezing/theft of unclaimed yield:
- 10% of assets at risk, minimum USD 2, 000; maximum USD 25, 000
All vulnerabilities marked in the https://github.com/Brahma-fi/brahma-security/tree/master/audits are not eligible for a reward.
Payouts are handled by the Brahma team directly and are denominated in USD. However, payouts are done in USDC.
- Up to USD $150,000
- Up to USD $25,000
- USD $1,500
Assets in scope
- Smart Contract - PMUSDC VaultType
- Smart Contract - PMUSDC BatcherType
- Smart Contract - ConvexFraxPoolTradeExecutorType
- Smart Contract - ConvexSUSDPoolTradeExecutorType
- Smart Contract - PerpTradeExecutorType
- Smart Contract - PerpPositionHandlerL2Type
- Smart Contract - HarvesterType
All smart contracts of Brahma can be found at https://github.com/brahma-fi/protected_moonshots/. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
If an impact can be caused to any other asset managed by Brahma that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This only applies to Critical and High impacts.
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.
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Miner-extractable value (MEV)CriticalImpact
- Protocol insolvencyCriticalImpact
- Theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of funds for more than 7 daysHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumptionMediumImpact
Out of Scope & Rules
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