ERC standards are the application-layer specifications that define how smart contracts on Ethereum and EVM-compatible chains expose tokens, approvals, vaults, and cross-chain intents. Each standard is finalized through the Ethereum Request for Comments process, where authors propose an interface, the community reviews it, and clients implement support. A builder shipping a stablecoin payment app, an NFT marketplace, a yield vault, or a cross-chain router pulls from this catalog rather than designing token plumbing from scratch.
​

This article maps the ERC standards that matter for production teams in 2026: the foundational token standards (ERC-20, ERC-721, ERC-1155), the approval-and-permit standards (ERC-2612, ERC-3009, Permit2), the vault and account standards (ERC-4626, ERC-4337), and the cross-chain standards that emerged in 2024 and 2025 (ERC-7683, ERC-7802, ERC-7811). Each section names the EIP, the mechanism, and the production protocols that depend on it.
​

An ERC (Ethereum Request for Comments) is a category of Ethereum Improvement Proposal that defines application-layer interfaces, conventions, and contracts. ERCs are distinct from "core" EIPs (which change consensus rules) and "networking" EIPs (which change client behavior). When a contract claims to be ERC-20-compliant, it implements the function signatures specified in EIP-20, allowing wallets, indexers, and DeFi protocols to interact with it without bespoke integration.
​

The ERC catalog has grown from ERC-20 in 2015 to over 200 finalized standards by April 2026, with another 100+ in draft. The Ethereum Foundation tracks status on eips.ethereum.org. Standards graduate through Draft, Review, Last Call, and Final. Once Final, the spec is frozen and clients can implement against a stable interface. ERC-20 alone underpins more than $230 billion in stablecoin supply across networks, per DeFiLlama stablecoin data (April 2026).
​

An ERC begins as a pull request to the ethereum/EIPs GitHub repository. Authors specify the motivation, interface, behavior, and reference implementation. Editors check formatting, then the proposal moves to Draft. Discussion happens on Ethereum Magicians, where wallet teams, exchange engineers, and protocol authors push back on edge cases. Once consensus stabilizes, the proposal moves to Review, then Last Call (a fixed comment window), then Final.
​

Adoption is separate from finalization. ERC-721 was Final in January 2018 but did not become economically meaningful until late 2020 when CryptoKitties, OpenSea, and the broader NFT market scaled it past $20 billion in monthly volume by January 2022, per Dune analytics on NFT trade volume. ERC-4337 (account abstraction) was Final in March 2023 but took eighteen months for major wallets like Coinbase Smart Wallet and MetaMask to ship production support. ERC-7683 (cross-chain intents) is in Final but adoption is still ramping across solver networks like Across, Eco, and LI.FI as of April 2026.
​

The token-standards family covers fungible tokens, non-fungible tokens, and multi-token contracts. These are the most-used ERCs by deployment count and remain the load-bearing primitives every other standard composes against.
​

ERC-20 defines the interface for fungible tokens: totalSupply, balanceOf, transfer, approve, transferFrom, and the Transfer and Approval events. Every major stablecoin (USDC, USDT, DAI, PYUSD, FDUSD, RLUSD, USDS) is an ERC-20 contract on at least one chain. The standard's simplicity is also its weakness: approve requires a separate transaction before any third-party transfer, creating a two-transaction UX that ERC-2612 and Permit2 later addressed.
​

ERC-721 defines unique tokens with per-token ownerOf lookups and tokenURI metadata. Marketplaces like OpenSea, Blur, and Magic Eden index ERC-721 collections by listening to Transfer events. The standard is gas-heavy for batch operations because each token write costs a separate storage slot — a problem ERC-1155 solves for game and edition use cases.
​

ERC-1155 lets a single contract manage many token IDs, each with its own supply (fungible, non-fungible, or semi-fungible). Authored by Enjin in 2018, the standard cuts gas by ~60% on batch transfers compared to one-call-per-ERC-721. Open-edition NFT drops, in-game item systems, and tokenized receipts use ERC-1155. Read the ERC-1155 multi-token standard breakdown for when to choose it over ERC-721.
​

The approve + transferFrom pattern in ERC-20 forces users to send two transactions to spend a token through a third-party contract. The permit family removes the first transaction by letting users sign an off-chain approval message that any caller can submit on-chain.
​

ERC-2612 adds a permit function that accepts an EIP-712 signed message and sets the allowance in a single transaction. DAI ships with native permit. USDC supports it on most chains. Compound, Aave, and Uniswap v3 routers consume permits to compress two-transaction flows into one. See the Permit1 deep dive for the EIP-712 mechanics.
​

ERC-3009 defines transferWithAuthorization and receiveWithAuthorization for stablecoin issuers. Signed messages carry a recipient, amount, validity window, and nonce. Circle's USDC, Paxos's USDP, and PYUSD implement ERC-3009 alongside ERC-2612 because the authorization model fits payment use cases (one-time, time-bounded, recipient-scoped) better than allowance-based permits.
​

Permit2 is not an EIP but a Uniswap-published contract that wraps any ERC-20 with permit-like signatures. Deployed at 0x000000000022D473030F116dDEE9F6B43aC78BA3 on most EVM chains, Permit2 replaced per-token permit support with a single approval to the Permit2 contract, then signed authorizations per spend. Uniswap Universal Router, 1inch Fusion, and CoW Swap route approvals through Permit2 to deduplicate the per-token allowance state.
​

Where token standards define what assets are, vault and account standards define what holds them. Two standards dominate this category in 2026: ERC-4626 for yield-bearing vaults and ERC-4337 for smart-contract wallets.
​

ERC-4626 standardizes deposit, withdraw, mint, and redeem on a vault that returns a share token. Aave's aTokens, Yearn v3 vaults, Morpho Blue markets, and Pendle's principal tokens implement ERC-4626. The standard makes one vault interchangeable with another from an integrator's view: a treasury app deposits USDC into Aave or Morpho with the same contract calls. Read the ERC-4626 vault standard explainer for the share-pricing math.
​

ERC-4337 introduced UserOperations, bundlers, paymasters, and EntryPoint without requiring an Ethereum protocol change. It moved smart-contract wallets from theory to production. Coinbase Smart Wallet, Safe, Biconomy, and Alchemy's Account Kit all build on ERC-4337. The standard reached more than 50 million UserOperations across chains by April 2026, per BundleBear analytics.
​

Cross-chain coordination is the newest standards frontier. Three ERCs published in 2024 attempt to standardize parts of the multi-chain stack: ERC-7683 for intents, ERC-7802 for token bridging, and ERC-7811 for wallet asset discovery.
​

ERC-7683 defines GaslessCrossChainOrder and OnchainCrossChainOrder: structured intents that solvers can fill across chains. Authored by Across and Uniswap Labs, ERC-7683 lets a user sign a single intent ("send 1000 USDC from Arbitrum to Base") that any of N solvers can execute. Across, Eco, and LI.FI support ERC-7683 intents. Read the ERC-7683 intents deep dive for the order struct and settlement flow.
​

ERC-7802 standardizes crosschainMint and crosschainBurn for tokens that exist natively on multiple chains. Optimism's SuperchainERC20 implements ERC-7802 to coordinate canonical token supply across the OP Superchain. See the ERC-7802 cross-chain token standard breakdown.
​

ERC-7811 lets dApps query a wallet for its asset positions across chains via a structured RPC method. Without it, every dApp re-implements multi-chain balance fetching against block explorers and aggregators. See the ERC-7811 wallet asset discovery deep dive.
​

The right standard depends on the asset class and use case. The decision matrix below maps common builder questions to their canonical standards.

The standards compose. A stablecoin issuer typically ships ERC-20 + ERC-2612 + ERC-3009. A vault product implementing ERC-4626 also exposes the underlying ERC-20 share tokens. A cross-chain router using ERC-7683 reads ERC-20 token addresses across chains and may interoperate with ERC-7802 tokens.
​

Production stablecoin teams build above the ERC catalog rather than around it. Eco's stablecoin orchestration network treats ERC-7683 intents, ERC-2612 permits, ERC-3009 authorizations, and ERC-7802 native cross-chain tokens as input formats: a user signs the standardized message, Eco's solver network selects a route across CCTP, Hyperlane, or LayerZero, and settlement happens on the destination chain. The orchestration sits one layer above the standards — the standards define the message shape, and the orchestrator handles solver selection, liquidity, and finality. Read the stablecoin automation platforms overview for how orchestration platforms compose ERC primitives.
​

An EIP is the umbrella term for any Ethereum Improvement Proposal. ERCs are a category of EIP that specifies application-layer interfaces (tokens, contracts, conventions). Core EIPs change consensus rules. Networking EIPs change client behavior. ERCs leave protocol rules untouched and define what contracts should look like.
​

Most stablecoin issuers implement ERC-20 plus ERC-2612 (permit) and ERC-3009 (authorization transfer). USDC adds ERC-3009 for payment use cases. DAI ships native ERC-2612 permit. PYUSD implements both. Cross-chain native tokens adopting the OP Superchain or Optimism's SuperchainERC20 also implement ERC-7802.
​

No. ERC standards specify interface contracts that auditors and integrators check against. Nothing in the EVM rejects a non-compliant contract. Wallets and protocols decide which standards to support; non-compliant tokens still deploy but lose access to wallet UI and DeFi integrations that gate on standard interfaces.
​

The gap between Final status and meaningful adoption ranges from months to years. ERC-20 took two years from publication to the 2017 ICO boom that made it ubiquitous. ERC-4337 took eighteen months from Final to mainstream wallet integration. ERC-7683 reached Final in late 2024 and adoption is still ramping across Across, Eco, and LI.FI in 2026.
​

New ERCs are proposed as pull requests to the ethereum/ERCs GitHub repository. Discussion happens on Ethereum Magicians. The Ethereum Foundation publishes finalized standards at eips.ethereum.org/erc.
​