Rules
Part of Crypto and stablecoin guide: a layer-by-layer overview
Crypto stablecoin problems: how to assess risk
Crypto stablecoin problems involve wallets, prices, withdrawals, bridges and yield claims. Check the evidence behind balances, transfers and returns.
What to take away
- A lost key and a custodian refusing a withdrawal are different failures, and they leave different evidence.
- A stablecoin trading below its reference value is a market event, not a finding about reserves or redemption.
- A withdrawal can stall before broadcast, in the mempool, or after confirmation at the receiving platform.
- A bridged token carries contract, validator and backing risk that the price on the destination chain does not show.
- Yield has to trace to an identifiable payer and obligation; a dashboard number traces to nothing.
Crypto stablecoin problems are easier to assess when you identify which layer stopped matching the state you expected. Do not file every loss under hacking.
USDC, USDT, and DAI are not interchangeable examples: their issuer or collateral structures, redemption eligibility, and governance differ. Check the specific token and the version you hold before drawing conclusions from another stablecoin’s disclosures or market behavior.
In the United States, the GENIUS Act (Guiding and Establishing National Innovation for U.S. Stablecoins Act) establishes a federal framework for payment stablecoins, but it does not make every token or holder’s redemption rights identical. State money-transmitter regimes and FinCEN requirements under the Bank Secrecy Act may also apply depending on the activity; NYDFS supervises certain issuers and publishes stablecoin guidance. Check which rules and issuer terms apply to the token in question.
For reserve evidence, read the issuer’s latest report and check its date, scope, assets covered, exclusions, and redemption terms. Look for whether an independent CPA performed an attestation under AICPA attestation standards; an attestation is not the same as a full financial-statement audit and does not by itself establish immediate redemption access.
Lost or compromised keys
A self-custody wallet has no support desk that can restore access. Whoever holds the seed phrase holds the funds, and no issuer, exchange or network can reverse a signed transfer.
Wallet control check
Is the wallet self-custodied or platform-controlled?
verify software, network, address path, last transaction
contact platform, preserve account and case records
The warning signs: the wallet will not sign, the recovery phrase fails, the device is gone, an outgoing transaction you did not send appears, or a new contract approval shows up.
If the platform holds the key, this is a custodial dispute and your evidence is the account record. If you hold it, verify the official software, the network setting, the derivation path, and your last known transaction.
Never type a seed phrase into a support form, a chat window, or a site reached from an unsolicited message.
If you suspect someone else controls the wallet, treat it as a compromised account. Move what remains only from a clean, verified setup. Revoke contract approvals where the wallet allows it. Save transaction hashes and addresses before you touch anything else. Nobody can reverse an irreversible transfer, so anyone charging a fee to do so is taking your money.
Depegging
A depeg is a market price moving away from its reference value. It is not proof that reserves are gone, and it is not proof that every holder can redeem at par.
Depeg causes vs evidence
Cause
- Reserve doubt
- Issuer reserve report
- Custodian stress
- Bank or custodian news
- Redemption limit
- Primary-market terms
- Thin liquidity
- Quote size, several venues
- Bridge discount
- Network variant price
- Oracle failure
- Feed source, timestamp
What to check
- Reserve doubt
- Custodian stress
- Redemption limit
- Thin liquidity
- Bridge discount
- Oracle failure
Causes differ, and they point to different evidence:
- doubt about the assets behind the token;
- stress at the bank or custodian holding reserves;
- a restriction on direct redemption;
- heavy selling into thin order books;
- network congestion;
- a discount on a bridged version;
- an order imbalance on one exchange;
- an oracle failure;
- forced liquidations in a lending protocol.
TerraUSD (UST) lost its peg in May 2022. It is a named example of algorithmic stablecoin risk, not a like-for-like reserve comparison for USDC or other fiat-referenced tokens.
A Federal Reserve staff note, “In the Shadow of Bank Runs: Lessons from the Silicon Valley Bank Failure and Its Impact on Stablecoins”, documents how concern about reserve exposure and contagion moved USDC and related mechanisms in March 2023. Read it as evidence of a transmission channel, not as a forecast for another token.
To judge a depeg, compare these five things:
- the issuer's direct redemption quote
- who is eligible to redeem
- prices on several secondary venues
- the network variant you hold
- the timestamp on each A price on one exchange at one moment is a thin basis for a conclusion.
Frozen withdrawals
A platform can block withdrawals while your balance still shows on screen. Maintenance, liquidity stress, a compliance review, and an account-security hold all look identical from the app. A network suspension, insolvency, and a mismatched deposit also look identical from the app.
Trace the stage of the transfer:
Where a withdrawal stalls
- Request created
- Platform approved
- Transaction broadcast
- Network confirmed
- Recipient credited
No hash means the transfer may never have reached the network, which makes it an internal ledger problem. A confirmed hash with no credit at the destination means the receiving side is applying its own asset, network, memo or account rules.
Keep the withdrawal request, the status history, the case ID, the address, the fee and dated screenshots. Do not send a second transfer hoping to free the first.
Bridge failure
A bridge locks an asset on one chain and issues a representation on another. The representation depends on several things:
- smart contracts
- validators
- relayers
- message verification
- governance keys
- liquidity pools
- the locked asset itself Any of those can fail.
Record these while the incident is fresh:
- source and destination networks;
- canonical bridge or third-party bridge;
- source asset contract and wrapped asset contract;
- the lock or burn transaction;
- the message ID;
- the mint or release transaction;
- validator or relayer status;
- the operator's official incident notice.
A destination token can keep trading after its backing is impaired. Price alone does not prove the bridge will release the original asset.
The Ronin bridge exploit in March 2022 illustrates how bridge trust assumptions can fail. Use a bridge incident to examine that system’s validator and control risks, not as proof that every bridged stablecoin is impaired.
Fake yield
A displayed yield can be paid from several sources:
- lending interest
- trading fees
- token emissions
- borrowed money
- maturity transformation
- a subsidy
- nothing at all The rate tells you which only if you ask who pays it.
Ask in this order: who pays, in which asset, and under what obligation. Is the principal lent, staked, bridged or pledged as collateral? Can the rate change without notice? Whose money absorbs a default? Is withdrawal immediate under stress? Does the balance sit on a public ledger, or only on the operator's website?
Platforms that show fabricated profits often demand a tax payment or a release fee before any withdrawal. Stop sending money and preserve the records.
Malicious links and seed theft
A fake stablecoin airdrop can imitate an issuer or wallet interface and ask for a wallet connection, signature, password, or seed phrase. Verify offers through a separately confirmed channel, inspect what a signature authorizes, and never disclose recovery credentials.
An unsolicited token does not have to be sold, claimed or opened. Hide it in the wallet interface if that option exists, and do not follow links attached to it.
Evidence table
| Layer | Evidence to keep |
|---|---|
| Wallet | Address, software version, signing result |
| Contract | Contract address, code version, admin events |
| Network | Hash, block, confirmations, fee |
| Bridge | Message and destination records |
| Platform | Account ID, request, status, case |
| Issuer | Terms, reserve report, redemption notice |
| Market | Venue, quote size, price, time |
| Bank | Payout or deposit reference |
Keep seed phrases and private keys out of the evidence package.
Common questions
Does a depeg prove insolvency?
No. It is a market event. Reserves, redemption terms, liquidity and the network all need checking before the price means anything about solvency.
Can support recover a seed phrase?
A legitimate self-custody product should never hold or ask for your seed phrase. Anyone who offers to recover it is describing a way to take the wallet.
Does a confirmed hash prove the platform credited me?
No. It proves a network record exists. The receiving platform still applies its own asset, network, memo and account rules before the balance appears.
Is high yield always fraud?
No, but a high rate needs an identifiable payer and an identifiable obligation. When neither can be named, the return is coming from new deposits or from nothing.
