Bank deposit tokens (JPMD on Base) vs public stablecoins

Bank deposit tokens are not a cosmetic rebrand of stablecoins. JPMD on Base matters because it puts a bank liability on a public blockchain and asks a direct question that matters to compliance teams, treasurers, and wallet builders: when do you want tokenized bank money, and when do you want a broadly distributed public stablecoin? The answer is not ideological. It depends on who needs to hold the asset, who may redeem it, who controls issuance, and how much balance-sheet and operational risk you want in the stack.

01What JPMD actually is

J.P. Morgan launched JPMD as a proof of concept in June 2025 on Base, an Ethereum Layer 2. The bank describes it as a USD deposit token, backed 1:1 by deposits, available only to qualified institutional participants, and designed for near-instant 24/7 settlement. Base’s own announcement emphasizes that the token is permissioned and not available to retail users. J.P. Morgan also says the design can support onchain payments, treasury flows, liquidity management, and, potentially, interest-bearing functionality for holders.

That structure is important. A deposit token is not just a token that happens to be denominated in dollars. It is a claim on a bank liability. In practice, that means the issuer is not trying to build a standalone digital dollar ecosystem outside the banking system. It is trying to extend the bank’s existing money substrate onto a blockchain rail. That gives the bank tighter control over client onboarding, compliance, settlement policy, and treasury integration than a public token can usually offer.

The flip side is scope. JPMD is built for a narrow user base. It is optimized for institutions that already live inside banking and treasury workflows, not for an open internet of anonymous wallet holders. That is a feature, not a bug, if your priority is controlled settlement and bank-grade oversight. It is a limitation if your priority is broad distribution and easy integration into public crypto markets.

02How public stablecoins differ

Public stablecoins, by contrast, are designed to circulate broadly on public blockchains. Circle’s USDC materials are a good reference point because they make the model explicit: USDC is backed 1:1 by cash and highly liquid cash equivalents, reserves are attested monthly, and the token is supported across many blockchain networks. The stablecoin model is built around open transferability, broad wallet support, and redemption into fiat through the issuer’s rails.

That open transfer layer is what makes public stablecoins so useful. They can move across exchanges, wallets, payments apps, market makers, and DeFi protocols without each participant needing a bilateral banking relationship with the issuer. For builders, that means faster integration and a much larger potential user base. For market structure, it means deeper composability. A stablecoin can serve as cash in one app, collateral in another, and settlement asset in a third.

But “public” does not mean “untethered.” Circle’s terms make clear that redemption is conditional, that only eligible users can redeem directly with the issuer, and that the issuer can suspend activity in certain network failure or fork scenarios. So the distinction is not public versus regulated. It is more precise than that: public stablecoins are open transfer instruments on public chains, but the redemption layer remains issuer-controlled and policy-driven.

That is why public stablecoins have a different risk profile. They rely heavily on reserve quality, redemption mechanics, chain support, and operational continuity. Users are taking exposure not to a bank deposit ledger, but to the issuer’s reserve governance and the integrity of the token’s onchain and offchain plumbing.

03The regulatory split is widening

The regulatory picture now reinforces the distinction. In September 2026, the Federal Reserve proposed rules under the GENIUS Act for Board-supervised payment stablecoin issuers. The proposal would require stablecoins to be fully backed by permissible reserve assets such as short-term Treasury bills and certain other high-quality, liquid assets, while also creating capital and risk-management standards and a tailored application process for banks that want to issue payment stablecoins.

That matters because it shows the policy direction. Public stablecoins are being pulled toward a bank-like prudential perimeter, even when they are not bank liabilities. Regulators are converging on the idea that stablecoin issuers need explicit reserve discipline, operational controls, and clear supervision. The objective is not to make stablecoins identical to deposits. It is to narrow the gap enough that payment stablecoins can be trusted at scale.

Deposit tokens sit on the other side of that line. If the token is truly a bank liability inside the deposit franchise, the regulatory logic is different. The token inherits banking relationships, compliance functions, and supervisory expectations more directly than a reserve-backed stablecoin does. That can simplify some questions and complicate others. It may make institutional adoption easier where the bank already has the client, the controls, and the legal relationship. It may also make cross-ecosystem portability harder, because the token’s center of gravity is the bank, not the chain.

This is where the market is likely to bifurcate. Stablecoins are moving toward clearer federal rules. Bank deposit tokens are becoming a distinct institutional product category. They are adjacent, but not interchangeable.

04Where each model wins

JPMD is strongest where the user already wants a bank relationship. Think corporate treasury, cross-border intercompany flows, onchain cash management, and institutional settlement where the parties care more about KYC, account controls, and direct bank integration than about open access. If the institution is trying to move internal dollars onto a programmable rail, a deposit token is conceptually cleaner than a stablecoin. The balance-sheet asset stays inside the bank franchise, and the operational control surface remains familiar to compliance and treasury teams.

Public stablecoins win where network effects matter more than bank integration. They are better suited to open distribution, 24/7 liquidity across venues, and application-layer composability. If a payment app, exchange, remittance product, or trading protocol needs a digital dollar that can move between many counterparties without bespoke onboarding every time, a public stablecoin is usually the more practical primitive.

There is also a difference in market plumbing. A deposit token can be a very efficient instrument inside a single institution’s ecosystem, but it may not immediately benefit from the broad liquidity network that public stablecoins have already built across exchanges, wallets, and protocols. Stablecoins trade on distribution. Deposit tokens trade on trust in a specific bank and the usefulness of that bank’s rails.

The deeper point is that these products solve different coordination problems. Stablecoins solve the problem of programmable dollars without waiting for every bank to join the same system. Deposit tokens solve the problem of programmable bank money without asking banks to leave their core business model.

05What builders should do now

For product teams, the first question is not “Which is better?” It is “Which liability do I need?” If you need open circulation, multi-wallet reach, and integration with public crypto markets, public stablecoins remain the default. If you need bank-controlled issuance, tighter client qualification, and direct integration with a bank balance sheet, deposit tokens are the more natural fit.

For compliance teams, the operational questions are just as important. Who can mint and redeem? Who can be frozen out? What happens on a chain fork? What reserves back the token, and where do they sit? What supervision applies if the issuer is a bank versus a non-bank payment firm? JPMD and public stablecoins answer those questions differently, and the differences show up in incident response, sanctions policy, redemption gating, and audit expectations.

For investors, the investment case is similarly split. Stablecoins are a broad platform bet on public-chain money and the liquidity network around it. Deposit tokens are a bet on banks bringing their existing client franchises onto programmable rails. The winners may not be one or the other. The more likely outcome is a layered market in which banks issue controlled money for institutional workflows while public stablecoins continue to dominate open crypto liquidity.

Practical takeaway: if you want a dollar asset that behaves like a bank claim inside a permissioned institutional workflow, JPMD is the right model to study. If you want a dollar asset that can travel across the open internet and plug into the widest range of onchain applications, public stablecoins still have the edge. The important shift in 2026 is that both models are moving from theory into regulated production.