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

# Bridging Stablecoins to MemeCore

MemeCore supports cross-chain transfers of **M** and **stablecoins** through [Stargate](https://stargate.finance/), the omnichain bridge built on LayerZero.\
With Stargate you can move `M` between MemeCore, BNB Chain, and Base, and bring `USDC.e` and `USDT0.s` to MemeCore from the Stargate network.

{% hint style="info" %}
**Stargate is the recommended bridge for MemeCore.**\
[Meson Finance](https://meson.fi/), the previous stablecoin bridge, remains available during a transition period and will be deprecated **before the end of 2026**. The `USDC.e` issued through Meson will be migrated to the `USDC.e` issued through Stargate. See [Migration](#migration-meson-usdc.e-stargate-usdc.e) and [Legacy Bridge: Meson Finance](#legacy-bridge-meson-finance) below.
{% endhint %}

***

### Supported Bridges

<table><thead><tr><th width="227.21484375">Bridge</th><th width="198.796875">Status</th><th>What you can bridge</th></tr></thead><tbody><tr><td><strong>Stargate</strong> (recommended)</td><td>✅ Active</td><td><p><code>M</code> between MemeCore, BNB Chain, and Base</p><p><code>USDC.e</code> between MemeCore and the Stargate USDC network</p><p><code>USDT0.s</code> between MemeCore and the Stargate USDT0 network</p></td></tr><tr><td>Meson Finance (legacy)</td><td>⚠️ Deprecating before end of 2026</td><td>Meson <code>USDC.e</code> only — not recommended for new transfers</td></tr></tbody></table>

* **Stargate**
  * Bridges the native **M** token between MemeCore, BNB Chain, and Base
  * Issues **USDC.e** (backed by USDC) and **USDT0.s** (backed by USDT) on MemeCore
* **Meson Finance** (legacy)
  * HTLC-based atomic swap bridge that issued the previous `USDC.e` on MemeCore
  * Scheduled for deprecation before the end of 2026

#### Where can I bridge from and to?

<table><thead><tr><th width="208.390625">Asset on MemeCore</th><th>Networks</th></tr></thead><tbody><tr><td><code>M</code></td><td><strong>MemeCore ↔ BNB Chain ↔ Base</strong> in any direction. No other networks.</td></tr><tr><td><code>USDC.e</code> (Stargate)</td><td><strong>MemeCore ↔ native <code>USDC</code> on BNB Chain, Base, Ethereum, Arbitrum, OP Mainnet, Polygon, Avalanche, and Sonic</strong>, and ↔ <code>USDC.e</code> on other Stargate networks. The Stargate app shows the full list when you select <code>USDC.e</code> on MemeCore.</td></tr><tr><td><code>USDT0.s</code> (Stargate)</td><td><strong>MemeCore ↔ Base, OP Mainnet,</strong> and other networks that carry <code>USDT0</code> or <code>USDT0.s</code> (for example Mode, Soneium, World Chain). The Stargate app shows the full list when you select <code>USDT0.s</code> on MemeCore.</td></tr><tr><td><code>USDC.e</code> (Meson, legacy)</td><td>MemeCore ↔ the chains where Meson is live. Being migrated to Stargate <code>USDC.e</code>.</td></tr></tbody></table>

{% hint style="info" %}
**Which stablecoin should I bridge?**

* If you hold **`USDC`** on BNB Chain, Base, Ethereum, or another supported network, bridge it to **`USDC.e`** (Stargate) on MemeCore in one step.
* If you hold **`USDT`**, note that regular `USDT` cannot be sent to MemeCore in one step yet. Use Stargate to convert it to `USDT0.s` on Base first (select **USDT0.s on Base** as the destination; `USDT` on Ethereum, Base, and Solana can be converted directly), then bridge `USDT0.s` from Base to MemeCore. `USDT` on BNB Chain needs one extra step: bridge it to Base as `USDT` first.
* If you hold **`M`** on BNB Chain or Base, bridge it to MemeCore directly.
  {% endhint %}

***

### Supported Assets

#### M (MemeCore native token)

<table><thead><tr><th width="191.95703125">Network</th><th width="172.84375">Token</th><th>Address</th></tr></thead><tbody><tr><td>MemeCore</td><td><code>M</code> (native)</td><td>—</td></tr><tr><td>BNB Chain</td><td><code>M</code></td><td><code>0x22b1458e780F8fA71E2F84502cEe8B5A3cc731Fa</code></td></tr><tr><td>Base</td><td><code>M</code></td><td><code>0x491CC54c9C852Db1f1A720d8Fd46C8A77bDE9dA1</code></td></tr></tbody></table>

`M` can be bridged in **any direction** between the three networks. On MemeCore, `M` is the native gas token, so no token approval is needed when bridging out.

#### Stablecoins on MemeCore

<table><thead><tr><th width="147.3828125">Token</th><th width="141.39453125">Issuer</th><th width="391.015625">Address on MemeCore</th><th width="463.74609375">Backed by</th></tr></thead><tbody><tr><td><strong><code>USDC.e</code></strong></td><td>Stargate</td><td><code>0x8a2B28364102Bea189D99A475C494330Ef2bDD0B</code></td><td>USDC held in Stargate pools on the source chain</td></tr><tr><td><strong><code>USDT0.s</code></strong></td><td>Stargate</td><td><code>0x0F3273eA5d8B182CD87C8630Dc436a6133b9bE39</code></td><td>USDT held in Stargate pools on the source chain</td></tr><tr><td><code>USDC.e</code> (legacy)</td><td>Meson Finance</td><td><code>0x552791BE94B679cd0CeFB35c8AB0364973ACB37f</code></td><td>USDC locked by the Meson bridge on the source chain</td></tr></tbody></table>

* **`USDC.e` (Stargate)** is bridged USDC. Bridge native `USDC` from any supported network and you receive `USDC.e` on MemeCore 1:1; bridge it back and you receive native `USDC` on the destination. On-chain name: `Bridged USDC (Stargate)`, 6 decimals.
* **`USDT0.s`** is the Stargate-issued version of **USDT0**, Tether's omnichain USDT. On-chain name: `Stargate USD₮0 (Bridged)`, on-chain symbol `USD₮0`, 6 decimals. The Stargate app lists it as **USDT0.s**; some wallets may show the on-chain symbol instead.
* **`USDC.e` (Meson, legacy)** is the stablecoin issued through Meson before Stargate was integrated. It is being migrated to Stargate `USDC.e`.

{% hint style="warning" %}
**Two different tokens on MemeCore use the symbol `USDC.e`.**\
The Stargate `USDC.e` (`0x8a2B28364102Bea189D99A475C494330Ef2bDD0B`) and the legacy Meson `USDC.e` (`0x552791BE94B679cd0CeFB35c8AB0364973ACB37f`) are separate contracts and are **not interchangeable**. Always identify a token by its **contract address**, not its symbol, before adding it to your wallet, trading it, or sending it to a bridge. Only the addresses listed on this page are official.
{% endhint %}

***

### 📘 Getting Started with Stargate

The full reference is the [Stargate documentation](https://docs.stargate.finance/). The steps below cover the standard transfer flow.

#### Step 1: Open Stargate and connect your wallet

1. Go to [https://stargate.finance](https://stargate.finance/) and select **Transfer**.
2. Click **Connect Wallet** and choose your wallet.

#### Step 2: Select the destination

1. In the **To** field, search for **MemeCore**.
2. Choose the destination token: **M**, **USDC.e** (Stargate), or **USDT0.s**.
3. The **From** field now lists only the source networks and tokens that can reach your selection.

#### Step 3: Select the source and amount

1. Choose the source network and token (for example, `USDC` on BNB Chain, or `M` on Base).
2. Enter the amount. Stargate shows the route, total fee, and estimated time before you confirm.
3. Click **Transfer**. Approve the token allowance (first time only) and confirm the transaction in your wallet.

#### Step 4: Track the transfer

* The Stargate app shows the transfer status in your transaction history.
* You can also track the message on [LayerZero Scan](https://layerzeroscan.com/) by pasting the source transaction hash.
* Once delivered, the asset appears in your wallet on MemeCore. If `USDC.e` or `USDT0.s` does not show up automatically, add it with the contract address listed above.

#### Bridging out of MemeCore

The same flow works in reverse. Select the source network as **MemeCore**, choose `M`, `USDC.e` (Stargate), or `USDT0.s`, and pick the destination network and token.

* `M` sent from MemeCore uses native `M`, so no token approval is needed.
* `USDC.e` (Stargate) sent from MemeCore arrives as native `USDC` on the destination network.
* `USDT0.s` sent from MemeCore arrives as `USDT0` or `USDT0.s` on the destination network.

{% hint style="info" %}
You need a small amount of the source network's gas token (for example `BNB` on BNB Chain, `ETH` on Base, or `M` on MemeCore) to pay for the transaction, plus the LayerZero messaging fee shown in the Stargate app.
{% endhint %}

***

### Migration: Meson USDC.e → Stargate USDC.e

The stablecoin previously bridged through Meson, `USDC.e` (Meson, legacy), will be **replaced by the `USDC.e` (Stargate) issued through Stargate**.

* Holders of Meson `USDC.e` (legacy) will be able to convert their balance to Stargate `USDC.e` 1:1.
* A detailed migration announcement and step-by-step guide will be published soon on this page and on MemeCore's official channels.
* Until the migration is complete, Meson `USDC.e` continues to exist on MemeCore. **Do not send Meson `USDC.e` to the Stargate bridge** — Stargate only recognizes its own `USDC.e` contract.
* After the migration, Meson `USDC.e` will no longer be supported by the bridge.

<table><thead><tr><th width="130.890625"></th><th width="392.9921875">New</th><th width="396.85546875">Legacy</th></tr></thead><tbody><tr><td>Token</td><td><code>USDC.e</code> (Stargate)</td><td><code>USDC.e</code> (Meson, legacy)</td></tr><tr><td>Issuer</td><td>Stargate</td><td>Meson Finance</td></tr><tr><td>MemeCore address</td><td><code>0x8a2B28364102Bea189D99A475C494330Ef2bDD0B</code></td><td><code>0x552791BE94B679cd0CeFB35c8AB0364973ACB37f</code></td></tr><tr><td>Backing</td><td>USDC held in Stargate pools on the source chain</td><td>USDC locked by the Meson bridge on the source chain</td></tr><tr><td>Bridge out to</td><td>Native <code>USDC</code> on BNB Chain, Base, Ethereum, Arbitrum, OP Mainnet, Polygon, Avalanche, Sonic, and other Stargate networks</td><td>Chains where Meson is live</td></tr></tbody></table>

***

### Legacy Bridge: Meson Finance

{% hint style="warning" %}
Meson Finance will be **deprecated before the end of 2026**. For new transfers, use Stargate. The information below is kept for users who still hold Meson `USDC.e` or have transfers in progress.
{% endhint %}

#### Supported Assets (Inbound)

You can bridge the following stablecoins to MemeCore via Meson:

* `USDC`
* `USDT`

These assets are supported on the chains where Meson is live.

#### Bridged Asset Format on MemeCore

Regardless of which stablecoin you bridge into MemeCore via Meson (`USDT` or `USDC`), it will be received as:

> **`USDC.e`** (Meson, legacy) on MemeCore — `0x552791BE94B679cd0CeFB35c8AB0364973ACB37f`

* Meson `USDC.e` (legacy) follows Circle's contract standard for bridged USDC tokens. Its value is backed by the bridge's locking mechanism on the source chain.
* This is **not** the same token as Stargate `USDC.e`. See the migration section above.

#### Using Meson

1. Visit [https://meson.fi](https://meson.fi/)
2. Connect your wallet and select the source chain and asset (`USDT` or `USDC`)
3. Set the destination chain as **MemeCore**
4. Confirm the swap and wait for the asset to arrive as Meson `USDC.e`

***

### ⚠️ Important Notes

* Use only the **official interfaces**: [https://stargate.finance](https://stargate.finance/) and [https://meson.fi](https://meson.fi/). Bookmark them and beware of look-alike domains.
* Verify every token by its **contract address**. Two tokens on MemeCore share the symbol `USDC.e`; only the addresses on this page are official.
* MemeCore does not control the Stargate or Meson contracts or their bridging operations. Please use them at your own discretion.
* Cross-chain transfers usually complete within a few minutes, but can take longer during network congestion. Check the status on LayerZero Scan before retrying.

***

### Resources

* Stargate app: [https://stargate.finance](https://stargate.finance/)
* Stargate documentation: [https://docs.stargate.finance](https://docs.stargate.finance/)
* LayerZero Scan (transfer tracking): [https://layerzeroscan.com](https://layerzeroscan.com/)
* Meson Finance (legacy): [https://meson.fi](https://meson.fi/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.memecore.com/guides/bridging-stablecoins-to-memecore.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.