buildoncircle

Circle has often been launching native USDC on new blockchains after a large amount of USDC liquidity had already been bridged by third parties. While it’s true that developers and users can readily migrate from bridged USDC to native USDC, the ideal scenario would be to avoid a migration entirely.

So, how can Circle simultaneously enable an early path to native USDC for new blockchains, solve the cold start problem, and avoid the pitfalls of liquidity fragmentation and lengthy migrations?

This brings us back to permissionless composability and the power of community.

Introducing: Bridged USDC Standard

Circle has often been launching native USDC on new blockchains after a large amount of USDC liquidity had already been bridged by third parties. While it’s true that developers and users can readily migrate from bridged USDC to native USDC, the ideal scenario would be to avoid a migration entirely.

So, how can Circle simultaneously enable an early path to native USDC for new blockchains, solve the cold start problem, and avoid the pitfalls of liquidity fragmentation and lengthy migrations?

This brings us back to permissionless composability and the power of community.

Introducing: Bridged USDC Standard https://www.circle.com/blog/bridged-usdc-standard

Director of Community at Circle. Working to help builders of tomorrow, TODAY

0xistp.uni.eth｜KOR｜Data Mining｜Moderator of /base-kr｜Host of /skip

I just read the introduction below. It's an amazing project.
Native USDC has the advantage of high reliability and official support, while bridged USDC is used to provide initial liquidity. Bridged USDC can be upgraded to native USDC later on!