Metronome
Metronome is continuing its journey by relaunching and innovating for DeFi in 2022. Metronome was a pioneer in the DeFi space when it was launched in June 2018. With an elegant system of four smart contracts, Metronome has had success with its daily auctions and DEX functionality. Since Metronome’s launch, DeFi has evolved due to the composable nature of protocols.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Any governance voting result manipulation
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
Permanent freezing of funds
Permanent freezing of NFTs
Miner-extractable value (MEV)
Unauthorized minting of NFTs
Predictable or manipulable RNG that results in abuse of the principal or NFT
Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
Protocol insolvency
Execute arbitrary system commands
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)
Out of scope
- Best practice critiques
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