Tokenization standards are the technical specifications that define how assets are represented, transferred, and governed on blockchains. Just as HTTP defines how web pages are transmitted, ERC token standards define the rules for how tokens behave — what functions they expose, how transfers are validated, what metadata they contain, and how they interact with wallets, exchanges, and DeFi protocols. The evolution of tokenization standards mirrors the evolution of on-chain use cases: ERC-20 (2015) enabled fungible tokens; ERC-721 (2018) enabled NFTs; ERC-4626 (2022) standardized yield-bearing vaults; ERC-1400/ERC-3643 enable regulated, compliant security tokens; and cross-chain standards (CCIP, ITS) enable tokens to move between blockchains. Understanding which standards apply to which asset types — and what compliance, composability, and interoperability each enables — is essential for anyone building or investing in the tokenized asset space.
Core Ethereum Token Standards
The following sections cover this in detail.
ERC-20 — Fungible Tokens
| Property | ERC-20 |
|---|---|
| Fungibility | Fully fungible — all units identical |
| Interfaces | transfer, approve, allowance, transferFrom |
| Use cases | Currency, governance tokens, DeFi tokens, stablecoins |
| Limitations | No built-in compliance; no metadata; simple binary approve |
ERC-721 — Non-Fungible Tokens
| Property | ERC-721 |
|---|---|
| Fungibility | Non-fungible — each token unique |
| Interfaces | ownerOf, safeTransferFrom, tokenURI |
| Use cases | NFT art, gaming items, real estate titles, identity |
| Limitations | One token per transaction — inefficient for bulk operations |
ERC-1155 — Multi-Token Standard
| Property | ERC-1155 |
|---|---|
| Fungibility | Mixed — supports both fungible and non-fungible in one contract |
| Interfaces | safeTransferFrom, safeBatchTransferFrom, balanceOfBatch |
| Use cases | Gaming items, fractional NFTs, multi-asset systems |
| Advantages | Batch operations save gas; single contract for multiple asset types |
Security Token Standards
The security model is explained below.
ERC-1400 — Security Token Standard
| Feature | ERC-1400 |
|---|---|
| Transfer restrictions | Partitioned balance — different “tranches” with different rules |
| Compliance hooks | canTransfer checks — block non-compliant transfers |
| Document management | On-chain document registry (prospectus, legal docs) |
| Issuance control | Issuer can control who may hold, transfer restrictions |
| Use cases | Tokenized equities, debt securities, fund shares |
ERC-3643 (T-REX Protocol) — Identity-Linked Security Tokens
| Feature | ERC-3643 |
|---|---|
| Identity requirement | Transfers require on-chain identity verification via ONCHAINID |
| Compliance engine | Modular compliance smart contracts — jurisdiction-specific rules |
| Registry | On-chain investor registry with verified identity claims |
| Use cases | Tokenized bonds/equities with KYC/AML enforcement |
| Adopters | BlackRock BUIDL, Ondo, Backed Finance, major institutional RWA |
DeFi-Native Standards
The following sections cover this in detail.
ERC-4626 — Tokenized Vault Standard
| Feature | ERC-4626 |
|---|---|
| Core concept | Shares of a yield-bearing vault — like a mutual fund share |
| Standardized interface | deposit, withdraw, redeem, convertToShares, convertToAssets |
| Use cases | Lending protocol receipts (aTokens), staked tokens (sUSDe), vaults |
| Composability | DeFi protocols can integrate any ERC-4626 vault with single adapter |
| Examples | sUSDe, Yearn vaults, AAVE aTokens (converted), Morpho markets |
Cross-Chain Standards
The following sections explain how this works.
Chainlink CCIP (Cross-Chain Interoperability Protocol)
| Feature | CCIP |
|---|---|
| Security model | Decentralized oracle + risk management network + ARM (Anti-fraud Risk Management) |
| Token transfers | Lock-and-mint or burn-and-mint for cross-chain token transfer |
| Messaging | Arbitrary data + token transfers in single transaction |
| Institutional use | SWIFT integration, institutional cross-chain pilots |
LayerZero OFT (Omnichain Fungible Token)
| Feature | OFT |
|---|---|
| Design | Burn on source chain → mint on destination chain |
| Config | Single token address model — canonical contract per chain |
| Use case | Tokens designed for multi-chain from launch (not just bridges) |
Common Misconceptions
“ERC-20 tokens can’t have compliance features.”
ERC-20 is a minimal interface — protocols can add compliance logic on top (transfer hooks, blacklists). USDC and USDT both use a custom ERC-20 variant with blacklisting and transfer pause capabilities. ERC-1400/ERC-3643 formalize these patterns with standardized interfaces.
“ERC-4626 is only for DeFi vaults.”
ERC-4626 is a general standard for any pool of assets that issues shares. It is being used for money market funds (tokenized T-bill products), staking pools, lending positions, and any yield-bearing asset where shares represent a proportional claim.
Criticisms
- Standard fragmentation: Multiple competing security token standards (ERC-1400, ERC-3643, ERC-1594, ERC-1462) exist — lack of single dominant standard complicates wallet/exchange integration for security tokens
- Backward compatibility: Newer standards (ERC-4626) are not automatically backward compatible with older deployments — protocol upgrades required when integrating
- Cross-chain fragmentation: CCIP, LayerZero OFT, Wormhole xAssets, Axelar ITS — multiple competing cross-chain token standards; bridges remain a security risk regardless of standard
- Compliance bottleneck: ERC-3643’s identity verification requirement adds friction — useful for institutional security tokens but creates barriers for retail DeFi composability
Social Media Sentiment
Tokenization standards receive primarily technical rather than social discussion. ERC-4626 generated significant DeFi excitement in 2022 as a composability unlock. ERC-3643 discussions are primarily institutional/B2B — less retail engagement. Cross-chain standard debates (CCIP vs. LayerZero) are ongoing and sometimes heated among DeFi developers. Generally: technical community positive on standardization; less mainstream engagement than asset-level narratives.
Last updated: 2026-04
Related Terms
Sources
- Ethereum EIPs (ERC-20, ERC-721, ERC-1155, ERC-4626) — ethereum.org / EIPs GitHub (2015-2022). The official Ethereum Improvement Proposals comprising each token standard — ERC-20 (EIP-20), ERC-721 (EIP-721), ERC-1155 (EIP-1155), ERC-4626 (EIP-4626).
- “ERC-3643 T-REX Protocol: Technical Specification” — T-REX Protocol / Tokeny Solutions (2023). Specification for ERC-3643 (formerly ERC-3643/T-REX) — the on-chain identity-linked compliant security token standard adopted by BlackRock BUIDL, Ondo Finance, and other major institutional RWA products.
- “ERC-4626: The DeFi Composability Standard for Yield Vaults” — a16z Crypto / EIP Authors (2022). Analysis and advocacy for ERC-4626 standardization — documenting the pre-standardization problem (every vault had a different interface, requiring custom adapters) and how ERC-4626 enabled composability.
- “Cross-Chain Token Standards: CCIP vs. LayerZero OFT vs. Wormhole xAssets” — Chainlink / LayerZero Research (2023-2024). Comparative analysis of leading cross-chain token standards — examining security models, design tradeoffs, and institutional adoption of CCIP, OFT, and Wormhole’s approach.
- “The Institutional Tokenization Stack: Standards, Infrastructure, and Adoption” — Boston Consulting Group / Ripple (2023). Analysis of enterprise tokenization infrastructure — mapping the standards layer, custody layer, settlement layer, and distribution layer of institutional tokenization and identifying which standards are gaining traction.