CASH is a stablecoin that pays the platform, not the holder

CASH is Phantom’s “open-loop” USD stablecoin on Solana, issued by Bridge Building Inc (BBI).

The design intent is explicit. CASH is built to make stablecoin origination economically attractive to wallets, apps, and fintechs that can drive distribution. The pitch is that a “CASH Contributor” can integrate the coin and keep 100% of the net revenue generated from the supply it originates (after issuance fees).

That is the core tokenomics move. It shifts reserve economics away from a single issuer capturing the entire float yield, and toward a revenue-sharing model where distribution partners compete to originate supply. Mechanically, it is closer to “stablecoin as a B2B margin line” than “stablecoin as a consumer product.”

For a more holder-oriented contrast, see Frax USD tokenomics.

There is also a second-order positioning benefit. By making the coin “neutral and open,” CASH aims to avoid walled-garden distribution and drive onchain liquidity from day one, while Phantom acts as a large default surface.

As a Regulatory Pragmatist, I read that as a deliberate trade. CASH makes the economic “who gets the yield” question legible and contractual at the platform layer. It also concentrates the real regulatory risk in the offchain rails and in any yield pass-through that looks like interest, not in the token’s price behavior.

Issuance and supply: elastic mint/burn under Bridge

CASH launched on Solana on September 30, 2025, designed by Phantom using Bridge (Stripe-backed) “Open Issuance.”

Supply is demand-driven. CASH is minted when users or platforms convert USD (or supported crypto flows) into the stablecoin through Bridge-connected rails, and it is burned on redemption. Bridge’s terms describe Bridge Stablecoins as redeemable 1:1 for USD with BBI or its affiliates, subject to conditions and limitations in the stablecoin terms.

CoinGecko provides live supply data, including circulating and total supply (which changes as minting and redemptions happen).

Two practical implications follow from this issuance model.

First, “tokenomics” is not an emissions schedule problem. There is no staking inflation, no vesting schedule, and no fixed cap to model. The coin’s growth is constrained by compliance, distribution, and reserve operations, not by protocol-level scarcity.

Second, stability on secondary markets is downstream of redemption credibility. Bridge’s terms state redemptions will be processed within two business days after Bridge determines the order complies with the applicable user terms. That puts a concrete time boundary on the arbitrage loop that normally keeps a fiat-backed stablecoin tight.

There is no documented token allocation schedule for CASH in the way you would expect for a governance token. Distribution is primarily “minted into existence” when someone brings dollars (or equivalent value) into the system.

That differs from debt-backed designs like DOLA tokenomics.

Economic flows: reserves, rewards, and who actually captures them

The real token economy is the reserve balance sheet. BBI states it maintains a reserve of high-quality liquid assets whose aggregate market value (in USD terms) is at least equal to outstanding stablecoins, measured as of 5:00 pm New York time on each business day.

Reserve composition is constrained, not exotic. The CASH site describes reserve asset classes that include short-dated U.S. Treasury bills, overnight reverse repos collateralized by U.S. Treasuries, U.S. government money-market funds, deposit accounts, and tokenized versions of those assets.

Two legal-economic statements matter more than the asset list.

Reserve yield belongs to the issuer unless contractually shared. Bridge’s stablecoin terms say BBI is entitled to all net returns earned on reserve assets, to the extent not required to maintain the reserve at the required minimum value.

Token holders do not have a property interest in the reserve. The same terms make clear Bridge Stablecoins do not convey a direct or indirect property interest in, or right to withdraw, reserve assets.

This is where CASH’s “revenue sharing” positioning becomes structurally important. CASH is marketed as letting businesses keep 100% of net revenue from the supply they originate, instead of the issuer keeping the entire float yield.

Bridge documents the core reward mechanics: rewards accrue based on the treasury allocation and are paid out at the end of each month, either minted as new tokens to a specified wallet or converted to fiat and deposited to a bank account.

That “minted as new tokens” detail is easy to miss. For a stablecoin, minting “rewards tokens” to a partner is economically equivalent to paying them yield sourced from the reserve portfolio, because the issuer’s balance sheet expands as reserves expand. It is clean from an accounting perspective. It is also where regulatory classification starts to bite.

If rewards stay at the platform level as B2B revenue, the compliance story is relatively straightforward. It looks like fee income or rebate economics paid to an integrator, not “interest paid to the public.” If rewards are passed through to end users as an “earn rate,” Bridge explicitly contemplates that as an option for issuers and calls out user-facing experiences like “Earn 3% on your balance.”

That is the tension. A stablecoin can be “not designed to generate returns” for users under the stablecoin terms, while the surrounding product can still pay incentives. The legal risk is not theoretical. Yield-like marketing tends to pull a product toward securities, banking, and consumer finance regimes depending on distribution, disclosures, and who bears the investment risk.

Utility surfaces: Phantom Cash, offchain rails, and DeFi composability

Onchain, CASH is a Solana stablecoin used for transfers, swaps, and DeFi. The Phantom Cash wrapper positions it as the foundation for “money movement features” inside Phantom, including P2P, funding, and card-based spending.

Phantom Cash is the main product wrapper. Phantom describes a “Cash account” as a self-custodial wallet on Solana tied to a Phantom username, which holds CASH and displays the balance in USD.

Phantom distinguishes between:

Onchain features available worldwide, like swapping Solana tokens into CASH and receiving CASH transfers.

Offchain features that are US-only (with New York excluded in Phantom’s documentation), like bank funding, ACH withdrawals, routing/account numbers, and the debit card.

The debit card mechanics are simple and important for token velocity. Phantom states that when you pay with the Phantom Cash debit card, Bridge draws CASH from your Cash account balance and converts it to USD so the merchant is paid like a standard Visa transaction.

From a token economy standpoint, that is a recurring onchain-to-offchain “burn-and-settle” style flow, even if the exact burn happens in Bridge’s internal accounting rather than an onchain burn instruction visible to everyone. It increases transaction frequency and, if the product scales, increases outstanding supply through higher working balances.

For DeFi, Phantom explicitly points users to earning yield by depositing CASH into apps like Kamino. Phantom’s support docs emphasize these products are not part of Phantom and require SOL for network fees.

This separation is compliance-aware. It keeps Phantom from implying that “holding CASH” itself generates yield, while still enabling DeFi composability for users who want onchain returns.

Governance and parameter control: centralized, contractual, and API-driven

CASH does not present as a governance token. There is no onchain voting system in the primary documentation. Control lives with Bridge as issuer-operator and with Phantom as the dominant distribution surface.

Bridge’s stablecoin terms grant Bridge broad discretion over operational support and risk controls. Bridge can suspend access or support for stablecoins under various triggers, including compliance, security incidents, or reputational risk.

Bridge also states it may freeze stablecoins by blacklisting addresses and can burn stablecoins held in a particular wallet and mint new stablecoins into a different wallet if required by law or internal compliance policies.

On the product side, Bridge’s Open Issuance platform is explicitly built for customizable parameters. Bridge’s documentation describes reserve allocation controls (cash versus treasuries) and notes that cash reserves do not generally generate rewards, while treasuries maximize rewards but settle in about one business day for redemption.

That is “governance,” just not community governance. It is issuer governance via API, contract, and compliance policy.

Regulatory posture is part of the token design. CASH’s site states Bridge operates its issuance and orchestration programs as a FinCEN-registered money services business with money-transmission licenses and other state authorizations where required, and describes separate arrangements for EEA and other non-US flows.

This matters for tokenomics because it defines who can access primary minting and redemption rails, under what identity requirements, and in which jurisdictions. Those constraints are often more binding than any smart contract parameter.

Risk analysis: CASH’s tokenomics are a regulatory product

CASH’s strengths come from its clarity. It is fully collateralized (by stated reserve policies), it has defined redemption mechanics, and it squarely answers the “who gets the float yield” question by pushing economics to originators.

Its weaknesses come from the same place. When you build stablecoin economics as revenue share, you invite scrutiny around inducements, interest, distribution payments, and the boundary between “payment instrument” and “investment product.” You also accept centralized controls like blacklisting as a condition of operating at scale.

We track adjacent patterns in our research reports.

Top 3 risks

  1. Compliance intervention and address-level loss. Trigger: sanctions action, fraud flags, law enforcement requests, or internal compliance escalation. Mechanism: Bridge may blacklist addresses, freeze transfers, and may burn tokens in a wallet (with no obligation to re-mint) under its stablecoin terms. Who bears it: end users, DeFi protocols holding CASH, and integrators with balances in affected addresses. Measurable indicators: increase in frozen/blacklisted addresses, elevated compliance-related support incidents, and onchain patterns consistent with funds being routed away from “tainted” clusters.

  2. Offchain rail concentration and operational gating. Trigger: partner downtime (banking, card programs), KYC vendor issues, or jurisdictional changes that reduce feature availability. Mechanism: Phantom Cash’s offchain features depend on Stripe for KYC and funding and on Bridge for deposits, withdrawals, and card settlement, with regional restrictions (including NY exclusions in Phantom docs). Who bears it: users relying on ACH, card spend, or direct deposit, plus merchants and payroll-like flows that assume “always available” settlement. Measurable indicators: increased waitlists, higher failed deposit/withdrawal rates, and more frequent feature suspensions by region.

  3. Secondary-market depeg and liquidity stress during redemption frictions. Trigger: fast sell pressure, chain instability, or narratives that call reserves or redemption access into question. Mechanism: while redemption at par is the anchor, Bridge’s terms describe a processing window of up to two business days after compliance determination, and Bridge disclaims control over third-party market pricing. Who bears it: DEX LPs, leveraged DeFi users, and anyone forced to exit onchain rather than redeem through primary rails. Measurable indicators: widening CASH/USDC spreads, elevated DEX outflows, and sustained deviation from $1 on major Solana venues.

Dominant risk: compliance-driven control is not a tail risk for CASH. It is a design requirement.

Bridge’s stablecoin terms reserve the right to freeze by blacklisting and, more aggressively, to burn tokens in a wallet and mint new tokens elsewhere if required by law or internal compliance policies, with explicit language that the user may lose the entirety of their stablecoins and Bridge is not liable for resulting losses.

For a payments-oriented stablecoin, that may be non-negotiable. The moment you connect stablecoin balances to ACH, card spend, and merchant acceptance, you inherit the compliance expectations of the banking and card ecosystems. Phantom’s own documentation reinforces that the debit card and bank features require KYC, and that partners handle identity verification and payments operations.

The problem is composability. DeFi assumes bearer assets. When a stablecoin can be frozen or burned under offchain policy triggers, every DeFi integration inherits a silent “compliance oracle” dependency. You can’t diversify that risk away inside a single asset. If CASH becomes a major settlement unit on Solana, the systemic question becomes simple: how much of Solana DeFi’s dollar liquidity is comfortable sitting behind a policy-controlled switch.

CASH’s revenue-sharing tokenomics makes this even sharper. By paying originators, you incentivize distribution. Distribution growth increases the surface area for illicit flow attempts. That increases the likelihood of enforcement actions and false positives. It also increases the value of having aggressive monitoring and intervention. In other words, the very mechanism that drives growth also drives the operational need for discretionary controls.

This is not an argument against CASH. It is the correct framing for users and integrators. If you treat CASH like a censorship-resistant onchain dollar, you will misprice the risk. If you treat it like a regulated payments stablecoin with onchain settlement and offchain enforceability, the design is coherent.

For another centralized, payments-facing comparison point, see Cap USD tokenomics.

One final note on regulatory edges. Bridge’s Open Issuance docs describe rewards as belonging to the developer (minus issuance fees), and they explicitly allow the developer to keep rewards as revenue or use them to incentivize users, with automated reward splitting described as “coming soon.”

If a major distributor chooses to market user yield directly on CASH balances, that is where classification risk spikes. Interest-like marketing tends to trigger securities analysis, consumer disclosure requirements, and potential banking-like supervision depending on jurisdiction and implementation. The safest path is the one CASH seems to be taking today: keep CASH itself as a plain payment stablecoin, and let yield live in clearly separated DeFi venues.

If you’re integrating CASH and need a second set of eyes on design components like incentive design, reserve-driven rewards pass-through, or how to describe the economics without drifting into “yield token” territory, that’s where tokenomics consulting and token design services work stops being cosmetic and starts being risk management. Keep the incentives, disclosures, and control surfaces consistent with the actual legal plumbing.



This article is part of our Tokenomics Deep Dive series.