Circle CCTP Adds Stellar Support, Assigning Stellar as Domain 27

Circle CCTP Adds Stellar Support, Assigning Stellar as Domain 27

N
News Editor
2026-06-19 05:54:51
Circle announced on X that Circle CCTP now supports Stellar. The accompanying Release Notes episode explains what changed, how Stellar fits into CCTP as domain 27, and the integration points builders should review before moving USDC to or from Stellar.
CircleCCTPStellarUSDCTechnology

Circle posted on X that Circle CCTP is now supported on Stellar. The update was presented through Circle’s @circleCCTP account and referenced @StellarOrg, placing the focus on the addition of Stellar to the CCTP environment. Foresight categorized the item under technology developments, and the headline states that Stellar has been assigned as the 27th domain within CCTP.

Stellar enters CCTP as domain 27

In the Release Notes episode referenced by Circle, the company says it covers what changed, how Stellar fits into CCTP as domain 27, and the key integration details builders should know before moving USDC to or from Stellar. The phrase domain 27 is the domain number used in the announcement to identify Stellar’s role in this CCTP integration.

The post is not presented as a market update or a trading-data item. It is written for builders who need implementation guidance before supporting USDC movements involving Stellar. Circle did not include additional on-chain figures or a separate deployment schedule in the provided text. Instead, the listed topics are technical points that builders are directed to review in the Release Notes episode.

Integration items named in the Release Notes

The first item Circle says viewers can learn about is Stellar address handling. The announcement does not provide a sample address or a separate address-format explanation, but it names address handling as one of the main topics for developers working with USDC transfers to or from Stellar.

The second named topic is the CctpForwarder contract. The post lists the contract by name and includes it among the key integration details builders should know. No additional contract parameters are included in the source text. The third topic is USDC precision on Stellar. Circle identifies this as a specific item in the episode, while the provided post does not state a particular decimal setting or a numerical precision value.

The fourth item is where to find the quickstart. Circle places the quickstart location alongside Stellar address handling, the CctpForwarder contract, and USDC precision on Stellar. Together, these four items form the learning checklist that Circle highlights for builders before they move USDC to Stellar or move USDC from Stellar.

Video and page details

The video information shown in the source includes 00:00 and 21:29, with the page also displaying the date 2026年6月18日. The post shows 6048 Views and a Read 9 replies entry. The scraped source content also contains number-flow-react page-component text and the visible component numbers 9, 24, 148, and 8, which appear as part of the original page display or captured interface data.

The original source URL for the item is Circle’s X status page at https://x.com/circle/status/2067721402095206425?s=20. The publication timestamp provided for this rewritten article is 2026-06-19T05:54:51.000Z, and the detected time in the input is 2026-06-19T06:00:52.466Z. The input also states SourceType as api_json, DelayMinutes as 6, and FreshnessScore as 13. The fetch status indicates that the full content was fetched, and the FetchedFromUrl field matches the same X link.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
300

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.