> For the complete documentation index, see [llms.txt](https://docs.metronome.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metronome.io/metronome-synth/metronome-synth-protocol.md).

# Metronome Synth Protocol

### Overview

Metronome Synth is a new multi-collateral/multi-synthetic protocol that enables users to post their existing crypto holdings as collateral to create synthetic versions of other popular assets. 

This collateral can include productive assets (yield bearing assets, such as Vesper Finance vPool tokens) or naked assets like ETH and USDC. Depositing collateral allows users to mint synthetic assets, which can then be swapped without slippage on the Metronome Synth Marketplace, or used for looped yield farming. These assets can also be used more generally for lending, farming, trading, or whatever else users desire.

The Metronome Synth protocol is powered by the MET token, which serves as both a utility token on the dApp, and as a governance token for the Metronome DAO.

Metronome Synth is currently deployed on Ethereum, Optimism, and Base. Additional chains are in development.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.metronome.io/metronome-synth/metronome-synth-protocol.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.