I honestly feel bad for newbies to crypto and I find myself somewhat doubtful of how mass adoption is supposed to hit with issues like this.
Initially, there was no "native" version of USDC on Arbitrum, such that you could only use a bridged version where USDC on Ethereum, for example, is sent to a contract which burns it, and then sends you back basically a USDC equivalent on Arbitrum. The process is the same in reverse to get USDC from Arbitrum back to Ethereum.
Now, there is a native version where Circle(the issuer of USDC) has directly issued USDC on Arbitrum and directly manages the USDC token on Arbitrum. So now there are two versions of USDC. To add insult to injury, some exchanges and platforms refer to the bridged(non-native/old) version as USDC.e and the native version simply as USDC. But not all of them do. Metamask for example, and MEXC as well, still call both by the same name of "USDC".
With all this confusion, you can end up ending sending bridged USDC to an exchange or wallet when you meant to send native USDC. You may also end up withdrawing native USDC and see it doesn't show up because you actually wanted bridged USDC. If you send to an exchange you will only be lucky if the exchange supports both versions on the same deposit address. In my experience however, I see many exchanges only support one version thus far. Kraken is the only exchange as far as I know with the care and foresight to support both tokens for deposits as well as using the same deposit address for both versions. This benefits Kraken users hugely.
[link] [comments]
You can get bonuses upto $100 FREE BONUS when you:
π° Install these recommended apps:
π² SocialGood - 100% Crypto Back on Everyday Shopping
π² xPortal - The DeFi For The Next Billion
π² CryptoTab Browser - Lightweight, fast, and ready to mine!
π° Register on these recommended exchanges:
π‘ Binanceπ‘ Bitfinexπ‘ Bitmartπ‘ Bittrexπ‘ Bitget
π‘ CoinExπ‘ Crypto.comπ‘ Gate.ioπ‘ Huobiπ‘ Kucoin.
Comments