ERC-20 (Token Standard)
ERC-20 is a technical standard that defines a common set of rules for creating and issuing tokens on the Ethereum blockchain. When a token is described as "ERC-20," it means its underlying smart contract follows this shared blueprint, which is what allows thousands of different tokens - from stablecoins to governance tokens - to work seamlessly with the same wallets, exchanges, and decentralized applications, rather than each requiring custom integration.
The standard was proposed on November 19, 2015 by developer Fabian Vogelsteller, building on an earlier idea sketched out by Ethereum co-founder Vitalik Buterin, and was formalized as Ethereum Improvement Proposal 20 (EIP-20) - "ERC" stands for Ethereum Request for Comment, the community process used to standardize how the network's software behaves. Before ERC-20, developers building tokens on Ethereum had to write bespoke code for basic functions, and wallets or exchanges had to build custom support for every single token - a fragmented, error-prone situation the standard was designed to fix.
Mechanically, ERC-20 requires a token's smart contract to implement a specific set of functions: totalSupply (how many tokens exist), balanceOf (how many tokens an address holds), transfer (send tokens to another address), approve and allowance (authorize a third party, such as a decentralized exchange, to move a set amount of your tokens on your behalf), and transferFrom (execute that authorized transfer). It also mandates two standardized events, Transfer and Approval, that get logged on-chain whenever tokens move or permissions change - this is what lets a block explorer or wallet app reliably detect and display any ERC-20 token without needing to know anything about it in advance.
The practical significance is enormous: the great majority of tokens traders encounter on Ethereum-based exchanges and decentralized finance (DeFi) platforms - including major stablecoins like USDT and USDC (when issued on Ethereum), governance tokens like UNI (Uniswap) or LINK (Chainlink), and countless smaller project tokens - are ERC-20 tokens. Knowing this matters practically for traders because it means the same Ethereum wallet address and the same type of transaction (an ERC-20 transfer, paying Ethereum's network gas fee) can be used to hold and move any of them, and because sending an ERC-20 token to a wallet or exchange address that does not support the Ethereum network can result in permanently lost funds - a common and costly beginner mistake.
ERC-20 is a crypto-specific concept with no equivalent in forex, stocks, or commodities trading - it describes a software standard native to blockchain systems. It is worth distinguishing from broader cryptography: ERC-20 defines how a token behaves and moves, while the digital signatures that authorize any Ethereum transaction (including ERC-20 transfers) rely on separate cryptographic techniques, such as elliptic curve cryptography, operating underneath the token standard rather than being part of it. Other blockchains have their own comparable standards - for example, BEP-20 on BNB Chain and TRC-20 on Tron are deliberately similar to ERC-20 but are technically distinct and not interchangeable with it.
The approve function is where most avoidable losses on Ethereum begin. Interacting with almost any decentralised application requires granting its contract permission to move a token on your behalf, and the convention for years was to request an unlimited allowance so that the user would not have to approve again. That permission persists indefinitely and survives the application being abandoned, its contract being upgraded, or its keys being stolen - so a wallet can be emptied by a protocol its owner used once, years earlier, and forgot. Several block explorers and dedicated tools list a wallet's outstanding allowances and let them be revoked, and reviewing them occasionally is the single most useful maintenance task a token holder can perform.
The second habit is verifying the contract address rather than the name. Nothing in the standard reserves a name or a symbol, so anyone can deploy a token calling itself USDC with the same ticker and the same logo, and it will display correctly in a wallet that has not been told otherwise. Only the contract address distinguishes the real one, which is why exchanges and issuers publish it and why a token that arrives unrequested in a wallet should be treated as bait rather than as a windfall. The related quirk worth knowing is that the standard's transfer function has no way of telling a receiving contract that it was paid, so tokens sent directly to a contract address that was not written to expect them are frequently unrecoverable - a flaw later standards attempted to fix without ever displacing this one.