ChainlinkFeedRegistry (not valid on Ethereum

All assets listed are available on the same address on Ethereum, Arbitrum, Optimism, Polygon, BNB Chain and Base – all those networks are considered in scope.

All smart contracts of Balmy can be found at https://github.com/Balmy-protocol. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an Critical or High impact can be caused to any other asset managed by Balmy 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.

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. 

Smart contract fails to deliver promised returns, but doesn’t lose value

Theft of unclaimed yield

Temporary freezing of funds for any amount of time

Permanent freezing of unclaimed yield

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Theft of gas

Unbounded gas consumption

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Balmy Documentation

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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__.