OpenUSD lists wrong partners in stablecoin alliance
OpenUSD published a partner list that included firms who said they had not agreed to join, prompting a corrected announcement and a review of its processes.
OpenUSD published a partner list for a planned stablecoin alliance that included several organizations that later said they had not agreed to participate. The announcement appeared on OpenUSD’s public channels earlier this week and was revised after the error came to light.
Several firms named in the original list issued statements saying they were not involved and had not consented to be presented as partners. The disputed names were removed from the updated announcement, but the initial disclosure had already circulated on industry discussion channels.
OpenUSD is an industry initiative focused on coordinating issuance and support for dollar-pegged tokens and related infrastructure. The announcement described an alliance intended to align technical and compliance practices among issuers, custodians and payment providers, and listed organizations described as potential participants in governance and technical workstreams.
OpenUSD acknowledged the mistake and said it will review how the partner list was compiled and how the announcement passed internal review. The organization’s revised materials say it will confirm formal agreements before public disclosures in future.
Industry representatives noted that partner lists for consortiums commonly reflect signed agreements or formal letters of intent. The original announcement relied on names that some firms said were included without formal consent, prompting questions about OpenUSD’s vetting and communications processes.
The error led to immediate corrections in public materials. Several companies publicly distanced themselves from the initiative as described in the first release. OpenUSD’s revision clarified the status of formal agreements for those remaining on the list.
OpenUSD said it would update stakeholders on any further changes and on the results of its internal review. The incident highlights the need for clear confirmation procedures when announcing collaborative industry projects involving technical standards and compliance arrangements.
Content on BlockPort is provided for informational purposes only and does not constitute financial guidance.
We strive to ensure the accuracy and relevance of the information we share, but we do not guarantee that all content is complete, error-free, or up to date. BlockPort disclaims any liability for losses, mistakes, or actions taken based on the material found on this site.
Always conduct your own research before making financial decisions and consider consulting with a licensed advisor.
For further details, please review our Terms of Use, Privacy Policy, and Disclaimer.








