Welcome to USD1cap.com

USD1cap.com is an educational page about USD1 stablecoins. On this site, the phrase USD1 stablecoins is used in a purely descriptive way: any digital token intended to be stably redeemable one-to-one for U.S. dollars. Nothing here is a brand claim, an endorsement, or an assurance that any particular token will hold its value.

In many real-world designs, USD1 stablecoins are created and redeemed by an issuer (the entity that creates and redeems the token). In other designs, creation and redemption may be mediated by smart contracts (software on a blockchain, meaning a shared ledger of transactions maintained by many computers, that runs automatically) or intermediaries, but the same questions about limits and risk still apply.

The topic of this page is cap, a short word that shows up in stablecoin conversations in two very different ways:

A cap (a maximum allowed amount) can be a rule that limits how much of something is permitted.
A market cap (short for market capitalization, meaning price multiplied by circulating supply) is a measurement people use to describe the size of a token.

Because these sound similar, it is easy to mix them up. The rest of this page separates the two ideas and explains how each one can matter for USD1 stablecoins.

What a cap means on this site

In everyday English, a cap is a ceiling. In finance, caps are used as guardrails. When you see a cap in connection with USD1 stablecoins, it usually points to one of these goals:

Safety (reducing the chance of losses for holders).
Stability (supporting the one-to-one redemption goal).
Liquidity (the ability to buy or sell without moving the price too much).
Compliance (meeting legal and regulatory duties such as identity checks).
Operational resilience (avoiding outages or bottlenecks during heavy use).

It is also useful to distinguish between a cap that is a measurement and a cap that is a rule:

Market cap is descriptive. It tells you how big the token looks right now based on supply and price.
A limit cap is prescriptive. It tells you what is allowed, what will be blocked, or what may need additional steps.

In practice, a single project or platform may use several caps at the same time. For example, there might be an overall issuance cap, a daily creation cap, a per-user holding cap, and a separate cap inside a lending protocol. The right question is not "Do caps exist?" but "Which caps exist, where do they apply, and why?"

Market cap for USD1 stablecoins

Market capitalization (often shortened to market cap) is usually computed as:

Market capitalization = token price times circulating supply (circulating supply means the number of tokens currently held by users, not locked or burned).

For USD1 stablecoins, the token price is intended to stay near one U.S. dollar because holders expect to redeem at par (par value means one token can be redeemed for one U.S. dollar). When the price stays close to one, market capitalization is often close to "how many tokens exist," expressed in dollars.

That sounds simple, but there are several key caveats.

Market cap does not prove backing

A common misunderstanding is that a larger market cap automatically means stronger backing. Market cap is an external measurement, while backing relates to reserve assets (the cash and cash-like assets held to support redemption). Market cap can rise because more tokens were created, but the quality, liquidity, and legal structure of reserve assets still matter.

International standard setters have emphasized that stablecoins can create financial stability risks if the stabilizing mechanism (the mix of rules, reserves, and operations intended to keep redemption near one-to-one) and reserves are not robust, especially at scale.^[1] In other words, "big" is not the same as "safe."

Market cap is sensitive to how supply is measured

Supply sounds like a single number, but it can become messy when tokens exist on multiple blockchains. A token can be issued on one network and "bridged" (moved across chains via a bridge, meaning a system that locks tokens on one chain and releases a representation on another). If data providers count both the locked tokens and the representation tokens, market cap can be overstated. If they miss a chain or a wrapper, market cap can be understated.

This is one reason why serious analysis often cross-checks several data sources and compares on-chain (recorded on a blockchain) totals with issuer reporting, when available.

Market cap is a snapshot, not a stress test

Market cap is typically measured at a point in time. It does not tell you what happens during a run (a rapid, large wave of redemptions). During stress, the key questions shift toward:

How quickly redemptions can be processed.
Whether reserve assets can be sold without heavy losses.
Whether there are legal or operational gates.
Whether market liquidity can absorb large selling pressure.

Research and policy work on stablecoins often focuses on these stress dynamics rather than the headline market cap number.^[2]

Market cap can be compared, but comparisons can mislead

Comparing market caps across USD1 stablecoins can be useful for understanding relative adoption. However, two tokens with the same market cap can have very different risk profiles because of differences in:

Reserve composition (what assets back the token).
Custody (who holds the reserve assets and under what legal arrangement).
Redemption terms (who can redeem, how fast, and what fees apply).
Transparency (attestations or audits, discussed below).

The IMF has noted that stablecoins vary widely in structure and risk, and that the regulatory approach is still evolving across jurisdictions.^[3] So market cap is a starting point for describing "scale," not a full safety assessment.

Supply caps, minting limits, and redemption limits

When people talk about a cap as a rule, they often mean a limit on how many tokens can exist, how fast tokens can be created, or how much can be redeemed in a given time window.

Supply cap

A supply cap (a maximum number of tokens allowed to exist) can be hard or soft:

A hard supply cap means the system is designed so it cannot exceed a specific maximum.
A soft supply cap means the system aims to stay below a target, but governance (the decision-making process for updates) can adjust the cap.

In USD1 stablecoins, supply caps are less common than in fixed-supply cryptoassets (digital assets recorded on a blockchain) because a redeemable token is often expected to expand and contract with demand. Still, caps may appear for practical reasons, such as limiting exposure during early stages or controlling risk while systems are tested.

Minting limit

Minting (creating new tokens) can be capped even when there is no lifetime supply cap. A minting cap can be:

Per day (a daily maximum new issuance).
Per account (a per-user maximum, often linked to compliance).
Per channel (a cap per on-ramp, meaning a method used to bring U.S. dollars into the token system).

Minting caps can be about liquidity management. If an issuer relies on bank transfers, there can be cut-off times, banking limits, and settlement delays. A minting cap can prevent a situation where more tokens are created than the issuer can safely settle into reserves on the same day.

Minting caps can also be about risk. If reserves are invested in instruments that take time to convert into cash, rapid issuance growth can raise maturity mismatch risk (a mismatch between when assets can be sold and when redemptions must be paid).

Redemption limit

Redemption (exchanging tokens for U.S. dollars) can also be capped. Redemption caps are often controversial because the redemption promise is central to stablecoin design, but caps may exist as:

Operational limits, such as banking hours, payment rail throughput, or fraud controls.
Compliance limits, such as sanctions screening (checking parties against sanctions lists) and KYC (know your customer identity checks).
Liquidity limits, such as internal risk controls that prevent forced selling of reserves during abnormal conditions.

From a user perspective, the key point is that a redemption cap can make a token behave differently in stress than it does in calm conditions. A token that is easy to redeem in small amounts might still have frictions when many holders seek cash at once.

The FSB's recommendations emphasize the need for effective governance, risk management, and clear redemption rights for stablecoin arrangements, particularly when they could become systemic (meaning large enough to affect the wider financial system).^[1]

Holding caps and transaction caps

A different class of caps does not focus on issuance. Instead, it limits how much people can hold or how much can be transacted in a period. These are often discussed in public policy because they can be used to manage systemic risk during a transition period.

Holding cap

A holding cap (a limit on how much a person or business can hold) is sometimes proposed to reduce bank disintermediation (shifts of funds out of bank deposits into other forms of money) during stress. The argument is that if households and firms could move large sums into a privately issued digital money instrument very quickly, banks might lose deposit funding, which could reduce credit availability.

The Bank of England has published analysis on holding limits for sterling-denominated systemic stablecoins and a potential digital pound, describing holding limits as a possible transitional safeguard for financial stability.^[4] This is an example of a policy-driven cap: it is less about the issuer's operations and more about the wider monetary system.

Holding caps are not universally adopted, and they have clear trade-offs:

A lower cap can reduce systemic risk but also reduces usability (how practical the token is for everyday use).
A higher cap supports usability but may increase the potential for rapid deposit outflows from banks during stress.

Even if a holding cap is not present at the stablecoin layer, it can appear at a service layer, such as within a wallet provider or a payment platform.

Transaction cap

A transaction cap (a limit on the number or value of transactions) can be designed to slow down rapid growth, reduce fraud, or reduce systemic spillovers. Some regulatory frameworks include explicit thresholds related to transaction activity.

For example, the European Union's Markets in Crypto-Assets Regulation (MiCA) includes a usage threshold for certain asset-referenced tokens (MiCA's term for a token designed to keep a stable value by referencing assets) used as a means of exchange (used for everyday payments). If daily transaction activity as a means of exchange exceeds the threshold within a single currency area, the issuer must stop issuing more of the token until it has a plan to bring activity below the threshold. One threshold stated in the regulation is more than 1,000,000 transactions and more than EUR 200,000,000 per day.^[5]

This shows a key point about "caps" in regulation: sometimes they are framed as triggers. Crossing the trigger changes what the issuer must do, what supervisors can demand, or whether issuance can continue.

Platform and DeFi caps

Caps are not only set by issuers or regulators. They are also used by platforms that integrate USD1 stablecoins, including trading venues, payment services, and decentralized finance systems.

Exchange and wallet caps

A centralized exchange (a trading venue operated by a company) or a wallet provider (a service that holds private keys or provides payment features) may set caps such as:

Deposit and withdrawal caps (limits on how much can enter or leave per day).
Transfer caps (limits designed to reduce fraud or comply with local rules).
Conversion caps (limits on swapping USD1 stablecoins into other assets through the platform).

These caps are often operational and compliance driven, but the user experience effect is real: a cap at the service layer can feel like a cap on the token itself, even when the underlying token contract has no such rule.

DeFi caps as risk controls

Decentralized finance or DeFi (financial activity carried out through smart contracts) often uses caps as a risk management tool. The reason is straightforward: DeFi protocols frequently take collateral, lend assets, and rely on liquidation (automatic selling of collateral when it falls below the minimum levels). If too much of one asset enters the system, a sudden shock can threaten solvency.

Common DeFi caps include:

Supply caps (limits on how much of an asset can be supplied to a lending pool).
Borrow caps (limits on how much can be borrowed against collateral).
Debt ceilings (limits on how much protocol debt can be issued, often used in overcollateralized stablecoin systems).

These caps are not about a redemption promise. They are about protecting the protocol against oracle failure (bad price data from an oracle, meaning a mechanism that brings external data on-chain), liquidity shocks, and correlated liquidations.

IOSCO has highlighted that stablecoins are frequently used in DeFi and can be critical to how DeFi operates, which means weaknesses in stablecoin arrangements can transmit into DeFi and vice versa.^[6] Caps are one way DeFi attempts to reduce that transmission, although they are not foolproof.

Bridge caps and cross-chain limits

A bridge often implements a cap on how much value can be moved in a time window. This is a response to bridge risk: bridges have been frequent targets of exploits (attacks that steal funds by abusing software flaws). A cap can limit loss if a vulnerability is exploited, but it also can create bottlenecks.

For USD1 stablecoins, a bridge cap can affect the "effective supply" on a chain, even if global supply stays unchanged. In periods of stress or high demand, that can create price differences between chains, which complicates market cap measurement and user expectations.

How caps are measured across chains

Measurement matters because market cap and many cap-like policies depend on accurate totals.

On-chain totals and circulating supply

On a single chain, circulating supply is often inferred from the token contract (the smart contract that records token balances and supply) total supply minus known burned balances (burned means intentionally removed from circulation). For multi-chain tokens, measurement may involve combining totals from each chain and adjusting for bridges and wrappers.

A practical way to think about this is: supply is easy to count when there is a single ledger, but it becomes a reconciliation problem when there are multiple ledgers and representations.

Attestations and audits

When an issuer publishes reserve reports, you may see terms like:

Attestation (an accountant's report that certain information is fairly stated at a point in time, based on agreed procedures).
Audit (a broader examination of financial statements under an auditing standard).

These reports can help assess whether reserve assets appear consistent with tokens outstanding, but they do not remove all risk. The quality of the report depends on the scope, the timing, the legal structure of reserves, and the ability to verify assets held with custodians (a firm that holds assets for others).

The IMF's work on stablecoins emphasizes that arrangements differ widely, and that transparency and governance are central to understanding risk.^[3]

Market cap and transaction activity in regulation

Some regulatory approaches look beyond market cap and focus on usage. MiCA is a clear example, using transaction activity thresholds for certain tokens used as a means of exchange within a currency area.^[5] This matters for the "cap" topic because the cap-like concept is not always "how many tokens exist" but "how intensively they are used."

Similarly, public authorities and standard-setting bodies have emphasized the role of oversight, risk management, and operational resilience for stablecoin arrangements, particularly where they could become widely used for payments.^[1]

Common misconceptions and risk trade-offs

Caps are often presented as simple safety features. In reality, they are trade-offs.

Misconception: A higher market cap means fewer risks

A higher market cap can indicate that a token is widely used. It can also mean the consequences of failure are larger. Many policy documents treat scale as a reason for stronger oversight, not as a badge of safety.^[1]

Misconception: Caps always protect holders

A cap can protect holders in one scenario while harming them in another. For example:

A bridge cap can limit losses from an exploit but can also trap liquidity on one chain.
A redemption cap can slow a run but can also intensify panic if holders fear they will be last in line.
A holding cap can reduce systemic risk but can also push activity into less supervised channels.

The effectiveness of a cap depends on design details, communication, and how people behave under stress.

Misconception: A supply cap is the same as a reserve limit

A supply cap limits token issuance. A reserve limit concerns what assets can be held, how liquid they are, and whether they are legally segregated (held separately so they are not mixed with other assets). They address different risks.

Trade-off: Usability versus stability safeguards

Caps often reduce usability. This is especially clear with holding limits and transaction thresholds in policy discussions, where the goal is to allow innovation while avoiding destabilizing shifts in the monetary system.

The Bank of England's analysis frames holding limits as a transitional tool: a way to learn about risks while limiting the scale of potential stress impacts.^[4] Whether that approach is appropriate depends on local banking structure, payment habits, and supervisory goals.

Trade-off: Speed versus control

Fast issuance and fast redemption are attractive features for USD1 stablecoins used in payments and settlement. Yet speed can conflict with control measures like sanctions screening, fraud checks, and liquidity risk management. Caps, queues, and cut-offs are often the operational compromise.

The Committee on Payments and Market Infrastructures has discussed considerations for stablecoin arrangements in cross-border payments and emphasized the need to manage credit and liquidity risk when stablecoins are used for payment and settlement.^[7]

Trade-off: Innovation versus consistency

Different jurisdictions may impose different caps or cap-like triggers, which can fragment the global use of USD1 stablecoins. The FSB has aimed for consistent high-level recommendations across jurisdictions while allowing local implementation flexibility.^[1] In practice, this can still lead to a patchwork of rules that affects how stablecoins scale.

FAQ

Is market cap the same as how many U.S. dollars are in reserve?

Not necessarily. Market cap is price times circulating supply. Reserves are the assets held to support redemption. In calm markets, market cap and reserves might look similar in size for a fully reserved token (meaning it is intended to be backed by reserve assets with a value that matches tokens outstanding), but they can differ due to timing, valuation, fees, or reporting scope.

If USD1 stablecoins are redeemable one-to-one, why can the price move at all?

Because many people trade USD1 stablecoins on secondary markets (markets where people trade with each other rather than redeeming directly with an issuer). Short-term imbalances in supply and demand, limited liquidity, and stress concerns can push prices slightly above or below one U.S. dollar even if redemption exists.

What is the difference between a cap and a trigger?

A cap is a hard ceiling. A trigger is a threshold that changes rules once crossed. In stablecoin regulation, triggers can function like caps by making an issuer stop issuing or take remedial steps once usage exceeds a certain level.^[5]

Can a DeFi supply cap change?

Yes. Many DeFi protocols use governance (a voting or administrator process) to adjust caps as liquidity and risk conditions change. That flexibility can be useful, but it also means the cap is only as reliable as the protocol's governance and security.

Do caps prevent a run?

Caps can slow down a run, but they do not remove the underlying reasons for a run, such as doubts about reserves, legal uncertainty, or operational failure. In some cases, tight caps can increase fear if users believe access will be restricted.

Why would a regulator care about holding caps?

Because very rapid movement of funds from bank deposits into other forms of money could affect bank funding and credit creation. Some central banks have analyzed holding limits as a way to reduce these risks during transition periods.^[4]

Are all caps visible on-chain?

No. Smart contract caps can be visible on-chain, but service-layer caps, banking limits, and policy constraints may not be visible in token data. Understanding caps often involves reading platform terms and regulatory disclosures.