How a stablecoin is actually built.
A production stablecoin is four systems working together: a legal and reserve structure off-chain, a token contract or ledger configuration on-chain, a compliance control plane, and an attestation layer that proves the first matches the second.
End-to-end flow
Mint and redemption lifecycle
Layer 1 · Legal & reserves
The balance sheet comes first
Regulators judge a stablecoin by its reserves and redemption rights before they look at the code.
Issuing entity
A licensed issuer, such as a GENIUS Act permitted issuer, a MiCA e-money institution, or an HKMA or MAS licensee, or a bank issuing deposit tokens. Many use a bankruptcy-remote trust or SPV to hold reserves.
Eligible reserves
Coins, insured deposits, Treasury bills of 93 days or less, overnight repo and government money-market funds, at least 1:1 and diversified. Reserves may not be rehypothecated.
Redemption at par
A clear legal right to redeem at face value within a set timeframe (for example T+1 to T+5, depending on the regime), with published fees and no yield paid to holders.
Layer 2 · Token contract
Control roles in an institutional EVM stablecoin
Institutional ERC-20 stablecoins share one pattern: an upgradeable proxy in front of an implementation with separate privileged roles. Each role is a key-management and governance decision.
| Role | Capability | Typical control | Risk if compromised |
|---|---|---|---|
| Proxy admin | upgradeTo / upgradeToAndCall replaces all contract logic | Multisig plus timelock, held in cold custody | Total: arbitrary logic, including balances |
| Owner | Reassigns every other role, sets registries and oracles | Multisig, two-step ownership transfer | Takeover of all roles |
| Master minter | configureMinter(minter, quota) | Treasury operations under dual control | Unlimited minter creation |
| Minter | mint up to allowance, burn on redemption | HSM hot key, quota sized to funded orders | Mint up to remaining quota |
| Compliance | freeze, unfreeze, wipeAccount for sanctions and court orders | Compliance team, logged with a reason code | Wrongful freezes or seizure |
| Pauser | Global circuit breaker on transfers | Security on-call, fast response | Denial of service |
| Oracle / attestor | Publishes reserve attestations that can gate minting | Threshold signatures, rejects stale data | False solvency signal |
The same controls exist in the largest live coins. USDC and PYUSD have upgradeable proxies with blacklist and wipe functions. USDT's contract includes a fee parameter and a destroyBlackFunds function. The Lab's contract analysis module walks through each one.
Layer 3 · Compliance plane
Identity, sanctions and the Travel Rule
- Onboard primary holders (mint and redeem counterparties) with KYB/KYC. Secondary-market holders are handled through screening and freezes.
- Screen addresses against OFAC and UN lists on chain and in real time. Freeze on a match and document the legal basis.
- Allowlist registries (ERC-3643-style) or XRPL Credentials and Permissioned Domains for restricted tokens.
- Send Travel Rule (FATF R.16) originator and beneficiary data between VASPs for transfers above thresholds.
- Monitor for AML typologies such as peel chains, mixers and bridge hops, and report suspicious activity (SARs).
Layer 4 · Attestation
Proving reserves to outsiders
- Monthly independent accountant attestations (reserve composition and amount), plus audited annual financial statements.
- On-chain proof-of-reserve feeds that publish reserve totals and can block mints that would exceed them.
- Merkle commitments over holder liabilities, so anyone can check they were included without exposing the full ledger.
- Bank statements reconciled daily against on-chain supply using ISO 20022
camt.053. - Reject stale data: minting halts if the latest attestation is older than its policy window, for example 24 hours.
Bank-grade integration
Capital and messaging standards
Basel Group 1b
For a bank's exposure to get favorable capital treatment, the stablecoin must pass a redemption-risk test (reserves of short-dated, high-quality assets at least equal to outstanding tokens) and have a supervised, regulated issuer. Coins that fail fall to Group 2, where unhedged exposure carries a 1250% risk weight.
ISO 20022
Fiat legs travel as pacs.008 credit transfers and are reconciled with camt.053 statements. On-chain transaction hashes go in remittance fields, so bank back offices can match token events to cash movements.
Identifiers
ISO 24165 Digital Token Identifiers (DTI) name the token unambiguously across chains. ISO 17442 Legal Entity Identifiers (LEI) identify the issuer and counterparties in reporting.