What Kills a New Stablecoin Isn’t a Depeg—It’s the Silent Death

If you work in payments, wallets, or exchanges—or someone on your team just pitched “let’s issue our own stablecoin”—don’t rush to deploy the contract. The contract is the cheapest part of this business. What actually kills you is the question nobody talks about, the one that surfaces after deployment: it’s live, and nobody uses it. Now what?

“Nobody uses it” isn’t a static state. It’s a knot that tightens on itself. The overwhelming majority of new stablecoins die in this knot—not in the technology.

The Framework: The Liquidity Chicken-and-Egg

Draw the knot, and it’s a closed loop where nobody will move first:

Users → need depth → need market makers → need volume → need users.

Without depth, users get scared off by slippage and don’t come; without users, market makers won’t lay down depth for you. Depth and users are each other’s precondition, so a new coin stalls at zero.

The entire essence of a cold start is using real money to force that loop open—to manufacture the “first chicken.” Whether you spend that money right, and whether you can afford it, decides if your coin survives its first year. It isn’t a marketing budget. It’s the entry deposit for this business.

You Have to Light Three Lamps at Once

Most people think issuing a stablecoin means deploying a contract and passing an audit. The real cold start is lighting three interdependent lamps simultaneously: credible redemption (people believe your 1:1), on-chain depth (it’s swappable, low slippage), and a real use case (someone genuinely needs it).

These three can’t be lit separately. Contract without depth is a bank with no cash in the vault; depth without a use case means the moment subsidies stop, your TVL evaporates the same day—the industry calls it “mercenary liquidity.”

I learned this the hard way, on the wrong side of a different track. Building the HPB public chain, we pushed signature verification to roughly 30,000 TPS and built our own hardware acceleration—the performance wasn’t bad. But once the performance was there, I discovered the chain had no applications, no developers, no assets. The performance became a perfectly straight highway with no cars on it. The hardest lesson wasn’t “we couldn’t build it”—it was “we built it and nobody came.” A stablecoin’s cold start and a chain’s ecosystem cold start are the same problem: you think the hard part is building, but the hard part is getting people to use it. I paid dearly for that lesson. I’m writing it here so you don’t have to.

How New Coins Die in Year One: Four Deaths

This section reads like an autopsy—causes and signals, not headlines.

Here’s the counterintuitive part: what kills new stablecoins is almost never a depeg. A depeg has a corpse, a headline, someone who remembers. Far more new coins die a “silent death”—no crash, just slowly fewer users, depth draining to zero, quietly delisted one day. Four typical deaths, all silent:

1. Mercenary-liquidity death. TVL looks great during the subsidy window, scatters the moment subsidies stop. The signal: the TVL curve tracks the incentive curve too closely.
2. Hollow-use-case death. There’s depth, but nobody needs it—the demand was all bought with subsidies.
3. Spread-too-thin-across-chains death. One limited pool of liquidity sliced across five or six chains, each shallow, soft everywhere, easy to topple everywhere.
4. Bridge-dependency death. You bridge the coin onto other chains; the bridge gets hacked, and every bridged version depegs at once.

Choosing a Chain Isn’t a Tech Decision—It’s a Distribution Decision

Most people think choosing a chain is about TPS and gas. Wrong. Choosing a chain is a distribution decision: behind each chain is a different crowd of users, a different set of wallet defaults, a different group of exchange integrations. Pick the wrong chain, and you’ve opened your shop on a street with no foot traffic.

The correct order is reversed: find your use case and channel first, then back into which chain to deploy on—not worship some chain’s peak performance and then go hunting for a use case. Performance is the entry ticket; the distribution behind the chain is what you’re actually after.

The bridge problem deserves its own line. A cross-chain bridge isn’t infrastructure—it’s a single point of failure on your balance sheet that you don’t control. Whether your coin holds 1:1 on another chain depends on a bridge you didn’t build and can’t manage. Issue natively across chains if you can; if you must use a bridge, manage it as a reserve risk exposure and disclose it.

Subsidies: Count Them as Customer Acquisition Cost, Not Charity

Subsidies aren’t the original sin; burning them wrong is. Ask every dollar of subsidy three questions: What is it buying—depth, users, or a use case? Will it stay when the subsidy stops—what’s the retention? Does its acquisition cost pencil against your future reserve spread?

Put cold-start subsidies next to the “channel tax” issuers pay distributors, and they’re the same thing: paying for distribution. The only difference is whether you’re renting liquidity that can leave any minute, or buying users who actually settle in.

Subsidies can buy depth, not trust; they can buy TVL, not habit.

The truth of a cold start: you’re not issuing a coin, you’re betting you can front the money to hatch “nobody uses it” into “people use it.” Hatch it wrong, and however good your tech, it’s just a highway with no cars—I built that highway myself, so I know how quiet it gets.

If you’re evaluating a project about to issue a new coin: before you admire how clean its contract is, ask how it plans to light those three lamps.

—— From The Stablecoin Operating Manual: Distribution, Reserves, and Compliance, Chapter 11

Sources (verified):

• Author’s firsthand account: HPB ~30,000 TPS, in-house hardware acceleration, software-hardware integrated chain (around 2018).
• GENIUS Act: Public Law 119-27, signed 2025-07-18; 1:1 reserves, monthly disclosure. https://www.govinfo.gov/content/pkg/PLAW-119publ27/pdf/PLAW-119publ27.pdf