Why stablecoins became a building block for DeFi
A stablecoin aims to track a reference value, such as one dollar. Redemption means exchanging the token back under an issuer's or protocol's rules. A market price near one dollar does not prove that every holder can use that exit.
The token chapter separated a software interface from the claim attached to it. Now imagine building a market or a loan when the unit used to quote prices also moves sharply. A trader may want to distinguish the performance of an asset from the changing value of the quote currency. A borrower may want to understand a repayment obligation in a familiar reference unit. A payment recipient may want predictable purchasing power. These are related needs, but they are not identical promises.
| Use | What becomes easier to express? | What remains to check? |
|---|---|---|
| Payment | A price or invoice in a familiar unit. | Can this recipient obtain usable money after fees? |
| Trading | A quote asset for comparing trades. | Are there enough buyers or sellers for the amount you want to trade at that price? |
| Lending | A debt amount and interest obligation. | What assets secure the loan (collateral), when can they be sold to cover it (liquidation), and when can funds be withdrawn? |
A fictional borrower owes 100 dollar-targeted units. If each unit trades at $0.90, the token count of the debt and its market value have diverged. Whether repayment still requires 100 units depends on the loan's actual terms. A target unit of account does not eliminate market, contract or redemption risk.
A dated example connects this need to DeFi development: Uniswap's March 23, 2020 v2 overview described direct token-to-token pools and used DAI/USDC to illustrate a pair. That was a design overview with a future launch target, not evidence that v2 launched on that date. It shows a use case for stablecoin pairs; it does not establish the first stablecoin or quantify market-wide adoption.
The gain is composability: a token can move between applications under compatible interfaces. The cost is that each application inherits relevant assumptions about that token, then adds its own. Depositing a stablecoin into a lending pool adds a lending exposure; bridging it adds another route to investigate.
Check your reasoning: if a token stays near $1 on a chart, does every holder have a $1 redemption right?
No. Market trading, issuer redemption and the particular holder's eligibility are separate. The four-layer framework below shows what evidence to collect.
Choose your depth: continue to DeFi Summer for the historical story, or open the detailed mechanism guide below to study reserves, redemption and a worked cash-out example.
Detailed guide: reserves, redemption rules and the cash you receive
Reviewed and updated: October 19, 2026.
A stablecoin aims to track a reference value. Whether it is useful for a payment depends on more than that target: the holder must identify the correct token, move it on a supported network and have an available exit route. These are separate parts of the architecture.
Four layers to examine
| Layer | Question | Typical evidence |
|---|---|---|
| Reference value | What unit does the token aim to track? | Token documentation and terms |
| Backing or stabilizing mechanism | What supports the obligation or market intervention? | Reserve reports, collateral contracts and mechanism rules |
| Holder exit | Who can redeem, for what, when and at what cost? | Eligibility, redemption terms and market depth |
| Transfer and control | Which network and contract apply, and who can change or restrict them? | Deployment records, permissions and supported-network lists |
A reserve claim does not answer the last three questions by itself. A publicly observable smart contract also does not verify every off-chain asset held for it.
How the broad design families differ
Reserve-backed issuance connects tokens to assets held under an issuer's arrangements. Collateralized borrowing creates debt against a position subject to valuation and liquidation rules. Algorithmic stabilization uses rules and incentives to influence supply or demand, sometimes with external collateral and sometimes without it. Real systems can combine features, so these are analytical categories rather than permanent product labels.
For that reason, this guide no longer lists BUSD as an unqualified active example or FRAX as permanently partially algorithmic. A named implementation needs a version, date and verified operating status. Nor does a crypto-collateral label establish complete independence from banks or issuers of the collateral assets.
A primary-source example: USDC terms
Circle's USDC terms, checked October 19, 2026, distinguish holders with Circle Mint accounts from other holders and condition direct redemption on eligibility and account requirements. The page states that these terms apply outside the EEA and directs EEA holders to separate materials. It also distinguishes issuer redemption from a market price on third-party platforms and does not promise that the latter always equals $1.
The lesson is specific: before relying on a redemption route, establish that it applies to the actual holder and jurisdiction. Buying a token from an exchange does not by itself demonstrate access to every service offered by its issuer.
A payment can settle while its exit value changes
Suppose a fictional recipient receives 1,000 units of a dollar-targeted token. The transfer is confirmed, but the available sale price is $0.995. Gross sale proceeds are $995. If the exchange charges 0.2% of proceeds and the fiat withdrawal costs $3, net cash is $995 − $1.99 − $3 = $990.01. The blockchain transfer and the final cash amount answer different questions.
The example assumes a full fill at that price and excludes tax and any separately paid network fee. It is not a current quote. Compare the same asset, network, size and settlement currency when comparing routes.
Native tokens, wrappers and yield products
A token bridged to another chain can add another contract or custody dependency. A similarly named ticker is not enough to establish issuer backing or network support. Record the contract address and the official route used to obtain it.
Likewise, a savings or lending wrapper can add a separate return mechanism and withdrawal rule. Holding the base stablecoin and depositing it into a yield-bearing product are different exposures. Trace who pays the return and what must happen to redeem the wrapper.
Use the architecture to ask concrete questions instead of awarding a blanket stability, decentralization or regulatory-risk score. This page is a mechanism guide; it does not claim that all stablecoins share one legal status or that a target price is guaranteed.
Sources and scope
- Circle: USDC terms, geographic scope and redemption conditions
- Frax documentation: FRAX v3 design scope
- Sky Protocol Docs: collateral liquidation
Continue reading: Algorithmic stabilization · Collateral and liquidation · RWA claims and exit risk
Editorial update: Replaced stale product and draft-law references with a mechanism framework; qualified redemption eligibility; added a net-cash example and wrapper-dependency checks.