Token Standards and Tokenomics
Token standards define the contract interface that wallets and applications use to handle a token. Tokenomics is the set of supply, allocation, distribution, and control rules around that token.
itDistributed systems, messaging, and integration | OpenSkills.info
Recommended first:blockchain-fundamentals
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic — Token Standards and Tokenomics
Token standards are the shared controls on a token contract: the names, inputs, events, and receiver behavior that let wallets, exchanges, and other contracts recognize what they are dealing with. They exist because every application inventing its own transfer button is a fine way to turn interoperability into a scavenger hunt. ERC-20 covers interchangeable balances; ERC-721 gives each asset its own identifier; ERC-1155 keeps several token types under one contract.
Tokenomics is the second layer, where the interesting arguments start wearing administrative hats. It describes supply, allocation, distribution, utility, governance, and control. A token can follow ERC-20 perfectly and still have a reachable mint function, a pauser, a treasury controller, or a changeable vesting schedule. The standard tells software how to call the contract. It does not certify scarcity, fairness, safety, or decentralization.
The useful mental model is a pair of maps. The interface map shows balances, transfers, approvals, allowances, token identifiers, and receiver checks. The authority map shows who can create supply, stop transfers, change metadata, upgrade logic, release allocations, or execute governance. Allowance is delegated transfer authority, not a decorative setting: an approved spender can use transferFrom within its scope. That is why it belongs on the authority map with the more dramatic-looking roles.
The surprising part is that a supply number is only a photograph. Vesting is also a release rule, not a force field around the token. Read the code path that changes supply or a schedule, the address allowed to call it, and the events and state changes that reveal what happened. A voting token adds another map layer: voting weight matters, but so do proposal rules, quorum, the executor, upgrade authority, pause authority, and treasury control. Governance is not a magic word; it is a route from a decision to a state change.
Start with the Intro when you need the full distinction between asset model, interface, and economic rules. Use Slides for the review order, Cheatsheet for the function and authority anchors, and Practice for a repeatable record. The Quiz is where the terms stop nodding politely and ask whether you can tell an interface guarantee from an economic claim. That is the whole game: read the standard, then read the implementation and its authority paths.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://ethereum.org/developers/docs/standards/tokens/
Supports
- Token standards as common interfaces for interoperability across wallets and applications
- ERC-20 fungible tokens and ERC-721 and ERC-1155 use cases
- https://eips.ethereum.org/EIPS/eip-20
Supports
- ERC-20 balances transfers approvals allowances delegated transfers events and optional metadata
- ERC-20 was created in November 2015
- ERC-20 specifies the allowance update warning
- https://eips.ethereum.org/EIPS/eip-721
Supports
- ERC-721 identifiers ownership approvals operator approvals safe transfers and metadata
- ERC-721 was created in January 2018
- https://eips.ethereum.org/EIPS/eip-1155
Supports
- ERC-1155 multiple token types operator approvals and single and batch transfers
- ERC-1155 was created in June 2018
- https://eips.ethereum.org/EIPS/eip-4626
Supports
- Tokenized vault interface and standardized asset and share accounting
- ERC-4626 was created in December 2021
- https://docs.openzeppelin.com/contracts/5.x/erc20
Supports
- Maintained ERC-20 implementation documentation and extension-oriented supply design
- https://eips.ethereum.org/EIPS/eip-223
Supports
- ERC-223 was created in May 2017 and specifies receiver-aware transfers
- https://eips.ethereum.org/EIPS/eip-777
Supports
- ERC-777 was created in November 2017 and specifies operators and hooks
- https://eips.ethereum.org/EIPS/eip-2612
Supports
- ERC-2612 was created in April 2020 and specifies signed approvals
- https://eips.ethereum.org/EIPS/eip-2981
Supports
- ERC-2981 was created in September 2020 and standardizes NFT royalty information
- https://docs.openzeppelin.com/contracts
Supports
- OpenZeppelin Contracts provides token-standard implementations access control governance and Contracts Wizard
- https://docs.sablier.com/
Supports
- Sablier documents token distribution concepts and protocol integration
- https://github.com/sablier-labs/flow
Supports
- Sablier Flow publishes source under Business Source License and GPL terms
- https://www.safe.global/
Supports
- Safe provides open-source multisignature treasury controls with thresholds roles and spending limits
- https://docs.snapshot.box/
Supports
- Snapshot provides governance spaces proposals voting strategies and execution setup documentation
- https://github.com/snapshot-labs/snapshot-v1
Supports
- Snapshot V1 is published under the MIT license
