B20 · Base’s native token standard

E20

Base’s token standard, on Ethereum.

B20 is the token standard Base built into its own chain. E20 is the same idea for Ethereum. It’s an ordinary ERC-20, with one difference: the rules are locked when it’s deployed. Supply is set once. There’s no owner key, so no one can mint more, freeze a wallet, or change the token after it’s live.

Owners
None
Supply
Fixed
Hidden controls
0
Wallets
All

About

Where it comes from.

On Base, B20 is the chain’s built-in way to make a token. Projects share one reviewed template instead of each writing their own contract and hoping it holds up.

E20 takes that idea to Ethereum. It acts like any ERC-20, so wallets and exchanges already know how to read it. The difference is that the parts people worry about are fixed once the token goes live. Nothing about it can be edited afterward, because there is no address with permission to edit it.

Base · native standard
B20

Base’s token standard, built into the chain.

Ethereum · open standard
E20

The same standard, written for Ethereum. ERC-20 compatible, fixed supply, no owner.

Guarantees

No one holds the keys.

Most token scams trace back to one address that can do something to coins it doesn’t own. E20 doesn’t have that address. The items on the left aren’t switched off or sitting behind a timelock. There is no code for them in the contract at all.

Can’t happenno key can do these
×Minting new supply
×Freezing a wallet
×Pausing transfers
×Blocklists and allowlists
×Seizing your tokens
×Hidden transfer taxes
×Editing the token later
×Rebasing balances
×Proxy upgrades
×An owner or admin
Always onin every token
Send and receive
Approvals by signature (permit)
Burn your own tokens
On-chain name and metadata
A supply you can count
Source anyone can read

Burning only touches your own balance, the same way sending does. No one can burn your tokens for you.

Compatibility

Works everywhere ERC-20 works.

There’s nothing to integrate. An E20 token is a standard ERC-20, so it reads correctly the first time in wallets, on explorers, and across DeFi. It also supports permit, which lets someone approve a swap by signing a message instead of sending a second transaction.

Wallets DEXs and aggregators Block explorers Bridges Exchanges Portfolio trackers

Verify

Read it. Scan it.

Run an E20 token through a safety scanner and it passes, because the contract has no code that would fail the checks. The source is short, it lives on-chain, and the behavior is set at launch. The whole thing is printed further down this page.

No owner
No mint
No blacklist
No pause
No transfer tax
No proxy

Open source under MIT, and tested against the common ways permit tokens go wrong. None of that replaces your own look at the code, so read it before you trust a token.

Launch

Three steps to launch.

You don’t write any code. Choose the details, deploy, and publish the source. The token is readable by anyone from the first block.

1

Choose

Name, symbol, decimals, supply, and the wallet that gets it. That’s the whole setup, and it stays that way.

2

Deploy

Send it to Ethereum or any EVM chain. The full supply goes to the wallet you named, usually a treasury or liquidity wallet.

3

Verify

Publish the source on the explorer so anyone can read what they hold. It verifies the same day, with the settings listed here.

What you set at launch

Six values, chosen once. After deployment none of them move, since there’s no admin who could move them.

For builders
  • StandardERC-20 + permit
  • Compilersolc 0.8.26 · 200 runs · cancun
  • Contract size4.07 KB
  • LicenseMIT
  • Constructorname, symbol, decimals, recipient, supply, uri

Source

Every line of it.

No imports and no inheritance. This is the full contract behind an E20 token, the same source you compile and verify.

E20.sol · MIT · 281 lines