What is a redemption run, and how does it differ from the stablecoin depeg covered in an earlier article?
A redemption run refers to a large number of stablecoin holders concentrating their redemption requests within a short window, with this demand's scale exceeding the speed the issuer or protocol can process it promptly, causing some holders to potentially be temporarily unable to smoothly recover equivalent-value assets even though reserves are theoretically sufficient. The essence of this phenomenon is a 'liquidity timing gap' problem — even if the total value of assets the issuer holds is entirely sufficient to cover all circulating stablecoins, if these reserve assets themselves aren't in a form instantly convertible to cash (say, partly held in bank time deposits or short-term bonds), facing a concentrated surge in redemption demand can still produce the awkward situation of 'having the assets but unable to mobilize the cash in time.'
The key difference from the stablecoin depeg covered in an earlier article lies in 'causal order': a depeg refers to the outcome of the market trading price deviating from the target value, while a redemption run is one of the possible causes leading to a depeg — panicked redemption demand surging concentrated together lets the market observe the signal that 'the issuer's redemption processing speed has slowed,' which in turn triggers more people rushing to redeem or panic-selling in the secondary market, causing price to deviate from the peg target as a result. A redemption run could be described as a mechanism-level phenomenon at the cause level, while a depeg is one of the price outcomes this mechanism could lead to.
Why does a redemption run happen, and what are the underlying triggering causes?
A few common triggering causes: wavering trust in reserve transparency — if the market starts questioning whether a stablecoin issuer's reserves are genuinely sufficient or include less liquid or higher-risk assets, this wavering trust itself could prompt some holders to rush to redeem ahead of others to avoid being late; a problem at infrastructure related to the issuer — even if the reserves themselves are entirely fine, if the bank or financial institution where the issuer holds reserve funds itself encounters a crisis (such as a bank failure), once the market observes this signal, even if the issuer can ultimately recover the funds, panic sentiment could still prompt a large number of holders to rush to redeem before the funds arrive; panic contagion effect — the crypto market reacts to negative news at extreme speed, and the real-time transparency of social media and on-chain data lets even minor developments potentially get amplified and spread within an extremely short window, letting an originally rational wait-and-see attitude rapidly turn into concentrated redemption behavior under a herd effect.
Worth noting: these causes frequently stack together — an originally minor trust concern could get amplified into large-scale concentrated redemption through social media's rapid spread effect, and the concentrated redemption itself further reinforces the market's wavering trust in that stablecoin, forming a self-reinforcing loop.
How does a redemption run actually unfold, and what does one complete incident flow look like?
A typical redemption run's unfolding process involves several stages:
The entire incident, from trigger to conclusion, can run through one complete round within days — the duration depends on whether the root problem can be clearly, quickly resolved.
What's the practical impact of a redemption run on everyday users, and how can you assess whether a stablecoin you hold is prone to this kind of incident?
For a user holding a stablecoin, a redemption run's most direct risk is 'even if reserves are theoretically sufficient, you might still temporarily be unable to smoothly redeem or sell at a reasonable price during the incident' — if you happen to need this capital during this 'temporarily stuck' period, it causes real liquidity trouble, and even if price ultimately corrects back and reserves genuinely proved sufficient, the inconvenience and potential loss during that period genuinely occurred.
A few concrete indicators for assessing whether a stablecoin you hold is prone to a redemption run: the reserve assets' liquidity structure — verify what proportion of the issuer's publicly disclosed reserve composition is instantly convertible cash or cash equivalent versus what proportion is other assets requiring time to convert (like bank time deposits or short-term bonds) — the more conservative the liquidity structure, the higher the pressure resistance typically holds up under concentrated redemption demand; the degree of dispersion in where reserves are held — if reserves are concentrated at a single bank or institution, once that counterparty runs into trouble, the risk affecting all reserves runs higher, while dispersing across multiple institutions theoretically lowers this concentration risk; whether the issuer has ever experienced a similar stress test before, and whether the handling afterward was transparent and quick — this kind of historical record provides a concrete reference baseline. For users, a more practical response is diversifying across the types of stablecoins held, not concentrating most of your liquidity needs on a single stablecoin — this way, even if a particular stablecoin genuinely experiences a redemption run, your overall capital usage doesn't end up completely stuck.
On March 10, 2023, Silicon Valley Bank collapsed and was taken over by U.S. federal regulators — one of the fastest large-bank runs in history, with over $42 billion withdrawn in a single day. Stablecoin issuer Circle subsequently confirmed that roughly $3.3 billion of USDC's reserves (about 8% of total reserves at the time) was held at Silicon Valley Bank, temporarily unavailable. Once the news broke, the market saw a large-scale wave of redemption — on-chain data showed Circle net-burning roughly $1 billion of USDC in a single day — and USDC's price briefly fell to around $0.87. It wasn't until U.S. regulators announced Silicon Valley Bank's depositors (including the portion exceeding the insurance cap) would be fully guaranteed and Circle confirmed the funds had arrived that USDC's price corrected back to $1 within a few days. The entire incident fully demonstrates a classic case of 'reserves ultimately sufficient, yet still triggering a genuine redemption run and price depeg.'
As a market risk term, there's no positive trade-off to speak of — a redemption run represents a purely temporary liquidity risk for holders. The only discussable trade-off: an issuer choosing to allocate reserve assets more conservatively (entirely cash) lowers run risk, but at the cost of forgoing extra return from holding assets like short-term bonds; choosing a more dispersed bank-holding strategy lowers single-counterparty risk, but might raise operational complexity and management cost — a trade-off in the issuer's operating strategy, not a choice a user can unilaterally change. What a user can do mainly involves diversifying across different stablecoins held and understanding each one's reserve structure.