21 Institutions Unite on a Public-Chain Stablecoin

A group of 21 international financial institutions has committed to establish a new company supporting a public-chain stablecoin solution. The group plans to focus first on a US dollar-denominated offering, prioritize a euro-denominated product as it expands, and target market entry in the first half of 2027. The announcement signals that regulated institutions increasingly view public blockchains as financial distribution and settlement infrastructure, but the proposed company and product still have substantial governance, compliance, and operational work ahead.

What Did the 21 Institutions Announce?

On September 1, 2026, Wells Fargo announced on behalf of the group that 21 institutions had committed to establish a new company in the second half of 2026, subject to closing conditions. The company name has not yet been disclosed.

The initiative intends to operate globally. Its initial focus is a US dollar-denominated stablecoin, followed by possible stablecoins tied to other G7 currencies, with a euro offering identified as the priority. The stated use cases span wholesale, institutional, and retail markets, including cross-border payments and digital asset settlement.

The participant list reaches across five regions:

• North America: Bank of America, Capital One, Citi, Fidelity Investments, Goldman Sachs, PNC Financial Services, Scotiabank, TD Bank Group, Wells Fargo, and WisdomTree
• Europe: Banco Santander, BBVA, Commerzbank, Credit Agricole, Deutsche Bank, Lloyds Banking Group, Rabobank, and UBS
• East Asia: MUFG Bank
• Middle East: Sirius International Holding
• Africa: Standard Bank

This is broader than a bank-only project, so the most accurate description is a consortium of financial institutions. It combines commercial banks, investment and asset management organizations, and other financial groups with existing customer distribution, treasury capabilities, compliance programs, and risk expertise.

Why a Public-Chain Stablecoin Matters

A public-chain stablecoin is an issuer-backed digital asset designed to circulate on open blockchain networks while maintaining a stable reference value. Public blockchains make the asset available to external wallets, applications, exchanges, and payment services without requiring every participant to connect to a closed ledger operated by the issuer.

That distribution model creates strategic benefits for financial institutions:

1. A shared settlement asset can move across organizations and applications.
2. Programmable transfers can support automated treasury and payment workflows.
3. Public-chain availability can connect institutional liquidity with digital asset markets.
4. Always-on networks can support settlement outside traditional banking hours.
5. Standard blockchain interfaces can reduce some bilateral integration work.

The announcement follows an October 2025 exploration by an initial group of 10 banks into a 1:1 reserve-backed form of digital money available on public blockchains. The expanded group and planned company show movement from research toward an operating structure.

However, a commitment to form a company is not the same as a launched stablecoin. The closing conditions, company formation, product design, reserve framework, network selection, regulatory treatment, and production controls remain prospective. The first-half 2027 target is an objective, not a guaranteed launch date.

The Governance Model Is Part of the Product

For an institution-led public-chain stablecoin, governance is not a back-office detail. It determines who can authorize issuance, change policies, approve supported networks, manage incidents, and resolve conflicts across the consortium.

The announcement highlights bank-grade compliance, strong governance, distribution, and institutional risk management. Turning those principles into an operating model will require clear decision rights across at least five areas.

Issuance and Redemption

The operating company will need rules for creating and redeeming tokens, verifying the assets backing circulation, managing liquidity, and reconciling token supply with reserve records. Privileged actions should use tightly controlled authorization, separation of duties, and complete audit trails.

Network Admission

Every supported public blockchain introduces different finality, upgrade, fee, smart contract, and incident assumptions. The consortium will need a consistent standard for adding, monitoring, pausing, and retiring network deployments.

Software and Contract Changes

Stablecoin contracts and supporting services may need upgrades. Governance must define proposal, review, testing, approval, deployment, and rollback procedures. Emergency controls should be narrow, documented, and observable.

Compliance Policy

The group intends the initiative to comply with the US GENIUS Act and the European Union's Markets in Crypto-Assets framework where applicable. That intent must be translated into product eligibility, disclosures, reserve management, sanctions controls, transaction monitoring, reporting, and jurisdiction-specific operating procedures.

Incident Response

Public blockchains run continuously, so the operating model must cover events outside normal banking hours. A credible response plan should establish severity levels, decision authority, communication procedures, evidence preservation, and recovery objectives across the issuer, infrastructure providers, custodians, exchanges, and distribution partners.

Public Networks Require Institutional Controls

The public-chain stablecoin model combines open network access with controlled issuance. Anyone may be able to read the ledger or interact with a token contract, but the issuer remains responsible for reserve management, regulated activities, and privileged operations.

This creates a hybrid control environment. Some responsibilities sit with the issuer, while others depend on the selected blockchain and the applications that use the asset.

No single participant controls the full stack. The product therefore needs contracts, operating agreements, technical monitoring, and escalation paths that make shared accountability explicit.

Multichain Distribution Raises the Infrastructure Bar

The announcement refers to a stable payment asset available on public blockchains, which suggests a multichain question even though no networks have been named. A public-chain stablecoin can only reach diverse markets if applications can access the relevant chains reliably and if the issuer can operate each deployment under a consistent control model.

Supporting more than one network multiplies operational states. Infrastructure teams must track contract addresses, chain identifiers, finality rules, software upgrades, fee balances, transaction receipts, indexed events, and endpoint health separately for every chain. Crosschain transfer mechanisms add message, attestation, liquidity, or bridging states that also require reconciliation.

An institutional rollout should evaluate public networks against practical requirements:

• Finality characteristics and reorganization risk
• Validator and infrastructure decentralization
• Contract security and upgrade capabilities
• Node client maturity and release practices
• RPC capacity, latency, and geographic resilience
• Data indexing and historical access
• Fee stability and operational predictability
• Incident history and governance responsiveness
• Wallet, exchange, custodian, and application support

Network selection should not be reduced to transaction speed or fees. The public-chain stablecoin will operate inside payment and settlement processes where stale data, inconsistent transaction status, or missed events can become financial and compliance exceptions.

RPC and API Reliability Becomes a Financial Control

Applications use blockchain nodes and RPC endpoints to query balances, estimate fees, submit transactions, monitor confirmations, and retrieve token events. If the access layer is unavailable or inconsistent, a payment may appear pending after it has settled, a treasury system may retry unnecessarily, or a compliance engine may miss a relevant event.

For a public-chain stablecoin, reliable blockchain access should be designed as part of the control environment. Relevant measures include:

• Multiple independent endpoints with health-based routing
• Current-state checks across providers for critical reads
• Idempotent transaction submission and retry logic
• Complete preservation of transaction and request identifiers
• Confirmation policies calibrated to each network
• Continuous contract event ingestion and gap detection
• Monitoring for chain stalls, reorganizations, and provider divergence
• Tested failover that preserves audit and reconciliation data

High availability means more than receiving a successful HTTP response. The data must reflect the correct chain and sufficiently current state for the financial decision being made.

Reconciliation Must Connect Onchain and Offchain Records

A reserve-backed stablecoin crosses multiple ledgers. The issuer records customer funds and reserve assets. The blockchain records token issuance, transfers, and redemption burns. Banks, exchanges, custodians, payment processors, and enterprise users maintain their own balances and transaction states.

The operating company will need reconciliation that connects those records without assuming that identical timestamps or identifiers exist across systems. A complete trace can link the customer request, authorization, bank movement, token transaction, chain confirmation, internal ledger entry, fees, and exception status.

For a multichain product, supply reconciliation should account for every canonical contract and any approved crosschain mechanism. Teams should be able to explain whether a token is newly issued, transferred between networks, held in a controlled intermediary contract, redeemed, or awaiting a final state.

Exception handling deserves the same design attention as the happy path. The system should define when an incomplete transaction becomes overdue, who investigates it, which evidence is preserved, and how customers receive an accurate status without triggering duplicate actions.

What Institutions Should Validate Before the 2027 Target

The public-chain stablecoin initiative has time before its stated market target, but the longest-lead controls should be tested early.

Confirm the Governance and Legal Perimeter

Define the issuer, reserve holder, redemption obligation, distribution roles, jurisdictional responsibilities, and decision rights across the consortium. Product language should distinguish commitments from dependencies and future options.

Test the Complete Issuance Lifecycle

Run issuance and redemption from customer instruction through banking rails, authorization, onchain execution, internal accounting, reporting, and exception resolution. Include reversals, rejected instructions, delayed settlement, and network disruption.

Use Network-Specific Readiness Gates

Require security review, performance testing, finality analysis, node diversity, monitoring coverage, and incident exercises before enabling each chain. A network should not enter production only because a contract deployment succeeds.

Build Continuous Evidence

Automate the collection of access logs, approval records, contract events, supply reconciliation, endpoint health, software versions, and incident timelines. Audit readiness is easier when evidence is a routine operating output rather than a periodic reconstruction.

Exercise Cross-Organization Incidents

Simulate a chain halt, RPC divergence, contract alert, reserve mismatch, and sanctions escalation. The consortium should know who has authority to pause an activity, how information moves across participants, and which recovery criteria restore service.

How InfStones Supports Institutional Blockchain Operations

InfStones provides enterprise-grade node and API infrastructure through a cloud-agnostic platform. For institutions connecting financial applications to public blockchains, production-grade access can reduce the operational burden of running and updating separate node fleets for every supported network.

Institutional-grade node and data infrastructure supports the access layer with high-availability architecture, automated failover, blockchain data services, and APIs designed for multichain applications. These capabilities can help payment, treasury, custody, and compliance systems maintain dependable connectivity as their network coverage expands.

InfStones is not presented as a participant in the announced consortium. The connection is operational: a public-chain stablecoin needs reliable node and API infrastructure alongside issuer governance, reserves, compliance, custody, liquidity, and application controls.

Frequently Asked Questions

Has the consortium already launched a stablecoin?

No. The 21 institutions have committed to establish a new company, subject to closing conditions. The group aims to bring a stablecoin solution to market in the first half of 2027.

Which currencies will the public-chain stablecoin support?

The initial focus is a US dollar-denominated offering. The group has a longer-term ambition to add stablecoins tied to other G7 currencies, with a euro offering named as the priority.

Which public blockchains will be supported?

The September 1 announcement does not name any specific public blockchains. Network choices, deployment structure, interoperability, and launch sequence remain to be disclosed.

Is the new company already formed?

The institutions said they committed to establish the company in the second half of 2026, subject to closing conditions. Its name has not yet been announced.

Why do node and API services matter to a stablecoin issuer?

Stablecoin operations depend on current blockchain state, reliable transaction submission, contract event monitoring, supply reconciliation, and incident response. Nodes and APIs provide the access layer for those controls across each supported network.

Looking Ahead: Trust Moves Into Operations

The 21-institution initiative is important because it combines public blockchain distribution with the governance, compliance, and risk capabilities of major financial organizations. It also exposes the size of the operating challenge. A trusted name and a reserve promise do not by themselves create a dependable global payment asset.

The public-chain stablecoin will need to make trust observable through authorized issuance, transparent supply records, consistent redemption processes, resilient network access, complete reconciliation, and tested incident response. Its credibility will be built through the routine performance of those controls across every institution, vendor, and blockchain in the system.

As the group works toward the first half of 2027, the most consequential decisions may happen below the product interface. Enterprise-grade governance and production-grade, cloud-agnostic infrastructure will determine whether the proposed stablecoin can move from institutional commitment to reliable financial infrastructure.