Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move USDC Section to OP Mainnet-Specific #1160

Merged
merged 3 commits into from
Dec 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 14 additions & 33 deletions pages/builders/app-developers/bridging/standard-bridge.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -191,11 +191,11 @@ The Standard Bridge contracts can also be used to bridge ETH from Ethereum to OP
The ETH bridging process is generally less complex than the ERC-20 bridging process.
Users simply need to trigger and send ETH to the [`bridgeETH`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L143-L150) or [`bridgeETHTo`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L152-L166) functions on either blockchain.

<Callout>
Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`.
This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function.
You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page.
</Callout>
<Callout>
Users can also deposit ETH from Ethereum to OP Mainnet by sending a basic ETH transfer from an EOA to the `L1StandardBridgeProxy`.
This works because the `L1StandardBridgeProxy` contains a [`receive`](https://github.com/ethereum-optimism/optimism/blob/2e647210882d961f04055e656590d90ad98c9934/packages/contracts-bedrock/src/universal/StandardBridge.sol#L119-L121) function.
You can find the mainnet and testnet addresses on the [Contract Addresses](/chain/addresses) page.
</Callout>

## Tutorials

Expand All @@ -221,35 +221,16 @@ You can easily find the bridged representation of a token for OP Mainnet on the
If you want to find the bridged representation of a token for another chain, use the following steps.

<Steps>
{<h3>Find the token you want to bridge</h3>}

{<h3>Find the token you want to bridge</h3>}
The Superchain Token List is organized by the token's address and native blockchain.
[Search the token list](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) for the token you want to bridge to confirm that it's included in the list.
Make sure that the chain ID in the entry matches the chain ID of the blockchain you're bridging from.
Retrieve the token's name and symbol from the list.

The Superchain Token List is organized by the token's address and native blockchain.
[Search the token list](https://github.com/ethereum-optimism/ethereum-optimism.github.io/blob/master/optimism.tokenlist.json) for the token you want to bridge to confirm that it's included in the list.
Make sure that the chain ID in the entry matches the chain ID of the blockchain you're bridging from.
Retrieve the token's name and symbol from the list.

{<h3>Find the bridged representation of the token</h3>}

Once you've found the token you want to bridge, look for the token's name and symbol in the list.
Find the entry that matches the name and symbol of the token you want to bridge and where the chain ID matches the chain ID of the blockchain you're bridging to.
The address of this entry is the address of the bridged representation of the token you want to bridge.
{<h3>Find the bridged representation of the token</h3>}

Once you've found the token you want to bridge, look for the token's name and symbol in the list.
Find the entry that matches the name and symbol of the token you want to bridge and where the chain ID matches the chain ID of the blockchain you're bridging to.
The address of this entry is the address of the bridged representation of the token you want to bridge.
</Steps>

## Special considerations

### USDC

[Circle](https://www.circle.com/en/), the issuer of [USDC](https://www.circle.com/en/usdc?gad_source=1), natively issues USDC on OP Mainnet [as of September 2023](https://www.circle.com/blog/what-you-need-to-know-native-usdc-on-op-mainnet).
Before this service was made available, USDC had to be bridged to OP Mainnet via the Standard Bridge.
This bridged representation of USDC is referred to as `USDC.e`.

Circle recommends that users and developers make use of the native version of USDC issued by Circle over the bridged `USDC.e` token. Please note that the bridged `USDC.e` token will be deprecated in the near future.

Information about the bridged `USDC.e` token and native USDC token can be found below.

| Symbol | Description | Address |
| -------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `USDC.e` | Bridged USDC from Ethereum | [`0x7f5c764cbc14f9669b88837ca1490cca17c31607`](https://optimistic.etherscan.io/token/0x7f5c764cbc14f9669b88837ca1490cca17c31607) |
| `USDC` | Native USDC issued by Circle | [`0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85`](https://optimistic.etherscan.io/token/0x0b2c639c533813f4aa9d7837caf62653d097ff85) |
15 changes: 15 additions & 0 deletions pages/chain/tokenlist.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,21 @@ This page is automatically generated from the Superchain Token List.
**The presence of a token on this page does not imply any endorsement of the token or its minter.**
</Callout>

### USDC on OP Mainnet

<Callout>
The legacy bridged version of USDC (USDC.e) at address `0x7f5c764cbc14f9669b88837ca1490cca17c31607` is being deprecated on OP Mainnet.
Users and developers should migrate to using the native USDC token issued directly by [Circle](https://www.circle.com/en/), the issuer of [USDC](https://www.circle.com/en/usdc?gad_source=1).
</Callout>

Information about the bridged `USDC.e` token and native USDC token can be found below.

| Symbol | Description | Address |
| -------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `USDC.e` | Bridged USDC from Ethereum | [`0x7f5c764cbc14f9669b88837ca1490cca17c31607`](https://optimistic.etherscan.io/token/0x7f5c764cbc14f9669b88837ca1490cca17c31607) |
| `USDC` | Native USDC issued by Circle | [`0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85`](https://optimistic.etherscan.io/token/0x0b2c639c533813f4aa9d7837caf62653d097ff85) |


## OP Mainnet

<TokenListTable l1="1" l2="10" />
Expand Down
Loading