Company: CRCL
Filing Date: 2025-02-13
Form Type: DRS/A
Source: 0000950123-25-001965
Chunk: 105

Company: Circle Internet Group, Inc.
Filing Date: 2025-02-13
Form: DRS/A
Chunk 105
---
. § 200.83

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
of the affected portions of our source code, we could be required to expend substantial time and resources to reengineer some or all of our software.

Although we
monitor our use of open-source software to avoid subjecting our products and services to conditions we do not intend, we have not recently conducted an extensive audit of our use of open-source software and, as a result, there can be no assurance
that our processes for controlling our use of open-source software in our products and services are, or will be, effective. If we are held to have breached or failed to fully comply with all the terms and conditions of an open-source software
license, we could face litigation, infringement, or other liability. We may also be required to seek costly licenses from third parties to continue providing our offerings on terms that