CANTORFI B20 GUIDE
The B20 token standard on Base, explained
The B20 token standard is Base's native token format. A B20 token behaves like an ERC-20 for wallets and applications, but it is not a contract someone wrote and deployed: every B20 is created by a single factory built into the chain, in one of two variants, Asset or Stablecoin, with a supply cap, roles, pausing and transfer policies as standard options.
What makes B20 different from an ERC-20
An ERC-20 is whatever its contract code says. Two tokens with the same interface can hide very different mint functions, fees or blacklists, which is why a token has to be audited before it is trusted. A B20 token has no custom code: the logic is implemented once by the chain, as a precompile introduced with Base's Beryl upgrade, and each token is only a configuration of that logic.
For a wallet, an exchange or a lending vault, a B20 answers the usual ERC-20 calls. What changes is that its rules can be read as data: who holds which role, whether a cap exists, whether transfers are paused, which policy gates an account.
- ERC-20-compatible interface
- One factory creates every token
- No custom contract code per token
- Roles, cap, pause and policies readable on-chain
Asset and Stablecoin: the two variants
The Asset variant is the general form, for a project, company or community token. The Stablecoin variant is for fiat-backed money: it fixes decimals at 6 and carries a currency code declared at creation, such as USD, that cannot be changed afterwards.
Both variants share the same controls. A supply cap can make the supply finite. Roles decide who may mint, pause or administer. A policy can restrict which accounts may hold or move the token, which issuers of regulated assets need.
How a B20 token is launched
Launching a B20 is one call to the B20Factory with the variant, a salt, the parameters and optional initial calls such as a first mint. Because the address is derived from those inputs, it can be predicted before the transaction is sent.
CantorFi's preparation service validates a request, predicts that address and returns the unsigned factory transaction. The creator signs it from their own wallet; no private key is ever sent to CantorFi.
How to inspect a B20 token before trusting it
CantorFi's inspection service takes a token address, checks that the factory recognises it, pins every read to the same recent block and returns metadata, supply and cap, pause state, policy records and the permissions of a given account.
That answers what a token can do, not whether its issuer is honest. A finite cap and a clean policy are useful facts about a token that may still be worthless.
Testnet evidence is not mainnet performance.
CantorFi's current public deployment is a Base Sepolia developer preview with temporary governance. Test balances, rates, volume, fees and positions have no economic value and must not be reported as production TVL, revenue, liquidity or guaranteed return.
FAQ
Questions about B20 token standard
01What is a B20 token?
A token created by Base's native B20 factory. It is compatible with ERC-20 and comes in two variants, Asset and Stablecoin, with built-in options for supply caps, roles, pausing and transfer policies.
02Is B20 the same as ERC-20?
It exposes the ERC-20 interface, so wallets and applications treat it the same way. The difference is underneath: the logic is provided by the chain instead of a contract deployed for each token.
03How do I create a B20 token?
Call the B20Factory with the variant and parameters you want. CantorFi can prepare that transaction unsigned so that you review and sign it from your own wallet.
04Does a B20 token have a price?
Only if someone trades it. The standard defines how the token behaves, not what it is worth.