From 94d28a707b678e653a6b40a267648a244ceb49e3 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Wed, 4 Dec 2024 17:22:24 +0100 Subject: [PATCH 1/3] Cleared confusion --- .../app-developers/bridging/standard-bridge.mdx | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/pages/builders/app-developers/bridging/standard-bridge.mdx b/pages/builders/app-developers/bridging/standard-bridge.mdx index 73eb844d6..645febb38 100644 --- a/pages/builders/app-developers/bridging/standard-bridge.mdx +++ b/pages/builders/app-developers/bridging/standard-bridge.mdx @@ -239,13 +239,12 @@ The address of this entry is the address of the bridged representation of the to ## Special considerations -### USDC +### USDC on OP Mainnet -[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. + +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). + Information about the bridged `USDC.e` token and native USDC token can be found below. From aca8b18ceec87fde8718882008140391c4e20550 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Wed, 4 Dec 2024 17:53:04 +0100 Subject: [PATCH 2/3] Moved the USDC on OP Mainnet to another section. --- .../bridging/standard-bridge.mdx | 18 +----------------- pages/chain/tokenlist.mdx | 15 +++++++++++++++ 2 files changed, 16 insertions(+), 17 deletions(-) diff --git a/pages/builders/app-developers/bridging/standard-bridge.mdx b/pages/builders/app-developers/bridging/standard-bridge.mdx index 645febb38..144868c86 100644 --- a/pages/builders/app-developers/bridging/standard-bridge.mdx +++ b/pages/builders/app-developers/bridging/standard-bridge.mdx @@ -235,20 +235,4 @@ Once you've found the token you want to bridge, look for the token's name and sy 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. - - -## Special considerations - -### USDC on OP Mainnet - - -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). - - -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) | + \ No newline at end of file diff --git a/pages/chain/tokenlist.mdx b/pages/chain/tokenlist.mdx index ac2301614..e844ff934 100644 --- a/pages/chain/tokenlist.mdx +++ b/pages/chain/tokenlist.mdx @@ -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.** +### USDC on OP Mainnet + + +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). + + +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 From 51c55e02b6ce3147b66969468bab9ab70de68444 Mon Sep 17 00:00:00 2001 From: Blessing Krofegha Date: Wed, 4 Dec 2024 18:20:02 +0100 Subject: [PATCH 3/3] fix lint issues --- .../bridging/standard-bridge.mdx | 32 +++++++++---------- pages/chain/tokenlist.mdx | 2 +- 2 files changed, 16 insertions(+), 18 deletions(-) diff --git a/pages/builders/app-developers/bridging/standard-bridge.mdx b/pages/builders/app-developers/bridging/standard-bridge.mdx index 144868c86..09f87c962 100644 --- a/pages/builders/app-developers/bridging/standard-bridge.mdx +++ b/pages/builders/app-developers/bridging/standard-bridge.mdx @@ -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. - - 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. - + + 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. + ## Tutorials @@ -221,18 +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. + {

Find the token you want to bridge

} -{

Find the token you want to bridge

} + 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. + {

Find the bridged representation of the token

} -{

Find the bridged representation of the token

} - -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. - - \ No newline at end of file + 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. + diff --git a/pages/chain/tokenlist.mdx b/pages/chain/tokenlist.mdx index e844ff934..73f4f4c9b 100644 --- a/pages/chain/tokenlist.mdx +++ b/pages/chain/tokenlist.mdx @@ -20,7 +20,7 @@ This page is automatically generated from the Superchain Token List. ### USDC on OP Mainnet - + 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).