Metronome-logo

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.

ETH
Optimism
Defi
Synthetic Assets
Yield Aggregator
Solidity
Maximum Bounty
$100,000
Live Since
21 February 2023
Last Updated
08 April 2024
  • PoC required

Rewards by Threat Level

Smart Contract
Critical
USD $10,000 - USD $100,000
High
USD $5,000 - USD $10,000
Medium
USD $1,000 - USD $5,000
Websites and Applications
Critical
USD $5,000 - USD $20,000
High
USD $1,000 - USD $5,000

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.

Bounty payouts will be dependent on actual risk to the platform. Total bounty will either be the minimum of the range, or 5% of the total funds that could be lost in the exploit (up to the maximum cap based on the tier severity) - whichever amount is greater.

All smart contract and web/app 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. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

Known issues highlighted in the following audit reports are considered out of scope:

Payouts are handled by the Metronome team directly and are denominated in USD. However, payouts are done in USDC, DAI, and MET, at the discretion of the project.

Program Overview

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. Relaunching Metronome will provide upgraded token features, security enhancements, DeFi composability, a new development roadmap, and the formation of a Metronome DAO.

For more information about Metronome, please visit https://www.metronome.io/

KYC not required

No KYC information is required for payout processing.

Prohibited Activities

Default 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.