What are ERC20 Token?

All news is rigorously fact-checked and reviewed by leading blockchain experts and seasoned industry insiders.

ERC20 was created to standardize how tokens behave on Ethereum, enabling seamless integration between wallets, exchanges, and smart contracts.

Why ERC20 Was Invented

Before the ERC20 standard, developers on Ethereum faced significant challenges when building and exchanging tokens. Each token implementation was custom-coded, making interoperability across different platforms complex and error-prone. For example, if a wallet or exchange wanted to support multiple tokens, it had to write individual integration logic for each one. This fragmented landscape slowed adoption and created friction in the early Ethereum ecosystem.

The introduction of ERC20 in 2015 by developer Fabian Vogelsteller offered a common blueprint for fungible tokens. It established a minimal yet powerful interface that all compliant tokens had to implement. The result was a technical unification that unlocked the first true token economy on Ethereum. It became the backbone of the 2017 ICO boom and laid the foundation for today’s decentralized finance (DeFi) and NFT markets.

Core ERC20 Architecture

Smart Contract-Based Structure

ERC20 tokens are not standalone assets. They exist entirely as smart contracts deployed on the Ethereum blockchain. Each token contract includes a predefined set of rules, including how the tokens can be transferred, how balances are tracked, and how supply is managed. The smart contract ensures that these operations are secure and tamper-proof.

Standardized Functions

At the heart of every ERC20 token are six mandatory functions and three optional ones. These functions enable other contracts, wallets, or DApps to interact with the token without needing custom code for each token. Here’s a breakdown of the key required functions:

This uniformity allows services like MetaMask, Uniswap, or Coinbase Wallet to interact with virtually any ERC20 token without needing custom logic for each.

How ERC20 Tokens Are Created

Deployment Process

Creating an ERC20 token involves writing a smart contract in Solidity, Ethereum’s most common programming language. Developers typically use frameworks like Hardhat or Truffle to compile, test, and deploy the contract. The token’s supply, name, symbol, and decimal precision are all configured at the time of deployment.

Many projects use standardized templates like OpenZeppelin’s audited contracts to reduce risks and ensure consistency. For instance, a developer can create a secure token contract by importing @openzeppelin/contracts/token/ERC20/ERC20.sol and customizing a few parameters. This modular architecture allows rapid development while maintaining high security standards.

Token Minting and Burning

Some ERC20 contracts support minting (creating new tokens) and burning (destroying tokens), while others have a fixed supply. Minting mechanisms are often restricted to a governance contract, DAO, or multisig wallet. These supply adjustments are publicly verifiable on-chain, providing transparency for token holders.

Use Cases of ERC20 Tokens

Utility Tokens

Most ERC20 tokens are utility tokens used to access services within a decentralized application. For example, BAT is used in the Brave Browser ecosystem to reward users for viewing ads. Similarly, GRT powers query operations in The Graph protocol.

Governance Tokens

ERC20 tokens are commonly used for on-chain governance. Projects like Compound (COMP) and Uniswap (UNI) give holders the right to vote on proposals regarding protocol upgrades, fees, and other key decisions. Voting mechanisms are implemented through smart contracts and operate autonomously.

Stablecoins

Some of the most widely used stablecoins like USDC, USDT, and DAI are ERC20 tokens. They track the value of fiat currencies and are essential for trading and DeFi liquidity. While USDC and USDT are issued by centralized entities, DAI is algorithmically stabilized through overcollateralization.

Wrapped Tokens

Wrapped tokens represent assets from other blockchains in ERC20 format. A prominent example is Wrapped Bitcoin (WBTC), which brings BTC liquidity to Ethereum-based DeFi. Wrapping is managed by custodians who hold the original asset and issue the equivalent ERC20 token on Ethereum.

This cross-chain tokenization allows users to access Ethereum’s smart contract ecosystem using assets they already own on other networks.

ERC20 Token Interoperability

Wallet Integration

Because all ERC20 tokens follow a universal standard, they can be added to any Ethereum-compatible wallet with ease. Wallets like MetaMask, Trust Wallet, and Ledger Nano X support automatic token detection or allow manual token addition using the contract address. This plug-and-play compatibility was crucial to the rapid growth of Ethereum’s token ecosystem.

Exchange Listings

Exchanges also benefit from ERC20 standardization. Platforms such as Coinbase and Binance can integrate new ERC20 tokens quickly using the same core logic. This streamlined process dramatically reduces listing complexity compared to non-standardized assets.

Smart Contract Composability

One of Ethereum’s most powerful features is composability—the ability for smart contracts to interact with one another like building blocks. ERC20 tokens are fully composable with other DeFi protocols, including lending platforms like Aave, yield aggregators like Yearn, and decentralized exchanges like Uniswap. This seamless interoperability creates a programmable financial ecosystem with unparalleled flexibility.

Decimals, Tickers and Token Identity

Each ERC20 token has a few core metadata parameters that define its identity on-chain:

• Name: The readable name of the token, e.g., “Tether USD.”
• Symbol: The ticker symbol (e.g., “USDT”).
• Decimals: Specifies the number of digits after the decimal point. For example, 18 decimals means 1 token = 10¹⁸ smallest units.

This metadata is mostly cosmetic but is essential for front-end applications and human-readable interfaces. Most wallets and exchanges pull this info directly from the token contract using view functions.

Gas and Transaction Fees

Transferring ERC20 tokens is not free. Unlike Bitcoin or native ETH transfers, which directly move coins from one address to another, ERC20 transfers are smart contract executions. This means every ERC20 token transfer requires gas and is subject to Ethereum network congestion.

The cost of transferring tokens fluctuates based on block space demand. During high usage periods, such as NFT drops or meme coin hype cycles, ERC20 transactions can become expensive. This limitation has sparked discussions around gas-efficient token standards like ERC223 or layer-2 solutions such as Polygon and Optimism.

Token Approvals and Security

Before a smart contract can spend a user’s tokens (e.g., swapping on Uniswap), the user must explicitly approve the contract. This approval is managed using the approve() function. While convenient, it introduces certain risks.

For instance, malicious contracts may trick users into approving unlimited token access. Therefore, many wallets now show warnings for unlimited approvals, and some users manually revoke old allowances via tools like Revoke.cash.

Why ERC20 Was Invented

Before the ERC20 standard, developers on Ethereum faced significant challenges when building and exchanging tokens. Each token implementation was custom-coded, making interoperability across different platforms complex and error-prone. For example, if a wallet or exchange wanted to support multiple tokens, it had to write individual integration logic for each one. This fragmented landscape slowed adoption and created friction in the early Ethereum ecosystem.

The introduction of ERC20 in 2015 by developer Fabian Vogelsteller offered a common blueprint for fungible tokens. It established a minimal yet powerful interface that all compliant tokens had to implement. The result was a technical unification that unlocked the first true token economy on Ethereum. It became the backbone of the 2017 ICO boom and laid the foundation for today’s decentralized finance (DeFi) and NFT markets.

Core ERC20 Architecture

Smart Contract-Based Structure

ERC20 tokens are not standalone assets. They exist entirely as smart contracts deployed on the Ethereum blockchain. Each token contract includes a predefined set of rules, including how the tokens can be transferred, how balances are tracked, and how supply is managed. The smart contract ensures that these operations are secure and tamper-proof.

Standardized Functions

At the heart of every ERC20 token are six mandatory functions and three optional ones. These functions enable other contracts, wallets, or DApps to interact with the token without needing custom code for each token. Here’s a breakdown of the key required functions:

This uniformity allows services like MetaMask, Uniswap, or Coinbase Wallet to interact with virtually any ERC20 token without needing custom logic for each.

How ERC20 Tokens Are Created

Deployment Process

Creating an ERC20 token involves writing a smart contract in Solidity, Ethereum’s most common programming language. Developers typically use frameworks like Hardhat or Truffle to compile, test, and deploy the contract. The token’s supply, name, symbol, and decimal precision are all configured at the time of deployment.

Many projects use standardized templates like OpenZeppelin’s audited contracts to reduce risks and ensure consistency. For instance, a developer can create a secure token contract by importing @openzeppelin/contracts/token/ERC20/ERC20.sol and customizing a few parameters. This modular architecture allows rapid development while maintaining high security standards.

Token Minting and Burning

Some ERC20 contracts support minting (creating new tokens) and burning (destroying tokens), while others have a fixed supply. Minting mechanisms are often restricted to a governance contract, DAO, or multisig wallet. These supply adjustments are publicly verifiable on-chain, providing transparency for token holders.

Use Cases of ERC20 Tokens

Utility Tokens

Most ERC20 tokens are utility tokens used to access services within a decentralized application. For example, BAT is used in the Brave Browser ecosystem to reward users for viewing ads. Similarly, GRT powers query operations in The Graph protocol.

Governance Tokens

ERC20 tokens are commonly used for on-chain governance. Projects like Compound (COMP) and Uniswap (UNI) give holders the right to vote on proposals regarding protocol upgrades, fees, and other key decisions. Voting mechanisms are implemented through smart contracts and operate autonomously.

Stablecoins

Some of the most widely used stablecoins like USDC, USDT, and DAI are ERC20 tokens. They track the value of fiat currencies and are essential for trading and DeFi liquidity. While USDC and USDT are issued by centralized entities, DAI is algorithmically stabilized through overcollateralization.

Wrapped Tokens

Wrapped tokens represent assets from other blockchains in ERC20 format. A prominent example is Wrapped Bitcoin (WBTC), which brings BTC liquidity to Ethereum-based DeFi. Wrapping is managed by custodians who hold the original asset and issue the equivalent ERC20 token on Ethereum.

This cross-chain tokenization allows users to access Ethereum’s smart contract ecosystem using assets they already own on other networks.

ERC20 Token Interoperability

Wallet Integration

Because all ERC20 tokens follow a universal standard, they can be added to any Ethereum-compatible wallet with ease. Wallets like MetaMask, Trust Wallet, and Ledger Nano X support automatic token detection or allow manual token addition using the contract address. This plug-and-play compatibility was crucial to the rapid growth of Ethereum’s token ecosystem.

Exchange Listings

Exchanges also benefit from ERC20 standardization. Platforms such as Coinbase and Binance can integrate new ERC20 tokens quickly using the same core logic. This streamlined process dramatically reduces listing complexity compared to non-standardized assets.

Smart Contract Composability

One of Ethereum’s most powerful features is composability—the ability for smart contracts to interact with one another like building blocks. ERC20 tokens are fully composable with other DeFi protocols, including lending platforms like Aave, yield aggregators like Yearn, and decentralized exchanges like Uniswap. This seamless interoperability creates a programmable financial ecosystem with unparalleled flexibility.

Decimals, Tickers and Token Identity

Each ERC20 token has a few core metadata parameters that define its identity on-chain:

• Name: The readable name of the token, e.g., “Tether USD.”
• Symbol: The ticker symbol (e.g., “USDT”).
• Decimals: Specifies the number of digits after the decimal point. For example, 18 decimals means 1 token = 10¹⁸ smallest units.

This metadata is mostly cosmetic but is essential for front-end applications and human-readable interfaces. Most wallets and exchanges pull this info directly from the token contract using view functions.

Gas and Transaction Fees

Transferring ERC20 tokens is not free. Unlike Bitcoin or native ETH transfers, which directly move coins from one address to another, ERC20 transfers are smart contract executions. This means every ERC20 token transfer requires gas and is subject to Ethereum network congestion.

The cost of transferring tokens fluctuates based on block space demand. During high usage periods, such as NFT drops or meme coin hype cycles, ERC20 transactions can become expensive. This limitation has sparked discussions around gas-efficient token standards like ERC223 or layer-2 solutions such as Polygon and Optimism.

Token Approvals and Security

Before a smart contract can spend a user’s tokens (e.g., swapping on Uniswap), the user must explicitly approve the contract. This approval is managed using the approve() function. While convenient, it introduces certain risks.

For instance, malicious contracts may trick users into approving unlimited token access. Therefore, many wallets now show warnings for unlimited approvals, and some users manually revoke old allowances via tools like Revoke.cash.

Event Logs and Transparency

Transfer and Approval Events

One of the most powerful features of ERC20 tokens is their built-in transparency through event logging. The standard defines two key events: Transfer and Approval. These events are emitted by the smart contract and recorded on-chain whenever tokens are transferred or allowances are updated.

These logs are indexed and searchable by Ethereum node providers and block explorers like Etherscan. For instance, when a user transfers tokens from one address to another, the contract emits a Transfer event, which includes the sender, receiver, and the amount.

This transparent architecture makes ERC20 tokens ideal for audits, compliance reporting, and analytics. Tools like Etherscan or Dune Analytics offer dashboards that track token movements, holder distributions, and contract activity.

Token Holder Tracking

On-Chain Ownership Data

Unlike traditional asset systems where ownership data is private or siloed, ERC20 tokens expose holder data directly on-chain. The balanceOf(address) function allows anyone to query any wallet’s balance. This openness is key for building trust and transparency in decentralized systems.

It also enables services to build advanced analytics, such as whale tracking, holder rankings, and behavior-based targeting. For example, a DeFi protocol might target early adopters of a competing token based on on-chain data. This form of programmable outreach is only possible due to the ERC20 standard’s transparency.

Snapshot Voting and Airdrops

Projects frequently use ERC20 balances to take snapshots—a record of token holdings at a specific block height. These snapshots determine voting rights in DAOs or eligibility for token airdrops. Tools like Snapshot.org enable gasless off-chain voting based on on-chain ERC20 balances.

This mechanism allows protocols to make governance decisions without incurring gas fees or creating friction for users. Airdrops, on the other hand, use these snapshots to distribute new tokens to existing holders, often as a form of reward or incentive.

Compatibility With DeFi Protocols

Lending and Borrowing

Protocols like Aave, Compound, and MakerDAO rely heavily on ERC20 tokens. Users can supply ERC20 tokens to liquidity pools and earn interest. In return, they receive interest-bearing tokens such as aTokens or cTokens, which are themselves ERC20-compliant and represent the user’s claim on the protocol.

This recursive use of ERC20 tokens inside DeFi systems exemplifies the standard’s composability. These tokens are not just assets; they become building blocks in a larger programmable economy.

Liquidity Pools and DEXs

Decentralized exchanges like Uniswap and Balancer use ERC20 tokens to create liquidity pools. A pair of ERC20 tokens is locked into a smart contract, allowing users to swap between them using automated market maker logic. In return, liquidity providers earn trading fees and often receive LP tokens (another ERC20 token) to represent their share in the pool.

This mechanism transforms passive holders into active participants in the ecosystem while unlocking new ways to earn yield on ERC20 holdings.

Advanced Token Features

Permit Function and EIP-2612

One notable upgrade to the ERC20 model is the introduction of EIP-2612, which adds a permit() function. This allows users to approve token allowances using off-chain signatures rather than on-chain transactions. The result: zero gas approvals, which reduce costs and enhance UX.

This feature is already supported by major DeFi protocols and wallets. By reducing friction in the token approval process, permit-enabled ERC20 tokens offer better accessibility and security. More technical info is available at the original EIP-2612 page.

Hooks, Pausable, and Role-Based Access

Some ERC20 tokens implement custom logic through hooks, allowing for additional functionality like transaction fees, blacklists, or rewards. Others implement Pausable functionality to stop all transfers in an emergency. Access control mechanisms like Ownable or AccessControl restrict administrative tasks to specific roles.

While not part of the base ERC20 specification, these enhancements offer flexibility for developers to tailor token behavior to specific use cases while still maintaining ERC20 compatibility.

Storage Structure of ERC20 Tokens

Internally, ERC20 token contracts use Solidity’s mapping data structure to track balances and allowances. Here’s a simplified breakdown:

• mapping(address => uint256) balances; stores how many tokens each address owns.
• mapping(address => mapping(address => uint256)) allowances; stores how many tokens a third party is allowed to spend on behalf of the owner.

Each time a token is transferred, these mappings are updated, and a Transfer event is emitted. This architecture allows for gas-efficient token management, even as the total number of holders grows.

Token Indexing and Off-Chain Analytics

Indexing services like The Graph or Covalent allow developers and analysts to query ERC20 token activity without running full Ethereum nodes. These services provide subgraphs that track token transfers, balances, and events, making it easier to build dashboards or trading tools.

For example, an exchange might use The Graph to display real-time ERC20 balances across trading pairs. Traders can use these insights to monitor whale activity, gas usage, or liquidity inflows—all thanks to the standardized event logs defined by ERC20.

Security Considerations in ERC20 Implementation

Common Vulnerabilities

Despite its standardization, ERC20 contracts can be vulnerable to poor implementations. Some historical examples include:

• Missing return values: Older tokens did not return a boolean on transfer, breaking compatibility with newer smart contracts.
• Reentrancy bugs: Poorly written callbacks in transfer functions could be exploited if not properly secured.
• Integer overflows: Before Solidity 0.8.0, developers had to manually guard against overflows. Libraries like SafeMath mitigated this.

Today, most developers rely on battle-tested templates from OpenZeppelin and other audited libraries. Nonetheless, understanding these risks is crucial for builders and investors alike.

Upgradeability and Proxies

Some projects implement proxy contracts to make their ERC20 tokens upgradeable. This allows token logic to evolve over time while preserving the contract address and balances. However, it introduces complexity and potential centralization, as proxy administrators may retain control over critical components.

While powerful, such upgrade patterns must be transparently communicated to token holders to maintain trust in decentralized ecosystems.

ERC20 Beyond Ethereum

The ERC20 standard has been so influential that it has inspired equivalent token formats on other blockchains. For example:

• BEP-20 on Binance Smart Chain
• TRC-20 on TRON
• SPL on Solana (not 1:1 compatible, but similar in spirit)

These standards aim to replicate the success of ERC20 in their respective ecosystems. However, none have achieved the same level of adoption and ecosystem integration as the original ERC20 on Ethereum.

FAQ: What are ERC20 Tokens?