Company: CRCL
Filing Date: 2025-08-12
Form Type: S-1
Source: 0001193125-25-178989
Chunk: 100

Company: Circle Internet Group, Inc.
Filing Date: 2025-08-12
Form: S-1
Chunk 100
---
 uses the trademarks in a manner that suggests that such party is the issuer of such stablecoin. If our trademarks are assigned to Coinbase, we will have no control over how such trademarks and trade names may be used by Coinbase and any third-party licensees. Any misuse or inconsistent use of such trademarks and trade names may cause consumer confusion and jeopardize the value of our brand and products. Furthermore, if we fail to make any royalty payments due to Coinbase under the Flipped Trademark License Agreement, Coinbase may terminate the agreement and/or the licenses granted therein. As it relates to USDC (or any other stablecoin that we issue under the Collaboration Agreement), failure to be able to use the relevant trademarks could have a significant and detrimental effect on our ability to operate as the issuer of USDC or other stablecoin. Any forced assignment of or other loss of rights to use our trademarks under the terms of the Collaboration Agreement could have a material adverse effect on our business, results of operations, financial condition, and prospects.

Our and the Circle stablecoin ecosystem’s partners’ products and services, including the blockchains on which the Circle stablecoins protocols are built, contain third-party open-source software components. Failure to comply with the terms of the underlying open-source software licenses could harm our business.

Our products and services contain software modules licensed to us by third-party authors under “open-source” licenses. Also, the blockchains on which the Circle stablecoins protocols are built and the other partners in the Circle stablecoin ecosystem materially rely on open-source licenses to operate. We also make certain of our own software available to customers for free under various open-source licenses. Use and distribution of open-source software may entail greater risks than use of third-party commercial software, as open-source licensors generally do not provide support, warranties, indemnification, or other contractual protections regarding infringement claims or the quality of the code. In addition, the public availability of such software may make it easier for others to compromise our products and services.

Some open-source licenses contain requirements that we make available source code for modifications or derivative works we create based upon the type of open-source software we use, or grant other licenses to our intellectual property. If we combine our proprietary software with open-source software in a certain manner, we could, under certain open-source licenses, be required to release the source code of our proprietary software to the public. This would allow our competitors to create similar offerings with lower development effort and time and ultimately could result in a loss of our competitive advantages. Alternatively, to avoid the public release