Balmy
Balmy is your home for accessing the world of decentralized finance as it was meant to be: safe, open, and intuitive. Swap your assets at the best price, make recurring investments into your favorite tokens, or transfer money easily — all in one place that meets your immediate financial needs and sets you up for long-term success.
PoC required
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.
Issues previously highlighted in the following audit reports are considered as out of scope:
- https://github.com/Balmy-protocol/dca-v2-core/blob/main/audits/PeckShield.pdf
- https://github.com/Balmy-protocol/dca-v2-core/blob/main/audits/Pessimistic.pdf
- https://omniscia.io/reports/mean-finance-transformers-module/
- https://omniscia.io/reports/mean-finance-oracle-module/
- https://omniscia.io/reports/mean-finance-swappers-module/
- https://omniscia.io/reports/mean-finance-permit2-adapter-64ad40c224448c00148ee2f9/static-analysis/BasePermit2Adapter-BPA
In addition, the following bug are also considered out of scope:
- The team is aware that UniswapV3 TWAP oracles can be manipulable if liquidity is low and there is a warning for low liquidity pairs on the front-end to address this. Hence, security assessments should be done under the assumption that oracles return the correct price.
- Tokens exhibiting non-standard ERC20 behavior that only affects holders of that token and does not impact any other assets managed by Balmy. (E.g., a transfer function that fails to update users balances).
- Bug reports that require escalated privileges
Payouts are handled by the Balmy team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
Balmy is your home for accessing the world of decentralized finance as it was meant to be: safe, open, and intuitive. Swap your assets at the best price, make recurring investments into your favorite tokens, or transfer money easily — all in one place that meets your immediate financial needs and sets you up for long-term success.
For more information about Balmy, please visit https://balmy.xyz. Docs at https://docs.balmy.xyz.
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.