Metronome
About
Metronome is a multi-collateral synthetic asset protocol that lets users deposit crypto collateral — including yield-bearing tokens from Vesper Finance — to mint synthetic versions of popular assets (msETH, msUSDC, msBTC, etc.) which can be swapped with zero slippage on the Synth Marketplace. It also offers Smart Farming, an automated yield-looping engine that repeatedly cycles deposits through Vesper pools and the Synth protocol to amplify yield. The protocol is governed by the MET token and its DAO, and is deployed on Ethereum, Optimism, and Base.
Where Does Yield Come From?
Metronome generates yield from three main sources. Here is how they work and where the money flows.
1. Fees from the Synth Protocol
When people use Metronome's synthetic assets (like msETH or msUSDC), the protocol collects three kinds of fees. All of them go to the Metronome DAO Treasury (a shared pot managed by the community):
- Synth Balance Fee — a small, ongoing charge on anyone who has borrowed by minting a synthetic asset. The fee grows their debt over time (calculated every second), and the rate depends on the riskiness of each synthetic asset.
- Marketplace Trading Fee — charged when users swap synthetic assets on the Synth Marketplace. It is 0.45% on most networks and 0.55% on Ethereum mainnet.
- Liquidation Fee — an 18% premium taken when someone's position gets liquidated. Of that, 10% goes to the person who performed the liquidation, and 8% goes to the Treasury.
2. Productive Collateral (yield-bearing deposits)
Users can put up "productive" tokens as collateral to mint synthetic assets. For example, you could deposit vaUSDC — a yield-bearing token from Vesper Finance. Even while that token sits as collateral, it keeps earning its normal yield (the lending or strategy returns from Vesper's pools). So you get the benefit of the yield and the ability to use the synthetic asset you minted.
3. Smart Farming (automated yield looping)
Smart Farming is a tool that runs a repeated loop to multiply your exposure to yield. Here is the basic cycle:
- You deposit productive collateral (e.g., vaUSDC) into Metronome.
- You set a loop multiplier (how many times to repeat the cycle).
- The system mints synthetic assets against your collateral.
- Those synths are swapped on a DEX (like Curve) back into the original asset (e.g., USDC).
- That USDC goes back into Vesper to mint more yield-bearing tokens.
- Those new tokens are re-deposited as additional collateral.
This creates a self-reinforcing position that amplifies your yield — but also increases your liquidation risk (leverage cuts both ways).
MET token holders and revenue share
Separate from the yield strategies above, the MET token has its own incentive mechanism. Holders can lock MET to receive esMET (a vote-escrowed position, tracked as an ERC-721 NFT). Each month, the DAO votes on an amount of Treasury funds to use for buying back MET on the open market. That bought-back MET is then streamed proportionally to everyone holding esMET. In short: locking your MET entitles you to a share of the protocol's buyback rewards.
Persons
Jeff Garzik
CEO/Co-founder of Bloq, Inc. (parent company of Autonomous Software)
Gabriel Montes
Team leader, Senior Node.js/JavaScript full-stack engineer (Autonomous Software)
Marcelo Morgado
Blockchain engineer (Autonomous Software)
Manoj Patidar
Developer (Autonomous Software)
Audits
| Audit / Date | Findings | Verdict |
|---|---|---|
Quantstamp25-10-2022 - 29-11-2022 |
| The audit found no high-risk or critical vulnerabilities, and the two medium-risk findings have been partially mitigated or remain unresolved with acknowledged risk, indicating that the protocol's core security posture is reasonable, though reliance on a single oracle without a backup (QSP-1) and the extensive privileged roles in upgradeable contracts (QSP-8, QSP-9) represent residual design risks that users should evaluate. |
Resonance Security16-09-2024 - 30-09-2024 |
| The audit found only low-severity and informational issues, both acknowledged by the development team based on the trusted nature of the AMO role, indicating a generally sound codebase with no critical or high-risk vulnerabilities identified. |
Resonance Security31-07-2023 - 17-08-2023 |
| The audit found no critical or high-severity vulnerabilities; four medium-severity issues were identified, two of which were resolved and two acknowledged by the team. With all medium-risk items addressed or accepted, the report indicates a reasonable security posture for the protocol at the time of review. |
Resonance Security, Inc.31-07-2023 - 17-08-2023 |
| The audit found no critical or high-severity vulnerabilities; the four medium-severity issues were either resolved or acknowledged with reasonable mitigations by the development team, indicating a solid security posture for the Metronome Synth protocol at the time of review. |
Resonance Security31-07-2023 - 17-08-2023 |
| The audit found no critical or high-risk vulnerabilities; the four medium-severity issues were either resolved or acknowledged with acceptable mitigations, indicating a reasonably secure codebase at the time of review. |
Dedaub28-02-2023 |
| The audit uncovered one high-severity liquidation DoS vector and minor low-severity issues, but most findings were either acknowledged as design trade-offs or resolved by the client; the protocol's core contract logic is generally sound, though the high-severity gas-exhaustion attack on liquidations should be mitigated before mainnet deployment. |
Dedaub20-01-2022 |
| The core Vesper Synth protocol was assessed as having a clean, well-organized architecture, but the critical missing-allowance-check in DepositToken and the front-runnable max-sentinel pattern in the Controller were serious defects (both resolved). The audit notes that oracle manipulation remains an inherent residual risk for a heavily oracle-dependent protocol, and the Vesper Pools delta review was necessarily restricted to changed lines, limiting confidence. |
Dedaub16-02-2022 |
| The one critical DoS issue was resolved before the audit concluded, and no high or medium severity vulnerabilities were found, indicating the delta changes are reasonably secure. However, residual design risks around oracle dependency and several open informational items from prior audits remain for ongoing attention. |
Dedaub03-06-2022 |
| The delta audit found no critical, high, or medium issues; the sole low-severity finding on oracle code was acknowledged and already slated for replacement, indicating the changes do not introduce material security risks to the protocol. |
Dedaub09-03-2022 |
| The audit found no critical vulnerabilities, with the single high-severity issue resolved and medium-severity items addressed or acknowledged; the residual risk is primarily from known sandwich-attack exposure on swaps, partially mitigated by small swap amounts and dual-exchange usage. |
Halborn06-06-2022 - 20-06-2022 |
| The audit found one high-severity issue (funds-at-risk on treasury migration) and one medium-severity DoS vector on reward claims, both of which require remediation before deployment; the remaining informational items are low risk. |
Halborn02-02-2022 - 02-03-2022 |
| Halborn's audit found no critical or high-severity issues; the single medium-risk finding (ERC20 approve race condition) was accepted by the Vesper team, and all low and informational findings were either fixed or acknowledged as acceptable design trade-offs, indicating a reasonably secure codebase for the Vesper Synth contracts. |
Legal
Status and notes
Metronome is operated by Autonomous Software (described as "A subsidiary of Bloq, Inc." on its GitHub organization page). The Terms & Conditions and Privacy Policy are hosted on GitHub (autonomoussoftware/metronome-synth-legal) and state the operator as "Autonomous Software." The Terms specify Delaware law as governing law and Chicago, Illinois for arbitration. No formal legal form (e.g., LLC, foundation, corporation) or registration jurisdiction is disclosed on the official metronome.io website or in the legal documents. Contact email: [email protected].
