Stablecoin Risk Checklist: 15 Checks, 6 Limits, and a Depeg Playbook

Stablecoins reduce one obvious source of volatility: the price movement of the unit they are designed to track. They do not remove issuer risk, reserve risk, redemption friction, exchange failure, smart-contract controls, chain outages, bridge failures, or crowded exits.

That is why a useful stablecoin risk checklist must answer two different questions:

1. Is this stablecoin structure credible enough to hold?
2. How much exposure can the portfolio tolerate if one dependency fails?

This updated framework provides 15 due-diligence checks, a 30-point scorecard, a five-bucket allocation plan, six hard exposure limits, and a staged depeg response playbook. It is designed for investors and crypto treasury users who treat stablecoins as operational capital, dry powder, collateral, or on-chain working capital—not as automatically risk-free cash.

Important: This article is educational and is not financial, legal, or tax advice. Stablecoin rules, issuer terms, reserve assets, redemption eligibility, and platform access vary by jurisdiction and can change.

What a stablecoin risk checklist should measure

A stablecoin position is a chain of claims and operating dependencies. The token may remain near its target price while another link in that chain weakens.

Separate the exposure into five layers:

Use this stablecoin risk checklist as a documented evidence review. The checklist scores each item from 0 to 2:

• 0 — Unverified or unacceptable: material information is missing, contradictory, inaccessible, or outside policy.
• 1 — Partially acceptable: the evidence exists, but an important limit, dependency, or uncertainty remains.
• 2 — Verified and acceptable: the evidence is current, relevant to your account and jurisdiction, and within written limits.

The maximum score is 30. A high total does not override a zero on a critical item. Weak redemption access, unclear reserves, or an untested exit can be a veto even when the aggregate stablecoin risk checklist score looks comfortable.

The 15-point stablecoin risk checklist

1. Define the job of the stablecoin position

Start with purpose before product. A token used for same-day settlement has a different risk budget from a six-month reserve or a DeFi strategy.

Write down:

• the amount and percentage of the crypto portfolio;
• the expected holding period;
• the required exit speed;
• the intended venue and chain;
• whether principal stability or yield is the priority;
• the maximum tolerable loss, delay, or temporary lockup.

Score 2 only if: the position has a specific job, time horizon, liquidity requirement, and loss limit.

2. Identify the legal issuer and the holder's claim

Do not stop at the ticker. Identify the issuing legal entity, governing jurisdiction, contractual terms, and who actually owes the redemption obligation.

Ask whether you hold a direct claim on the issuer, a claim through an exchange or custodian, a bridged representation, or a wrapper issued by another protocol. Each layer can change creditor status and recovery rights.

Score 2 only if: the issuer, contract, jurisdiction, and your place in the claim structure are clear.

3. Map the reserve assets

“Backed by reserves” is not enough. Record the reserve composition, duration, liquidity, credit quality, currency, custodian, and any permitted lending, pledging, or reuse.

Cash and short-term government obligations have different behavior from corporate debt, secured loans, commodities, crypto collateral, or algorithmic stabilization mechanisms. The question is not whether an asset sounds safe in normal conditions. The question is whether it can support redemptions during stress without forced-sale losses or delays.

Score 2 only if: the reserve assets are transparent, liquid enough for the liability, and compatible with your policy.

4. Grade the quality of reserve reporting

An attestation, audit, assurance engagement, dashboard, and issuer statement are not interchangeable.

Check:

• who prepared or verified the report;
• the reporting date and publication lag;
• whether assets and liabilities are both covered;
• whether the scope includes all issuing entities;
• whether exceptions, qualifications, or related-party exposures appear;
• whether the report shows only a point-in-time snapshot.

Score 2 only if: independent, current reporting covers the relevant issuer and provides enough detail to evaluate backing.

5. Verify direct redemption eligibility

A stablecoin may advertise one-to-one redemption while retail holders cannot redeem directly. Minimum sizes, onboarding rules, geography, account type, banking access, fees, and processing windows can all matter.

If you rely on an exchange rather than direct issuer redemption, your exit depends on that venue's liquidity and solvency. Document both the direct route and the route available to your actual account.

Score 2 only if: you know who can redeem, the minimum size, expected timing, fees, and settlement rail.

6. Measure secondary-market liquidity

The quoted price alone does not show how much capital can exit near par.

Track the specific pairs and venues you would use:

• bid-ask spread;
• order-book depth around the peg;
• estimated slippage for your position size;
• spot volume concentration by venue;
• fiat and stablecoin quote-pair availability;
• withdrawal status on the intended network.

Run the test during calm markets and again during a volatility event. Reported volume is not a substitute for executable depth.

Score 2 only if: your planned exit size can be sold or redeemed within the required time and slippage budget.

7. Review peg behavior as a stress signal

A stablecoin can briefly deviate from its target because of market plumbing rather than reserve impairment. The duration, venue distribution, and recovery mechanism matter more than one screenshot.

Review historical deviations across multiple venues. Record the largest gap, time to recovery, whether redemptions remained open, and whether the event was isolated to one chain or exchange.

Score 2 only if: past deviations were explainable, bounded, and resolved through functioning liquidity or redemption mechanisms.

8. Separate issuer risk from custody risk

A well-backed token can still be lost through an exchange, custodian, wallet, or account-control failure.

Document where the token is held, whether assets are segregated, the withdrawal policy, account recovery, key management, jurisdiction, and the legal treatment of customer property. Use the same rigor you would apply in a crypto exchange due-diligence review.

Score 2 only if: custody, ownership, withdrawal control, and failure treatment are documented and acceptable.

9. Inspect smart-contract and administrative controls

Many stablecoin contracts include roles that can freeze addresses, pause transfers, mint or burn tokens, denylist accounts, or upgrade logic. These controls may support compliance and incident response, but they also create governance and key-management dependencies.

Identify the administrators, signer structure, upgrade process, emergency powers, security audits, and incident history for the exact contract on the exact chain.

Score 2 only if: the controls and governance model are public, secured, and compatible with your use case.

10. Treat each chain and bridge as a separate exposure

The same ticker on two networks may not represent the same technical or legal claim. One version may be issuer-native; another may be bridged, wrapped, or exchange-issued.

Verify the contract address, issuer support, bridge model, validator or multisig design, finality assumptions, congestion history, and the route back to a directly redeemable asset.

Score 2 only if: the token is authentic on the intended chain and every bridge or wrapper dependency is understood.

11. Confirm the current regulatory category and permissions

Regulation can improve minimum standards without eliminating market, custody, operational, or counterparty risk.

In the United States, the GENIUS Act became law on July 18, 2025. In the European Union, the Markets in Crypto-Assets framework includes rules for asset-referenced tokens and e-money tokens. The relevant question is not simply whether “stablecoins are regulated.” It is whether this issuer, product, holder, venue, and activity are permitted under the rules that apply to you.

Check regulator status, licenses or registrations, disclosures, marketing restrictions, reserve requirements, redemption rights, and any transition dates. Recheck before a large allocation.

Score 2 only if: the legal status and required permissions are current and relevant to your jurisdiction and activity.

12. Map correlated concentration

Owning several stablecoin tickers does not create meaningful diversification if they depend on the same exchange, bank, custodian, chain, bridge, liquidity pool, or yield platform.

Create a dependency matrix:

Positions A and B have different issuers but share three important failure paths. Concentration should be capped by dependency, not just ticker.

Score 2 only if: written limits cover issuer, custody or banking rail, venue, chain, bridge, and wrapper concentration.

13. Score yield-bearing products separately

Once a stablecoin earns yield, the exposure may include borrower credit, leverage, liquidity mismatch, smart-contract risk, tokenized claims, or rehypothecation.

Ask where the yield comes from, who owes repayment, what collateral supports it, whether withdrawals can be gated, where you rank in a failure, and whether you still own the original stablecoin. A lending receipt, exchange balance, liquidity-pool token, and tokenized fund share should not be scored as plain stablecoin cash.

Score 2 only if: the yield source and every added risk layer are transparent, liquid, and separately capped.

14. Read insurance and safeguarding claims literally

Reserve cash held at a bank does not automatically make the stablecoin holder an insured bank depositor. The FDIC states that deposit insurance does not protect crypto assets.

Evaluate the exact legal wording behind “insured,” “safeguarded,” “segregated,” and “bankruptcy remote.” Determine what event is covered, who is the beneficiary, the coverage limit, exclusions, and whether records satisfy any pass-through requirements.

Score 2 only if: the protection applies to your claim and the specific failure scenario—not merely to an intermediary's reserve account.

15. Run a live exit drill and set monitoring triggers

An untested redemption plan is a hypothesis.

Before increasing the position:

1. Send a small amount to the intended wallet or venue.
2. Withdraw through the intended chain.
3. Sell or redeem a small amount.
4. Confirm the fiat or replacement-asset settlement route.
5. Record time, fees, limits, support requirements, and failure points.

Set explicit review triggers for peg deviation, reserve-report delay, issuer or custodian changes, redemption restrictions, venue withdrawal limits, contract upgrades, security incidents, regulatory action, or unexplained supply growth.

Score 2 only if: the exit works and the position has written monitoring, reduction, and escalation rules.

Turn the stablecoin risk checklist into a 30-point decision rule

Use the stablecoin risk checklist score to structure discussion, not to manufacture certainty.

Add three veto rules:

• No allocation when issuer identity or reserve structure cannot be verified.
• No cash-equivalent label when direct or secondary exit access is untested.
• No aggregation with plain stablecoins when yield, bridge, wrapper, or platform risk has been added.

Build a five-bucket plan from the stablecoin risk checklist

Do not begin with a universal percentage. Begin with the jobs that stablecoins perform in your portfolio.

For each bucket, set six limits. The first four cap balance-sheet concentration. The last two test whether the position can actually leave through the available routes.

bucket cap = maximum portfolio percentage assigned to the job
issuer cap = maximum exposure to one legal issuer
venue cap = maximum amount held with one exchange or custodian
implementation cap = maximum exposure to one chain, bridge, wrapper, or protocol
route-capacity cap = amount that can exit within the required time and slippage budget
loss-budget cap = amount consistent with the portfolio's maximum tolerated stablecoin loss

The effective position limit is the smallest applicable cap.

effective stablecoin limit = min(
  bucket cap,
  issuer cap,
  venue cap,
  implementation cap,
  route-capacity cap,
  loss-budget cap
)

This prevents a large “safe” bucket from bypassing a tighter counterparty, chain, exit-capacity, or portfolio-loss limit.

Calculate route capacity before sizing the position

A stablecoin balance may look liquid because daily trading volume is large. Portfolio liquidity is more specific: it depends on the venues you can access, the pairs you can trade, your verified account limits, the chain you hold, and the amount you can move without breaking the slippage budget.

Estimate three numbers for every material position:

Use the most conservative capacity that matches the bucket's required exit time.

route-capacity ratio = tested exit capacity / position size

A ratio below 1 means the planned position is larger than the proven exit route. That does not automatically make the position unacceptable, but it means the excess should not be described as same-day liquidity.

Run the test with executable quotes or small live transactions, not homepage volume figures. A venue's total volume can include unrelated pairs, inaccessible jurisdictions, wash activity, or liquidity that disappears when the peg is under pressure. The crypto exchange due diligence checklist provides a complementary method for testing spread, depth, custody, and withdrawals.

A worked allocation example

Assume a crypto portfolio creates a stablecoin sleeve of 20 units out of 100. This is an illustration of the method, not a recommended allocation.

Now stress the design:

1. Issuer freeze: Can the portfolio still meet near-term obligations?
2. Venue halt: Is enough capital accessible outside the primary exchange?
3. Chain outage: Is an alternate native rail already tested?
4. Peg break: What portion can exit without exceeding the slippage budget?
5. Banking disruption: Can proceeds settle through another permitted route?

If one scenario disables several buckets at once, the allocation is less diversified than the ticker count suggests.

For portfolio-wide sizing and rebalancing rules, pair this checklist with the crypto portfolio risk budget framework.

Use a staged depeg response playbook

Do not invent the plan while spreads are widening. Define observation, investigation, reduction, and exit actions before the position is funded. Thresholds should reflect the stablecoin's design, the portfolio's purpose, normal market noise, tax and legal constraints, and the liquidity of the actual route.

The trigger should be multi-signal rather than price-only. A brief deviation on one thin venue can be a local market problem. A smaller deviation combined with failed withdrawals, worsening redemption terms, and inconsistent reserve communication can be more serious.

For each stage, document:

1. who has authority to act;
2. which balances are reduced first;
3. which exit pairs, venues, and chains are approved;
4. the maximum acceptable slippage and fees;
5. where proceeds may be held;
6. which evidence is required before returning to normal limits.

Avoid an all-or-nothing response when the evidence does not justify it. The purpose of staged rules is to reduce hesitation without turning every market wobble into forced trading.

Map failure domains, not just token tickers

Diversification only works when the exposures fail for different reasons. Create a row for every stablecoin implementation and columns for the dependencies that could stop access.

Positions A and C are not independent simply because one is wrapped or earning yield. They share issuer, banking, and chain dependencies, while Position C adds wrapper and protocol risk.

Apply a failure-domain cap to the combined exposure behind each material dependency:

failure-domain exposure = sum(all positions disabled by the same failure)

This is the stablecoin version of correlation-aware risk budgeting. It also prevents a portfolio from treating balances on several exchanges as diversified when those balances depend on the same issuer or chain. For context on separating exchange balances from broader on-chain signals, see the four-layer on-chain exchange reserves framework.

A monthly stablecoin monitoring dashboard

The stablecoin risk checklist is not a one-time approval. Review each material position on a fixed schedule and after any trigger event.

Track:

• latest reserve report date and publication lag;
• reserve-composition changes;
• supply growth or contraction;
• direct redemption terms and actual processing time;
• largest observed peg deviation across selected venues;
• spread, depth, and expected slippage for your exit size;
• balances by issuer, venue, chain, bridge, and wrapper;
• contract, administrator, custodian, or banking changes;
• regulatory or enforcement developments in relevant jurisdictions;
• date and result of the last exit drill.

Convert the dashboard into a simple operating cadence:

• Daily for operational balances: peg, withdrawals, chain health, route availability, and issuer alerts.
• Weekly for material reserves: cross-venue spreads, depth for the portfolio's size, concentration by failure domain, and policy-limit utilization.
• Monthly for full due diligence: reserve report freshness, redemption terms, legal and regulatory changes, custody evidence, contract controls, and a documented score update.
• Event-driven immediately: security incident, blacklist or freeze action, banking change, report qualification, bridge failure, regulatory order, or unexplained redemption delay.

The Bank for International Settlements has emphasized that stablecoins can carry structural limitations and risks distinct from tokenized deposits. The practical portfolio response is to monitor the entire claim and access chain, not just the market price.

Final takeaway

A stablecoin risk checklist should not end with “the token held its peg.” It should establish:

1. who owes the claim;
2. what supports it;
3. who can redeem;
4. whether your actual exit route works;
5. which issuer, venue, bank, chain, bridge, and protocol dependencies overlap;
6. how much exposure each portfolio job is allowed to carry.

Use the 15 checks to decide whether the structure is acceptable. Use the five buckets and six hard limits to decide how much exposure the portfolio can tolerate. Use the depeg playbook to decide what happens when evidence deteriorates. Then retest the assumptions before market stress turns a paper exit plan into a queue.

BTCMind can help organize issuer, reserve, liquidity, custody, and tail-risk questions into a repeatable research workflow. Explore the BTCMind research features or download the app to build a more disciplined review process. Final allocation and custody decisions remain the user's responsibility.

FAQ

What are the biggest stablecoin risks?

The main stablecoin risks are issuer failure, weak or illiquid reserves, redemption restrictions, secondary-market liquidity gaps, custody failure, smart-contract controls, chain or bridge problems, regulatory restrictions, and hidden concentration across shared dependencies.

How do you evaluate a stablecoin before holding it?

Identify the issuer and legal claim, inspect reserve composition and reporting, verify redemption eligibility, measure liquidity for your position size, review custody and contract controls, confirm the exact chain representation, and test a small exit.

Are stablecoins insured like bank deposits?

Not automatically. FDIC insurance protects eligible deposits at insured banks under specific conditions; it does not protect crypto assets merely because reserve assets may be held at a bank. Read the legal structure and coverage terms for the exact product.

How much of a crypto portfolio should be in stablecoins?

There is no universal percentage. Size the stablecoin sleeve by its purpose, liquidity horizon, loss tolerance, and the smallest applicable issuer, venue, chain, wrapper, and portfolio concentration limit.

Does using several stablecoins reduce risk?

Only when their failure paths are meaningfully different. Multiple tickers may still share the same exchange, custodian, banking rail, chain, bridge, or yield protocol.

Should yield-bearing stablecoins count as cash?

Usually not without a separate risk assessment. Yield can add borrower credit, leverage, smart-contract, liquidity, custody, or wrapper risk. Score and cap the yield-bearing product separately from the underlying stablecoin.

What should a stablecoin depeg plan include?

A depeg plan should define multi-signal triggers, decision authority, approved exit routes, reduction order, slippage limits, destination assets, and the evidence required before rebuilding exposure. Test the routes before a market event.

How do you calculate stablecoin liquidity for an allocation?

Measure the amount that can reach the intended destination within the required time and slippage budget through routes you can actually use. Compare that tested exit capacity with the planned position size; do not rely only on headline market volume.

Sources

• U.S. Congress: S.1582, GENIUS Act
• White House: Fact Sheet on the GENIUS Act signing
• Federal Deposit Insurance Corporation: Crypto and deposit insurance fact sheet
• European Commission: Crypto-assets and MiCA
• European Banking Authority: Asset-referenced and e-money tokens under MiCA
• Bank for International Settlements: Stablecoins versus tokenised deposits