What is a token standard?
A token standard is a shared set of rules for how a token contract behaves, so wallets and apps can work with any token that follows it.1 On Ethereum, these rules are published as proposals called ERCs.2,3
A token is a contract that keeps a list
An Ethereum token lives inside a smart contract. The contract keeps track of the tokens and how many each address holds.4,5 Tokens can stand for almost anything: reputation points, a game character's skills, a share in a company, a dollar, or an ounce of gold.4
Why tokens need shared rules
Imagine every token used its own words for "send" and "balance". Every wallet would need new code for every token. Token standards solve this.1 They define how tokens behave, so a new token works with existing wallets, exchanges and apps.1
The ERC-20 standard puts it plainly. A standard interface lets any token be reused by other apps, from wallets to exchanges.5
A standard is a list of functions
A token standard is mostly a list. It names the functions a contract must have and what each one does.5 It also names events: signals the contract must give when something happens, such as a transfer.5 If a contract has all of these, it can be called by the standard's name, such as an ERC-20 token contract.4
Standards use a few words in capitals with exact meanings, borrowed from an internet rulebook called RFC 2119.6,7
- MUST means the rule is an absolute requirement.7
- SHOULD means follow it, unless there is a good reason not to and you understand the effects.7
- MAY or OPTIONAL means the item is truly optional.7
Where standards come from
Ethereum's standards usually start as Ethereum Improvement Proposals, or EIPs.2 An EIP is a design document. It gives information to the Ethereum community or describes a new feature.3 Its author is responsible for building agreement in the community.3
There are three types of EIP: Standards Track, Meta and Informational.3 Standards Track has four categories, and one of them is called ERC.3,2 ERCs are standards for apps, including token standards.3 ERC stands for Ethereum Request for Comments.4 EIP-1's style rule says to write them as ERC-20, ERC-721, and so on.3
How finished is a standard?
Every EIP has a status. The main stages are Draft, Review, Last Call and Final.3 A Final EIP is the finished standard. After that, it should only change to fix mistakes or add clarifications.3 A proposal left inactive for six months or more is marked Stagnant.3
The five Ethereum standards in this module all show the status Final on their official pages.5,6,8,9,10
| Standard | What it is for | Created |
|---|---|---|
| ERC-20 | Fungible tokens5 | November 20155 |
| ERC-721 | Non-fungible tokens (NFTs)6 | January 20186 |
| ERC-1155 | Many token types in one contract8 | June 20188 |
| ERC-3643 | Tokens only approved investors may hold10 | July 202110 |
| ERC-4626 | Vaults that issue shares9 | December 20219 |
A standard is not a safety check
A standard describes behaviour. It does not prove that a contract behaves well. ERC-4626 warns that a harmful contract could match the list of functions but not follow the rules.9
The next five lessons take each standard in the table in turn. The last lesson shows how Solana handles tokens differently: shared Token Programs (the original one or Token 2022) hold the rules for every token, instead of each token having its own contract.
- Token standards. ethereum.org developer docs, page updated 15 July 2026.
- Ethereum development standards. ethereum.org developer docs, page updated 26 September 2025.
- EIP-1: EIP Purpose and Guidelines. Ethereum Improvement Proposals (Martin Becze, Hudson Jameson and others), created 27 October 2015, status Living.
- ERC-20 Token Standard. ethereum.org developer docs, page updated 9 July 2026.
- ERC-20: Token Standard. Ethereum Improvement Proposals (Fabian Vogelsteller, Vitalik Buterin), created 19 November 2015, status Final.
- ERC-721: Non-Fungible Token Standard. Ethereum Improvement Proposals (William Entriken, Dieter Shirley, Jacob Evans, Nastassia Sachs), created 24 January 2018, status Final.
- RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. Internet Engineering Task Force (S. Bradner), March 1997.
- ERC-1155: Multi Token Standard. Ethereum Improvement Proposals (Witek Radomski, Andrew Cooke, Philippe Castonguay, James Therien, Eric Binet, Ronan Sandford), created 17 June 2018, status Final.
- ERC-4626: Tokenized Vaults. Ethereum Improvement Proposals (Joey Santoro, t11s, Jet Jadeja, Alberto Cuesta Cañada, Señor Doggo), created 22 December 2021, status Final.
- ERC-3643: T-REX - Token for Regulated EXchanges. Ethereum Improvement Proposals (Joachim Lebrun, Tony Malghem, Kevin Thizy, Luc Falempin, Adam Boudjemaa), created 9 July 2021, status Final.
General education built from the publicly available sources listed above. Not financial, legal, tax or investment advice. Naming a company, project or regulator is not an endorsement either way. Last checked 2026-10-22. Terms and disclaimer.