ERC-20 vs ERC-721 vs ERC-1400 vs ERC-3643: Token Standards Explained

ERC-20 handles fungible assets and ERC-721 handles unique ones, but neither can enforce investor restrictions - ERC-3643 was built specifically to add compliance to the $32B tokenized asset market.

Introduction

ERC-3643 governs $32B+ in tokenized real-world assets (RWAs) across 180+ jurisdictions — yet it was proposed only in 2021, three years after ERC-1400 attempted the same compliance problem and came up short. The gap between these standards is architectural: ERC-3643 enforces compliance on-chain through a persistent identity registry; ERC-1400 depends on an off-chain signing key that can fail silently. Choosing the wrong standard for a regulated asset creates legal exposure no post-deployment upgrade can fix, because redeploying requires migrating all existing token holders.

This article maps five active Ethereum token standards — ERC-20, ERC-721, ERC-1155, ERC-1400, and ERC-3643 — across fungibility, compliance architecture, and live deployment data from Securitize ($4B+ assets under management (AUM)), Ondo Finance ($2.5B total value locked (TVL)), and Centrifuge ($1.6B TVL). The result is a concrete decision framework for selecting the right standard across equity, debt, real estate, collectibles, and gaming assets.

Why Does Token Standard Choice Determine Legal Enforceability and On-Chain Behavior?

Token standards are legally operative rule sets, not interface specifications — they determine transfer validity, who can hold a token, and whether an asset is securities-compliant before a single token is minted. Five Ethereum standards encode this logic differently, each producing a distinct ownership regime with compounding regulatory consequences.

Why Token Standards Are Legally Operative Rule Sets, Not Just Interfaces

A token standard defines the function calls a smart contract must expose — approve, transfer, and transferFrom for ERC-20; ownerOf and safeTransferFrom for ERC-721. But function signatures alone do not determine compliance. Whether a token can enforce know your customer (KYC) checks, restrict transfers to whitelisted wallets, or encode partition-level vesting rules depends entirely on which standard underlies the contract architecture. A project that deploys a real estate fund as an ERC-20 token ships with no transfer restrictions, no investor identity checks, and no mechanism to block non-accredited buyers — regardless of what the off-chain legal documents state. The on-chain code is the operating rule set. If the standard does not enforce compliance, no subsequent patch can retrofit it without redeploying the entire token contract and migrating all holders.

How Five Ethereum Standards Occupy Distinct Compliance and Fungibility Layers

The five standards in active institutional use — ERC-20, ERC-721, ERC-1155, ERC-1400, and ERC-3643 — divide across two axes. On fungibility: ERC-20 and ERC-3643 tokens are interchangeable units; ERC-721 tokens are unique by ID; ERC-1155 supports both; ERC-1400 tokens are fungible but partition-able into sub-classes with distinct transfer rules. On compliance: ERC-20, ERC-721, and ERC-1155 carry no built-in compliance logic; ERC-1400 adds compliance through off-chain signing keys and document registries; ERC-3643 embeds it on-chain via an identity registry that validates every wallet before every transfer. These two axes determine which standard fits which asset class — and the table below maps each combination against live examples.

Data current as of May 2026.

ERC-20 occupies the first and most heavily deployed layer of this stack — powering a $322B stablecoin market while encoding zero compliance logic.

How Does ERC-20 Define Fungible Token Behavior and Power the Trillion-Dollar DeFi Stack?

Proposed in 2015, ERC-20 defines six functions — totalSupply, balanceOf, transfer, transferFrom, approve, and allowance — that give any Ethereum contract a standard token interface. Every unit is identical to every other — ERC-20 is the default standard for currencies, stablecoins, and decentralized finance (DeFi) protocol tokens.

ERC-20 Mechanics — Fungibility, Approve-Transfer Pattern, and DeFi Composability

The approve-transferFrom pattern is ERC-20's most consequential design decision. A holder calls approve(spender, amount) to authorize a third-party contract — a decentralized exchange, a lending protocol, or an automated market maker — to move tokens without requiring the holder's private key at execution time. The authorized contract then calls transferFrom to execute the transfer autonomously. Uniswap's liquidity pools, Aave's collateral vaults, and Compound's money markets all depend on this pattern to process billions in daily volume. ERC-20 carries no transfer restrictions, no identity check, and no concept of investor eligibility — any wallet can hold and transfer any ERC-20 token unconditionally, which is both its greatest composability advantage and its disqualifying limit for regulated assets.

ERC-20's Trillion-Dollar Stablecoin and DeFi Ecosystem Footprint

The scale of ERC-20 adoption is measured by the assets it underpins. Tether (USDT) — an ERC-20 token — reached $189.6B in market capitalization in May 2026, representing 58.8% of the $322.7B total stablecoin market (as of May 2026) . USD Coin (USDC) holds a further $79B on the same standard. Beyond stablecoins, ERC-20 underlies governance tokens (UNI, COMP, MKR), yield-bearing instruments (stETH, aUSDC), and wrapped assets (WBTC) moving hundreds of billions in daily DeFi volume. Approximately 200,000 ERC-20-compatible contracts are deployed on Ethereum; around 5,476 are actively tracked, with a combined market capitalization of approximately $498.9B (as of May 2026) . The standard's total absence of compliance logic made every security token standard that followed necessary.

ERC-721 solved a different problem — creating tokens that cannot be substituted for one another — but introduced structural limits that make it equally unsuited to regulated financial assets.

How Does ERC-721 Encode Unique Digital Ownership and Where Does Its Compliance Model Break?

ERC-721, finalized in 2018, defines the non-fungible token (NFT) standard — every token receives a unique integer ID, and ownership is tracked individually on-chain. No two ERC-721 tokens are interchangeable, which makes the standard the architectural foundation for digital art markets, gaming items, and unique deed-like instruments.

ERC-721 Non-Fungibility — Unique Token IDs, safeTransferFrom, and Metadata URI

ERC-721 tracks ownership through a tokenId-to-address mapping: ownerOf(tokenId) returns the current holder, and safeTransferFrom verifies the receiving address can handle ERC-721 tokens before executing the transfer. Each token links to a metadata URI — an off-chain JSON file specifying name, description, and image — giving NFT marketplaces a standard way to display asset attributes. A holder can approve one operator per specific token or grant setApprovalForAll permission to transfer their entire collection. By Q1 2026, ERC-721 tokens generated $720M in monthly average trading volume (as of Q1 2026) , with gaming NFTs accounting for 38% of all NFT transaction volume.

ERC-721 Compliance Limitations — No KYC, No Transfer Lock, No Programmatic Restrictions

ERC-721 encodes ownership uniqueness but no compliance logic. There is no mechanism to restrict transfers to KYC-verified wallets, block sales to non-accredited investors, or enforce holding-period lockups within the standard itself. A security issued as an ERC-721 token — a fractionalized property deed, a private equity interest, a revenue-share certificate — transfers to any wallet without restriction unless the issuer deploys a separate transfer restriction layer on top of the base contract. That approach introduces architectural fragility: the restriction logic and the token contract are separate systems that can fall out of sync. For financial assets subject to KYC and Anti-Money Laundering (AML) requirements, ERC-721's compliance gap is structural, not a configuration-level shortfall.

ERC-1155 addresses a different gap — the gas inefficiency of minting thousands of unique tokens — without solving the compliance problem ERC-721 shares.

How Does ERC-1155 Enable Fungible and Non-Fungible Assets in a Single Smart Contract?

ERC-1155, proposed in 2018, allows a single smart contract to manage multiple token types simultaneously — both fungible and non-fungible — within one deployment. A gaming studio can issue currency, equipment, and unique collectibles from one ERC-1155 contract rather than deploying separate ERC-20 and ERC-721 contracts for each asset class.

ERC-1155 Multi-Token Contract — Fungible and Non-Fungible in One Deployment

ERC-1155 introduces a token ID system where the issuer assigns fungibility per ID. Token ID 1 represents 10,000 identical in-game gold coins; token ID 2 represents a single unique sword. The balanceOf function accepts both a wallet address and a token ID — the return value is that account's balance of that specific type. Transfers use a safeTransferFrom call that bundles multiple token types in one transaction through the safeBatchTransferFrom function — the result is fewer on-chain operations and significantly lower gas costs versus deploying multiple ERC-721 contracts.

ERC-1155 Batch Transfer Efficiency and Gaming-Native Adoption

The batch transfer function makes ERC-1155 the standard of choice for gaming studios issuing large, diverse item sets. Gods Unchained, Sorare, and most major blockchain gaming platforms deploy ERC-1155 for in-game economies. OpenSea and other NFT marketplaces support ERC-1155 alongside ERC-721 through the same listing interface. Like ERC-20 and ERC-721, ERC-1155 carries no built-in compliance logic — transfers execute without identity verification, which means it shares the same disqualification from regulated securities use as the standards it extends.

ERC-1400 was the first standard designed specifically to address securities compliance — built by Polymath in 2018 to embed transfer restrictions and legal document links directly into token architecture.

What Is ERC-1400 and How Does It Embed Securities Compliance Into Token Transfer Logic?

Proposed by Polymath in 2018, ERC-1400 was the first attempt to embed securities compliance natively into a token standard. Rather than building compliance as a wrapper around an existing token, ERC-1400 introduces a partition system that allows different transfer rules for different subsets of the same token — enabling corporate cap table structures where founders, employees, and investors hold tokens with different vesting and restriction profiles.

ERC-1400 Architecture — Partitions, Document Management, and Off-Chain Key Validation

ERC-1400's partition system divides token holdings into labeled classes — "unvested," "Series A," "restricted" — each governed by distinct transfer rules. A transfer within one partition can be permitted while the same transfer fails in another — issuers gain granular control over complex cap table structures. ERC-1400 also links tokens to off-chain legal documents through a document registry: issuers attach operating agreements, prospectuses, or subscription agreements to the token contract — the result is an auditable link between the on-chain asset and its legal wrapper. Compliance validation relies on an off-chain signing key — before a transfer executes, the issuer's compliance engine generates a certificate, signed off-chain, that the contract verifies on-chain. This architecture gives the issuer full control over transfer eligibility without storing identity data on-chain.

ERC-1400 Limitations — ERC-20 Incompatibility, Key Custody Risk, and Cap Table Complexity

The off-chain signing key is ERC-1400's most significant structural weakness. If the key is compromised, lost, or the compliance provider goes offline, the entire token transfer mechanism breaks — no transfers can execute until the key is replaced and the contract updated. ERC-1400 tokens are also not fully ERC-20 compatible: the partition functions and document registry methods fall outside the ERC-20 interface — ERC-1400 tokens are incompatible with standard ERC-20 wallets, decentralized exchanges, and DeFi protocols without custom adapter contracts. A holder cannot deposit an ERC-1400 token into Uniswap or Aave without such an adapter. Gas costs per transfer also run higher than ERC-20 or ERC-3643 due to certificate verification and partition lookup overhead on each transaction.

ERC-3643 takes a fundamentally different approach — moving compliance from an off-chain signing key to an on-chain identity registry that cannot be compromised or go offline.

How Does ERC-3643 T-REX Build Identity-Centric Compliance Natively Into Every Token Transfer?

ERC-3643, finalized in 2021 and officially merged into the Ethereum master GitHub as the first permissioned token standard, extends ERC-20 with an on-chain identity registry that validates sender and receiver eligibility before every transfer. Every ERC-3643 token is ERC-20 compatible — wallets, exchanges, and DeFi protocols handle it natively — while compliance enforcement runs autonomously at the contract layer.

ERC-3643 Identity-Centric Model — On-Chain Registry, Wallet Whitelisting, and Transfer Validation

ERC-3643 moves compliance from a token-centric model — where the token contract itself enforces rules — to an identity-centric model — where a separate, persistent on-chain identity registry stores verified credentials for every eligible wallet. When a transfer is initiated, the token contract queries the identity registry to confirm both the sender and receiver hold valid, unexpired claims — such as KYC-verified, accredited investor, or jurisdiction-eligible. If either wallet lacks the required claims, the transfer reverts automatically with no human intervention required. The identity registry is reusable: once a wallet is verified, that credential applies across all ERC-3643 tokens issued by any issuer using the same registry — eliminating per-issuance KYC onboarding. Tokeny, which developed ERC-3643, reports the standard now governs $32B+ in tokenized assets (rwa.xyz; Finextra, 2026) across 180+ jurisdictions.

ERC-3643 vs ERC-1400 — Gas Efficiency, DeFi Composability, and $32B+ Live Proof

The advantages of ERC-3643 over ERC-1400 are architectural. ERC-3643 tokens are ERC-20 compatible by design — Securitize, Ondo, and Centrifuge all issue ERC-3643 tokens that route through standard DeFi infrastructure — tokenized assets can serve as collateral in lending protocols without custom adapters. Gas costs per transfer are lower than ERC-1400 because the identity registry lookup replaces the certificate generation and verification cycle. Chainlink secured $3B in new real-world asset (RWA) oracle contracts by March 2026, providing net asset value (NAV), assets under management (AUM), and yield data feeds for ERC-3643 tokenized assets across BlackRock, Ondo, and UBS deployments (coinreporter.io, 2026-03). ISO standardization of ERC-3643 is in progress — once complete, it will provide the first internationally recognized compliance framework for blockchain-native securities.

With both compliance architectures mapped, a direct comparison across all five standards reveals which dimensions separate institutional-grade from experimental-grade token infrastructure.

How Do ERC-20, ERC-721, ERC-1400, and ERC-3643 Compare Across Fungibility and Compliance?

The five standards occupy distinct positions when measured across fungibility, transfer restrictions, on-chain compliance, ERC-20 wallet compatibility, and institutional endorsement. ERC-3643 is the only standard that scores positively on all five dimensions — which explains why it commands $32B+ in institutional tokenization while ERC-1400 remains a niche choice for complex cap table structures.

Fungibility, Compliance Architecture, and Wallet Compatibility Across All Five Standards

ERC-20 and ERC-3643 are the only fully ERC-20-compatible standards — both interoperate with any Ethereum wallet, decentralized exchange, or DeFi protocol without custom adapters. ERC-721 and ERC-1155 are partially compatible: they implement transfer functions but not the full approve-allowance interface DeFi protocols require. ERC-1400 is the outlier: its partition functions and certificate verification sit outside the ERC-20 interface — it is fundamentally incompatible with standard DeFi infrastructure. On compliance, ERC-20, ERC-721, and ERC-1155 carry none; ERC-1400 enforces compliance off-chain through a signing key; ERC-3643 enforces compliance on-chain through a persistent identity registry. The gap between off-chain and on-chain enforcement is not cosmetic — it determines whether compliance can fail silently when the signing key is unavailable.

ISO Status, Regulatory Endorsements, and Live Deployment Scale Compared

ERC-3643 is the only token standard undergoing International Organization for Standardization (ISO) certification as of May 2026. It has received endorsements from the U.S. Securities and Exchange Commission (SEC), the Depository Trust and Clearing Corporation (DTCC), and Singapore's Monetary Authority of Singapore (MAS) Project Guardian. No equivalent endorsements exist for ERC-1400. At deployment scale, Securitize ($4B+ AUM), Ondo Finance ($2.5B total value locked (TVL)), and Centrifuge ($1.6B TVL) all operate on ERC-3643. Polymath and Taurus serve institutional clients with ERC-1400, primarily for corporate securities where partition-level vesting schedules are the primary requirement — a use case ERC-3643 can also address through its modular claims architecture.

Data current as of May 2026.

Knowing how standards compare is necessary but insufficient — the operative question is which standard a project should deploy for a specific asset class and regulatory environment.

Which Token Standard Should a Project Choose for Equity, Debt, Real Estate, or Collectibles?

Standard selection is an architectural decision that preconditions every subsequent compliance, liquidity, and exit option available to a token project. Deploying across the asset-to-standard boundary creates legal and operational costs that exceed the cost of choosing correctly at the outset.

Token Standard Selection by Asset Type — Equity, Debt, Real Estate, Collectibles, Gaming

Fungible, regulated financial assets — equities, bonds, real estate fund units, revenue-sharing certificates — map to ERC-3643 in every current institutional deployment. ERC-3643's on-chain KYC enforcement, ERC-20 composability, and ISO track record make it the default for any asset subject to securities law across MiCA, SEC Regulation D, or MAS frameworks. Unique assets with no securities exposure — art, music rights, event tickets, gaming items with transferable provenance — map to ERC-721 or ERC-1155 depending on whether batch efficiency matters. For DeFi-native fungible protocol tokens with no investor eligibility requirements, ERC-20 remains correct: it offers maximum composability with no compliance overhead that restricts holder access.

When ERC-1400 Wins — Complex Cap Tables and Partition-Level Vesting Schedules

ERC-1400 retains a narrow but legitimate use case: corporate securities where multiple token sub-classes with different rights must coexist within the same wallet address. An employee equity grant holds unvested and vested tokens that behave differently even though both reside in the same wallet — a requirement ERC-3643 can address through its claims architecture but that ERC-1400's partition system handles with less configuration overhead. Taurus deploys ERC-1400 for institutional clients managing structured corporate securities in Switzerland, where the primary requirement is partition-level enforcement of vesting schedules rather than cross-chain DeFi composability. For any project that also requires DeFi liquidity — using tokenized equity as collateral in a lending protocol — ERC-3643 is the only viable choice, as ERC-1400's DeFi incompatibility makes collateralization structurally impossible without a custom adapter.

Data current as of May 2026.

The theoretical selection framework is confirmed by how the three largest tokenization platforms have deployed these standards at scale.

How Are These Token Standards Used by Securitize, Ondo, Taurus, and Centrifuge Today?

Securitize, Ondo Finance, and Centrifuge collectively manage more than $7B in tokenized value and have all converged on ERC-3643 — for reasons that trace directly to its ERC-20 compatibility and on-chain compliance. Taurus and Polymath chose ERC-1400 for institutional clients where partition-level complexity outweighs DeFi composability.

Securitize, Ondo, and Centrifuge — ERC-3643 at $7B+ Institutional Scale

Securitize manages $4B+ in tokenized AUM as of Q1 2026, including BlackRock's BUIDL fund — the largest tokenized money market fund at $2.4B — deployed on ERC-3643 infrastructure. Securitize reported $19.5M in Q1 2026 revenue, its highest quarter to date. Ondo Finance reached $2.5B in TVL across tokenized stocks (Ondo Global Markets), OUSG (tokenized U.S. Treasury), and USDY (yield-bearing stablecoin) — all ERC-3643 tokens (as of May 2026) . Centrifuge reached $1.6B TVL after expanding to the Base chain, with its JAAA collateralized loan obligation (CLO) fund holding $653M on-chain (as of April 2026) . All three platforms cite ERC-3643's ERC-20 compatibility as the feature enabling their DeFi composability strategy.

Taurus and Polymath — ERC-1400 in Structured Securities and Corporate Cap Tables

Taurus Group, the Swiss digital asset infrastructure provider, deploys ERC-1400 through its Taurus-CAPITAL platform for institutional clients managing corporate securities on Ethereum. Its use targets the niche where ERC-1400 excels: complex corporate cap tables with differentiated vesting schedules, multiple share classes, and partition-level transfer restrictions within the same wallet address. Polymath, the ERC-1400 originator, operates the Polymesh blockchain — a purpose-built compliance chain where ERC-1400-derived logic runs at the chain level rather than the contract level. Neither Taurus nor Polymath positions their ERC-1400 deployments for DeFi composability; both serve regulated institutional markets where the primary constraint is cap table complexity rather than cross-protocol liquidity.

Data current as of May 2026.

The divergence between ERC-3643's dominance and ERC-1400's specialization will sharpen as cross-chain compliance bridges and ISO certification extend the compliance-native standard's reach.

How Will Token Standards Evolve as Cross-Chain Compliance and DeFi Composability Demands Grow?

The next phase of token standard evolution runs on two tracks: ERC-3643's progress toward ISO certification, and the development of cross-chain compliance bridges that preserve identity registry enforcement when assets move between Ethereum, Base, Polygon, and other networks.

Cross-Chain Portability and ERC-3643 ISO Standardization as the Compliance Frontier

ISO certification for ERC-3643 is in progress as of May 2026 — once finalized, it will make ERC-3643 the first token standard with an internationally recognized compliance designation, a prerequisite for adoption by sovereign wealth funds and pension managers operating under fiduciary mandates requiring regulator-recognized infrastructure. Cross-chain bridges compliant with ERC-3643's identity registry are in development across Ethereum Layer-2 networks — these bridges allow tokenized assets to move between chains without losing whitelist enforcement properties.

Composable RWA Tokens as DeFi Collateral in Lending and Money Markets

Approximately $400M of BlackRock's BUIDL AUM was deposited in DeFi protocols as collateral or yield-bearing reserves by 2026. This composability track — using ERC-3643 tokenized real-world assets as collateral in Aave, Morpho, or other permissioned lending pools — represents the convergence of regulated asset infrastructure and DeFi capital efficiency. As ISO certification reduces institutional onboarding friction, RWA collateral volume in DeFi money markets is positioned to grow substantially across 2026 and 2027.

FAQ

References / Sources