ERC-20 is the standard interface for fungible tokens on Ethereum, defined in EIP-20 by Fabian Vogelsteller and Vitalik Buterin on November 19, 2015: six required functions, three optional ones and two events that every token contract exposes in the same way. WETH is the textbook example, because the WETH9 contract implements all nine functions and both events in plain sight, while native ETH implements none of them. The rule that follows: any contract that can handle one ERC-20 token can handle WETH, and none can handle ETH directly.

Key takeaways
  • The interface: totalSupply, balanceOf, transfer, transferFrom, approve and allowance are required; name, symbol and decimals are optional; Transfer and Approval are the events (EIP-20, Final).
  • ETH came first: Ethereum mainnet launched on July 30, 2015 and EIP-20 was created 112 days later, which is why ETH has no ERC-20 contract and WETH exists.
  • Supply equals reserve: WETH9's totalSupply() returns its own ETH balance, 2,175,140.76 on November 21, 2026 (Ethereum RPC, block 26,464,782).
  • Lost tokens: at least $83,656,418 of ERC-20 tokens had been lost by June 20, 2024 because they were sent to contracts that cannot handle them (ethereum.org).

What ERC-20 Is

ERC-20 is a list of functions and events that a token contract must expose so that wallets, exchanges and other contracts can work with it without custom code. ethereum.org describes the tokens it covers as fungible: each unit is identical to every other unit in type and value. The standard does not define what a token is worth or who issues it; it defines how its balances are read and moved.

ERC stands for Ethereum Request for Comments. Fabian Vogelsteller proposed ERC-20 in November 2015, and the text was published as EIP-20, whose status is Final (eips.ethereum.org). Because the interface is fixed, a wallet shows any ERC-20 balance by calling balanceOf() and a DEX trades any ERC-20 token through the same transferFrom() call.

The Nine Functions and Two Events of ERC-20

The ERC-20 interface has nine functions and two events, and WETH9 implements every one of them. The table lists them with what each does and how WETH answers it on Ethereum mainnet (verified source on Sourcify and Etherscan, values read on November 21, 2026).

Function or event Required What it does In WETH9
name() Optional Human-readable name “Wrapped Ether”
symbol() Optional Ticker “WETH”
decimals() Optional Digits after the point 18
totalSupply() Yes Tokens in existence Returns the contract’s ETH balance
balanceOf(owner) Yes Balance of an address Public mapping
transfer(to, value) Yes Sends tokens from the caller Calls transferFrom() with the caller as sender
transferFrom(from, to, value) Yes Moves tokens on someone’s behalf Checks and reduces the allowance
approve(spender, value) Yes Lets another address spend up to a limit Sets the allowance, emits Approval
allowance(owner, spender) Yes Remaining approved amount Public mapping
Transfer event Yes Logged on every move Emitted by transferFrom()
Approval event Yes Logged on every approve Emitted by approve()

EIP-20 marks name, symbol and decimals as optional and says other contracts must not expect them. In practice almost every token sets them, because wallets need them to display a balance.

Why ETH Is Not an ERC-20 Token

ETH is not an ERC-20 token because it is the native coin of the network, not the state of a contract. Ether balances live in the account records of Ethereum itself, are moved by plain transactions and pay for gas; there is no ETH contract to call balanceOf() or approve() on. Ethereum mainnet went live on July 30, 2015 (ethereum.org), and EIP-20 was created on November 19, 2015, 112 days later.

That gap is the reason for WETH. A DEX pool or a lending market is written against the ERC-20 interface and moves funds with transferFrom(); native ETH has no such function, so the contract cannot pull it. Wrapping puts ETH behind the interface on the same chain (why WETH exists): the ETH does not leave Ethereum, it changes standard.

How WETH Implements ERC-20

WETH implements ERC-20 with two extra functions that connect it to native ETH. deposit() takes the ETH sent with the call and credits the same amount of WETH to the sender; withdraw() burns WETH and sends the same amount of ETH back. Both emit their own events, Deposit and Withdrawal, next to the standard Transfer and Approval. How a wrap and an unwrap look from the user’s side is on the what is WETH section.

Three details of the WETH9 source, compiled with solc 0.4.19 and verified on Etherscan since December 2017, make it the reference implementation people point to:

  • Supply equals reserve: totalSupply() does not count anything; it returns the ETH balance of the contract, 2,175,140.76 on November 21, 2026, so supply and backing cannot drift apart.
  • No owner: there is no admin function, no pause and no upgrade path; no address can mint WETH without depositing ETH or freeze a balance.
  • Unlimited approval: when an allowance is set to the maximum value (uint(-1)), transferFrom() skips the decrement, so a spender approved for the maximum never runs out.

In a wallet the result is two separate balances on the same address: native ETH and the WETH token. A self-custody wallet that supports several networks, such as WETH Wallet, shows WETH on Ethereum and WETH on Base as two separate assets, because each is a different ERC-20 contract.

Decimals: How ERC-20 Amounts Are Stored

ERC-20 contracts store every amount as a whole number of base units and use decimals() to say where the point goes. EIP-20 gives the example of 8 decimals: divide the stored number by 100,000,000 to get the amount a user sees. The table compares three tokens read on Ethereum mainnet on November 21, 2026.

Token decimals() Base units in 1 token Same as
WETH 18 10^18 1 ETH in wei
WBTC 8 10^8 1 BTC in satoshi
USDC 6 10^6 One dollar in millionths

WETH matches ETH exactly: 18 decimals, so 1 WETH is 10^18 base units just as 1 ETH is 10^18 wei, and a wrap never rounds. Tokens that represent other assets pick the precision of that asset; WBTC follows Bitcoin’s 8 (WETH vs WBTC compares the two wrappers).

Approve and transferFrom: Why Apps Ask for Permission

An app asks you to approve a token because ERC-20 gives a contract no way to take tokens unless their owner has set an allowance first. The flow has two steps: approve(spender, amount) records the limit, and the app’s contract later calls transferFrom() to move up to that amount. That is why the first swap of a token on a DEX starts with a separate approval transaction.

EIP-20 notes a known weakness: changing an allowance from one non-zero value to another can let a spender use both amounts if it acts in between, so interfaces should set the allowance to 0 first. Allowances stay in force until changed, which is why revoking unused ones matters; the details are in WETH approvals and allowances.

What ERC-20 Cannot Do

  • It cannot pay gas: network fees are paid in ETH, never in an ERC-20 token, including WETH; a wallet holding only tokens cannot send them.
  • It cannot tell a contract it received tokens: a plain transfer() to a contract that has no way to move tokens out leaves them stuck; at least $83,656,418 was lost this way by June 20, 2024 (ethereum.org), and standards such as ERC-223 and ERC-1363 were proposed to fix it.
  • It cannot prove a token is genuine: any contract can return the name “Wrapped Ether”; only the address identifies the real WETH, listed on the contract addresses section.
  • It cannot move tokens between networks: WETH on Ethereum and WETH on Arbitrum are two ERC-20 contracts with separate supplies; moving between them is a bridge operation.
  • It does not cover NFTs: unique tokens follow other standards, such as ERC-721; ERC-20 covers interchangeable units only.

ERC-20 FAQ

No. ETH is the native coin of Ethereum and has no token contract; it went live on July 30, 2015, before the ERC-20 standard existed. WETH is the ERC-20 form of ETH.