MetalSwap
MetalSwap is a decentralised platform that enables hedging swaps in financial markets with the aim of providing a hedge for commodity traders and an investment opportunity for those who contribute to the shared liquidity of the project.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any funds belonging to specific users, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Maximal extractable value (MEV) mechanisms that directly prevent the use of the hedging swap instrument by the end users
Protocol insolvency regarding tokens other than the governance reward token XMT
Theft of unclaimed yield
Theft of unclaimed royalties
Permanent freezing of unclaimed yield
Temporary freezing of funds for at least 1 hour
Out of scope
- Best practice critiques
- Bugs and possible attacks publicly disclosed by MetalSwap (or remedied) before their bounty is claimed
- Known and already remedied bug on the Liquidity Pool smart contracts that allowed users to redeem XMT token rewards for NFT liquidity positions owned by other users
- Protocol insolvency regarding the governance reward token XMT
- Cases of protocol insolvency related to transactions failing because of lack of tokens on the Smart Contracts or token allowances given on platform-owned wallets by MetalSwap operators are excluded from the bug bounty program because they are improbable and easily and quickly fixable
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers