Circle Launches Native USDC On NEAR Protocol

Circle Launches Native USDC On NEAR Protocol

Financial technology company Circle, the issuer of USD Coin (USDC), announced the native stablecoin liquidity access on the NEAR protocol ecosystem. The USDC NEAR access can be gained from Circle Account and Circle APIs, the company announced on Wednesday.

Also Read: US PPI Comes In Hotter Than Expected, But Crypto Market Remains Steady


The NEAR USDC pairing can be accessed through Circle Account and Circle APIs for various use cases including low cost payments and remittances globally, 24/7 trading, borrowing and lending, and enabling users to hold savings in digital dollars without a bank account. Circle revealed the announcement in a statement:

“We are announcing that USDC is now available natively on NEAR and accessible from Circle Account and Circle APIs. Developers can now take advantage of the speed and scalability of the NEAR blockchain to build fast, user friendly apps with USDC.”

The new access addition comes after Circle gaining a massive stranglehold in the US crypto ecosystem with crypto exchange Coinbase purchasing a stake in the company. This could go on to be a key partnership as regulators could favor it as both are United States based companies. Earlier, CoinGape reported that on June 1, 2023, a similar announcement was made on introducing USDC natively on the Arbitrum Layer 2 network.

Also Read: Polygon Releases Proposals On Ambitious Ethereum Scaling And POL Token

✓ Share:

Anvesh reports major crypto updates around U.S. regulation and market moving trends. Published over 1,200 articles so far on crypto and blockchain. A proud dropout of University of Massachusetts, Lowell. Can be reached at or or

The presented content may include the personal opinion of the author and is subject to market condition. Do your market research before investing in cryptocurrencies. The author or the publication does not hold any responsibility for your personal financial loss.


Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!