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

# Conversion Guide

### **Conversion Process for Self-Custody**

{% embed url="<https://jumpshare.com/v/2sSb1k05FG2OyOCO8ATg>" %}

**In order to participate in the conversion, users have several options.** To convert MPL to SYRUP from a self-custody wallet, users can visit [syrup.fi/convert](http://syrup.fi/convert) to initiate the process.

The steps are simple:

* Navigate to the official Syrup webapp using a supported web browser
* Connect a self-custody wallet and follow the conversion workflow to select “Claim & Stake”
  * SYRUP that is staked will be represented as stSYRUP in a user’s wallet, with the value of accrued SYRUP viewable in the staking dashboard
  * SYRUP that is not staked will reflect in a user’s wallet balance
* The conversion ratio is 1 MPL to 100 SYRUP

While staking is the default option, it is not mandatory.&#x20;

<figure><img src="/files/pABFiH1SGyDjuPAGo6Jm" alt=""><figcaption></figcaption></figure>

Below is a list of supported wallets for interacting with the Syrup webapp in order to stake:

* Coinbase Wallet
* MetaMask
* WalletConnect
* Ledger
* Exodus
* Phantom
* Browser Wallet
* OKX Wallet
* Binance Web3 Wallet

Users should always be mindful to keep a sufficient balance of ETH in their wallets to cover any associated gas fees. Users should also always double-check transaction details before confirming, and ensure they’re interacting with the official Syrup webapp to avoid potential scams.

### **Conversion Process on Exchanges**

Users converting their MPL to SYRUP on an exchange must comply with each exchange’s unique processes.

While some exchanges will enable automatic conversion of MPL to SYRUP, others will require a user to transfer their MPL balance into a self-custody wallet in order to participate in the conversion. Details per exchange are included in the links below:

* [Coinbase](https://syrup.gitbook.io/syrup/syrup-token/supported-exchanges/coinbase)
* [Kraken](https://syrup.gitbook.io/syrup/syrup-token/conversion-guide/supported-exchanges/kraken)
* [Gate](https://syrup.gitbook.io/syrup/syrup-token/conversion-guide/supported-exchanges/gate)
* [AscendEX](https://syrup.gitbook.io/syrup/syrup-token/conversion-guide/supported-exchanges/ascendx)
* [Bitstamp](https://syrup.gitbook.io/syrup/syrup-token/conversion-guide/supported-exchanges/bitstamp)
* [Bitmart](https://syrup.gitbook.io/syrup/syrup-token/conversion-guide/supported-exchanges/bitmart)

It's important for users to carefully read all communications from their exchange regarding the MPL to SYRUP conversion to ensure they don't miss important steps or deadlines.&#x20;

Avoid scams and phishing by only engaging with official exchange communications. Engage with each exchange’s customer support with inquiries when needed.

Links will be updated as exchange announcements are made.


---

# 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://syrup.gitbook.io/syrup/syrup-token/conversion-guide.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.
