Demo
Network Status
B20 shipped in the Beryl upgrade. The B20 Stablecoin and Asset variants are active on Base Mainnet. Before you deploy on any network, confirm the variant is active withisActivated on the Activation Registry.
createB20 requires no role or allowlist. Any account can create a stablecoin once the variant is active, and the Factory keeps no access to the token after creation.
Integrate Stablecoins From Other Issuers
Wallets, apps, and payment providers that hold or move stablecoins issued by others work with the same interface for every issuer:- One integration. Every B20 stablecoin exposes the same ERC-20 surface and
IB20Stablecoininterface, so code written for one issuer’s token works for any other. - Per-token rules. Each token enforces its own issuer’s policies on the sender, receiver, and transfer executor. A transfer of one issuer’s token succeeds only if the accounts pass that token’s policies. Call
isAuthorizedon the Policy Registry to check an account before you send. - Shared compliance lists. Policies live in the Policy Registry, not on the token, so one policy can back many tokens. Issuers that agree on a list can attach the same policy ID.
- Conversion and redemption. B20 has no protocol-level conversion between stablecoins from different issuers. Each token is a separate asset: convert through an onchain swap or a venue that supports both tokens. Fiat redemption happens offchain with each issuer, which then burns the redeemed supply.
Guides
Issue Your Stablecoin
Create a fiat-backed token in one call.
Mint Supply
Issue new tokens as reserves grow.
Burn Supply
Retire tokens on redemption.
Restrict Who Can Hold It
Limit transfers to approved accounts.
Block an Account
Stop one address on a compliance hold.
Recover Funds
Reclaim and reissue a blocked balance.
Pause Activity
Halt transfers, mints, or burns.
Reconcile with Memos
Match onchain activity to your books.