Skip to main content

Tokens for Smart Contract Developers

Token standards are agreed interfaces that let wallets, exchanges and other contracts treat assets uniformly. ERC-20 defines fungible tokens, ERC-721 non-fungible tokens and ERC-1155 multiple token types in one contract. Using audited libraries such as OpenZeppelin avoids rewriting sensitive logic and keeps a token compatible with the wider ecosystem.

Stage: Standards and Patterns · Part of the Smart Contract Developer roadmap · Last reviewed 19 November 2026

What to learn in Tokens

Tokens interview questions

Why does ERC-20 have both approve and transferFrom?

A contract cannot pull tokens from a user without permission. The user calls approve to set an allowance for a spender, and the spender then uses transferFrom within that limit. It enables patterns such as exchanges and staking, but unlimited approvals carry risk.

What is the difference between ERC-20 and ERC-721?

ERC-20 tokens are fungible, so any unit is interchangeable and balances are plain numbers. ERC-721 tokens are unique, each has a token id and an owner, and metadata can differ per token. ERC-1155 supports both kinds in one contract.

Where Tokens fits in the Smart Contract Developer roadmap

Tokens belongs to the Standards and Patterns stage (intermediate level), which takes about 25 hours. Real contracts.

Back to the full Smart Contract Developer roadmap