Five US Regional Banks Launch the Cari Network -- FDIC-Insured Tokenized Deposits to Challenge Stablecoins

The Banks Are Fighting Back – And They Brought FDIC Insurance

Something genuinely consequential happened this week in the intersection of traditional banking and blockchain infrastructure. Five US regional banks – First Horizon ($84B assets), Huntington Bancshares ($225B), KeyCorp ($184B), M&T Bank ($214B), and Old National Bancorp ($72B) – formally announced the Cari Network, a permissioned blockchain-based platform for tokenized bank deposits. Leading the initiative is Eugene “Gene” Ludwig, the 27th Comptroller of the Currency under President Clinton, and a figure who arguably understands the regulatory architecture of US banking better than anyone alive.

This is not another crypto experiment. This is the regulated banking system adopting blockchain rails to compete directly with stablecoins – and doing it with FDIC deposit insurance intact.

What Is the Cari Network, Exactly?

At its core, the Cari Network creates deposit tokens: digital representations of actual customer deposits denominated in US dollars, held at chartered banks participating in the network. These tokens are recorded on a permissioned blockchain, enabling 24/7, always-on, programmable money movement between participating institutions and their customers.

The critical legal distinction here is that each Cari token is a liability of the issuing bank. The deposit sits on the bank’s balance sheet. It is subject to all existing bank regulation – capital requirements, AML/KYC compliance, safety and soundness examination. And because it remains a bank deposit in the legal sense, it retains eligibility for FDIC insurance up to the standard $250,000 per depositor, per institution limit.

The timeline is aggressive but staged: Minimum Viable Product by end of March 2026, a pilot program in Q3, and commercial launch by Q4 2026.

Why This Matters for Stablecoin Competitors

The stablecoin market, dominated by Tether (USDT) and Circle (USDC), currently moves over $150 billion in daily volume. But stablecoins have a structural vulnerability that the Cari Network directly exploits: they are not deposits, and they are not FDIC-insured.

When you hold USDC, you hold a claim on Circle’s reserves – a mix of short-term Treasuries and cash held at partner banks. If Circle fails, your recourse is through bankruptcy proceedings, not FDIC resolution. The GENIUS Act, signed in July 2025, established a federal regulatory framework for payment stablecoins, but it did not grant them deposit insurance status. That distinction is enormous.

With Cari tokens, the depositor’s relationship is with a regulated, examined, FDIC-insured bank. The token is just the delivery mechanism. The underlying economics are identical to a traditional bank deposit.

The Programmability Angle

Beyond insurance, the Cari Network introduces programmable money features that traditional bank wires and ACH cannot match. Smart contract logic can be embedded into token transfers – think automatic escrow release upon delivery confirmation, conditional payments tied to real-world events, or automated treasury sweeps across multiple bank relationships.

This is the functionality that DeFi protocols have been building in the unregulated space for years. The Cari Network aims to bring that same programmability into a fully regulated, compliant-first environment. The network was co-developed with the bank partners from the ground up to meet the business, operational, and regulatory needs of financial institutions.

Gene Ludwig: The Regulatory Chess Master

Ludwig’s involvement is not incidental – it is the strategic cornerstone of this entire initiative. After serving as OCC Comptroller from 1993 to 1998, he founded Promontory Financial Group, the most influential regulatory consulting firm in banking, which IBM acquired in 2016. He retired from that role in 2021. The man has spent three decades at the nexus of banking regulation and financial innovation.

His presence signals to regulators, bank boards, and institutional investors that this network is being built within the guardrails, not despite them. Ludwig has publicly framed the Cari Network as a way for regional and community banks to offer stablecoin-like functionality without leaving the regulatory perimeter.

The Liquidity Argument

There is a macroeconomic angle here that deserves attention. When consumers convert fiat into stablecoins, that money effectively leaves the banking system’s balance sheet. It sits in reserves backing the stablecoin, reducing the money multiplier effect and weakening banks’ capacity to lend. The New York Fed has published research on this dynamic, reviving the “narrow banking” debate.

Tokenized deposits solve this problem entirely. The funds remain on the bank’s balance sheet, available for lending, investing, and general liquidity management. For the five Cari Network banks – collectively holding nearly $780 billion in assets – this is not an abstract concern. Deposit outflows to stablecoins are an existential competitive threat.

What to Watch

Initially, the Cari Network will be limited to customers of the five participating banks transferring funds between each other. This controlled scope allows the banks to ensure robust AML controls are in place before expanding access. The real question is whether this consortium model can scale – both in terms of participating banks and in terms of the programmable use cases built on top of the network.

For those of us in the Web3 infrastructure space, this is a pivotal moment. The regulated banking system is not ignoring blockchain – it is co-opting it. Whether that is good for decentralization is a separate debate, but for mainstream adoption of tokenized value transfer, the Cari Network may end up being the most important launch of 2026.

I would love to hear perspectives from the community. Is this the beginning of the end for stablecoins as we know them, or can both models coexist?

Great breakdown, Rachel. I want to push back on the framing that this is the beginning of the end for stablecoins, because I think it fundamentally misunderstands why stablecoins exist in the first place.

Stablecoins did not grow to $150B+ in daily volume because people were desperate for FDIC insurance on-chain. They grew because they are permissionless. Anyone, anywhere in the world, can hold USDC or USDT without a bank account, without KYC (on decentralized exchanges), and without asking permission from a five-bank consortium in the American Midwest.

The Cari Network is a permissioned blockchain. Its initial scope is limited to customers of those five banks moving money between each other. That is a fancy interbank settlement layer – useful, sure, but it is not competing in the same arena as stablecoins in the DeFi ecosystem.

Consider the use cases that drive stablecoin adoption today:

  • Cross-border remittances where users in emerging markets need dollar-denominated value without local banking infrastructure
  • DeFi lending and liquidity provision on protocols like Aave, Compound, and Morpho
  • DEX trading pairs as the base settlement asset across thousands of on-chain markets
  • Yield farming strategies that depend on composability with permissionless smart contracts

Can Cari tokens be deposited into an Aave lending pool? Can they be paired on Uniswap? Can a farmer in Nigeria hold them without a Huntington Bancshares account? The answer to all of these is no, and that tells you everything about the actual competitive overlap.

Where the Cari Network does compete is in institutional and corporate treasury management. For a mid-market CFO who banks at M&T and needs to move $5 million to a supplier who banks at KeyCorp at 2 AM on a Saturday, this is genuinely transformative. That is a real pain point. ACH takes days, wires have limited hours, and neither is programmable.

But let us not confuse an interbank settlement upgrade with a stablecoin killer. These are different tools serving fundamentally different markets. The DeFi economy runs on permissionless composability – Cari runs on bank compliance committees. Both can thrive.

Diana makes fair points about permissionless vs. permissioned, but I think she is underweighting the institutional capital flows angle. Let me put some numbers on this.

The five Cari Network banks collectively hold roughly $780 billion in assets. The entire stablecoin market cap is around $230 billion. These banks do not need to capture the DeFi degen market – they need to prevent their corporate depositors from migrating to Circle and Tether for faster settlement.

Here is the tokenomics problem for stablecoins that nobody talks about enough: stablecoins break the fractional reserve banking model. The New York Fed’s research on this is clear. When a corporate treasurer moves $50 million from their M&T demand deposit into USDC, that $50 million leaves M&T’s balance sheet. Circle parks it in T-bills and repo agreements. M&T loses the ability to lend against those deposits. Multiply that across the banking system and you get a meaningful contraction in credit availability.

The Cari Network solves this from the banks’ perspective because the tokenized deposit stays on the balance sheet. The bank retains its lending capacity. The customer gets 24/7 programmable transfers. It is a Pareto improvement for the bank-customer relationship.

Now, from a token design standpoint, I have questions:

  1. Interoperability: Can a Cari token issued by First Horizon be seamlessly accepted by a KeyCorp customer? What is the atomic settlement mechanism between different issuing banks? This is the technical core of the entire value proposition and the details are still opaque.

  2. Yield dynamics: Traditional deposits earn interest. Will Cari tokens carry yield? If so, this makes them strictly superior to stablecoins for institutional holders, since USDC and USDT do not pass through yield to holders (Circle keeps the Treasury income).

  3. Scalability beyond five banks: The consortium model has a mixed track record in banking. Remember R3 Corda? The value of a payment network scales with the number of participants. Five banks is a proof of concept, not a network effect.

The Q4 commercial launch timeline is ambitious. The MVP in March will be the real tell – if the atomic settlement between different bank-issued tokens works cleanly, this could be the most significant payments infrastructure development since FedNow. If it is clunky and requires manual reconciliation, it is just another consortium pilot that fades away.

I am cautiously optimistic. The economic incentives are strongly aligned for the banks, and Ludwig knows how to navigate the regulatory maze. But execution is everything.

As someone who has spent the last four years building fintech products that bridge crypto rails and traditional banking, this announcement hits differently than most “banks doing blockchain” press releases. Let me explain why from a builder’s perspective.

The number one pain point I hear from our enterprise customers is settlement finality on weekends and holidays. We have clients running supply chain finance platforms where a delayed payment on a Friday afternoon creates a cascading liquidity crunch that costs real money. ACH batch processing is a relic. Fedwire closes at 7 PM ET. Even FedNow, while 24/7, has adoption challenges and transaction limits that make it impractical for larger corporate flows.

The Cari Network, if it delivers on the programmability promise, could be the infrastructure layer that finally makes real-time B2B payments work at scale within the regulated banking system. The smart contract angle Rachel mentioned – automatic escrow release, conditional payments, treasury sweeps – these are exactly the features we have been hacking together with stablecoin workarounds and off-chain oracles.

But here is my concern as a startup founder: closed consortiums tend to innovate slowly. The history of banking technology is littered with consortium projects that launched with fanfare and then got bogged down in governance disputes, competing priorities among member banks, and glacial feature development cycles. SWIFT gpi took years to roll out basic tracking. R3 raised hundreds of millions and then largely pivoted away from its original interbank vision.

What would make me genuinely excited is if the Cari Network publishes open APIs and developer documentation that allow fintech companies to build on top of their token rails. If it remains a walled garden accessible only through direct bank relationships, it will serve a narrow institutional market and miss the broader opportunity.

The other thing I am watching closely is how community and regional banks beyond the initial five join the network. Ludwig has explicitly positioned this as a solution for smaller banks to compete with Big Tech and stablecoin issuers. If onboarding bank number 50 or bank number 200 is as painful as typical core banking integrations, the network effect will never materialize.

Cautiously bullish, but I will reserve judgment until I see the March MVP and whether any developer-facing tools emerge alongside it.

I want to zoom out from the stablecoin competition narrative and talk about what this means for blockchain infrastructure builders – which is what most of us on this forum actually are.

The Cari Network is built on a permissioned blockchain. They have not publicly disclosed the underlying technology stack, but the design philosophy is clear: compliance-first, bank-grade security, controlled validator set. This is the opposite of the open, permissionless ethos that most of us build on. And yet, I think it is an enormously positive signal for the entire blockchain ecosystem.

Here is why: legitimacy breeds infrastructure investment.

Every time a consortium of $780 billion in combined bank assets says “we are building on blockchain,” it validates the core technology thesis. It makes it easier for every other enterprise to justify blockchain R&D budgets. It creates demand for blockchain engineers, auditors, and tooling developers. The talent pipeline that trains on permissioned enterprise chains eventually feeds into the permissionless ecosystem too.

From a technical architecture perspective, I am fascinated by the settlement design challenge. In a multi-issuer deposit token system, you need:

  • Atomic swap capabilities between tokens issued by different banks (a First Horizon token for a KeyCorp token must settle simultaneously to avoid counterparty risk)
  • Real-time reserve verification to ensure each token is fully backed by an actual deposit at the issuing bank
  • Privacy-preserving transaction logic since commercial banks cannot expose customer payment data on a shared ledger, even a permissioned one
  • Regulatory reporting hooks that give examiners and the FDIC real-time visibility into token activity without compromising customer privacy

These are non-trivial engineering challenges. If Cari solves them cleanly, the solutions will likely influence how tokenized assets are designed across both permissioned and public chains.

The BIS published a bulletin comparing stablecoins and tokenized deposits, and their conclusion was essentially that tokenized deposits are the institutional-grade version of the same fundamental innovation. I tend to agree. We are watching the bifurcation of the digital dollar market into two tiers: permissionless stablecoins for the open internet economy, and permissioned deposit tokens for the regulated financial system.

For those of us building API infrastructure and node services at BlockEden.xyz and similar platforms, the question is whether permissioned networks like Cari will eventually need bridge infrastructure to interact with public chains. If a corporate treasury wants to move value from a Cari deposit token into an on-chain DeFi strategy, that bridge becomes critical infrastructure. That is where I see the long-term opportunity for our community.

The banks are validating blockchain. Now we need to build the connective tissue.