Ethereum's design surface — what contracts can do, how transactions are priced, how accounts behave, how cross-chain coordination happens — is defined by a few dozen EIPs that ship as Final and the broader pool of ERCs that win adoption. For developers, knowing which EIPs matter saves time on integrations and avoids reinventing patterns the protocol already standardizes.
This list covers the ten EIPs and ERCs that have the broadest impact on production smart contract and infrastructure development as of 2026. Each entry includes the full title, author, status, and the practical reason it matters for builders working on tokens, accounts, fees, signing, or cross-chain transfers.
Why These Ten?
The selection criteria are pragmatic: each EIP either powers a category developers integrate daily (token standards, signing, account abstraction) or has reset the cost or capability floor for an entire layer of the stack (fee markets, blob data, cross-chain intents). Less-cited but newer proposals are included where they are already in production or scheduled for an upcoming fork.
The list excludes purely-meta EIPs (process documents) and consensus-layer changes (validator economics, client networking) because those mostly affect protocol researchers and node operators rather than application developers.
1. ERC-20: Fungible Token Standard
ERC-20 defines the interface for fungible tokens on Ethereum. Authored by Fabian Vogelsteller and Vitalik Buterin in November 2015 and finalized as EIP-20, the standard specifies six required functions including transfer, balanceOf, approve, and transferFrom.
Every major stablecoin — USDC, USDT, DAI, PYUSD, RLUSD, USDe — implements ERC-20. Wrapped assets like WBTC, liquid staking tokens like stETH, and governance tokens like UNI all use the same interface. The standard's longevity comes from doing less, not more — wallets and exchanges only need to call balanceOf and transfer to handle most user flows.
Status: Final. Adopted by virtually every fungible token deployed since 2017. Total ERC-20 contract count exceeds 1.5 million on mainnet alone according to Etherscan's token tracker.
2. ERC-721: Non-Fungible Token Standard
ERC-721 defines the interface for unique tokens, where each token has a distinct ID. Authored by William Entriken, Dieter Shirley, Jacob Evans, and Nastassia Sachs in January 2018, the specification on eips.ethereum.org defines functions like ownerOf and tokenURI that wallets and marketplaces rely on to display NFTs.
The standard launched the NFT category and remains the dominant interface for digital collectibles, profile-picture projects, and onchain identity. Use beyond art has expanded — Uniswap v3 represents liquidity positions as ERC-721s, and several real-world asset platforms tokenize ownership claims as ERC-721s.
Status: Final. Universally adopted for unique-token use cases.
3. ERC-1155: Multi-Token Standard
ERC-1155 lets a single contract manage fungible, non-fungible, and semi-fungible tokens. Authored by Witek Radomski and the Enjin team and finalized in June 2018 as EIP-1155, the standard reduces deployment overhead for use cases — like onchain games — that need many distinct token types.
The batched safeBatchTransferFrom function lets users transfer multiple token IDs in one transaction, which is significantly cheaper than equivalent ERC-721 transfers. OpenSea, Magic Eden, and most NFT marketplaces support ERC-1155 alongside ERC-721.
Status: Final. Heavily used in gaming and any context where deploying separate contracts per token type is wasteful.
4. EIP-1559: Fee Market Reform
EIP-1559 replaced first-price gas auctions with a protocol-set base fee plus an optional priority fee. Authored by Vitalik Buterin, Eric Conner, Rick Dudley, Matthew Slipper, Ian Norden, and Abdelhamid Bakhta and activated August 5, 2021 with the London hard fork, the specification made next-block fees estimable and shifted ETH supply mechanics by burning the base fee.
Cumulative ETH burn from EIP-1559 exceeds 4.6 million ETH as tracked by ultrasound.money. The same fee mechanism has been adopted by most EVM-compatible L2s (Arbitrum, Optimism, Base, Polygon zkEVM), which is why cross-chain quote engines can apply consistent fee logic.
Status: Final. Live since August 2021.
5. EIP-712: Typed Structured Data Signing
EIP-712 standardizes how Ethereum apps request signatures over structured data. Authored by Remco Bloemen, Leonid Logvinov, and Jacob Evans and finalized in September 2017, the EIP-712 specification defines a hashing scheme that makes signed payloads readable in wallets ("approve 100 USDC for Uniswap" instead of an opaque hex blob).
EIP-712 is the foundation of gasless approvals (EIP-2612 permits), order books (Seaport, Reservoir, 0x), session keys for smart wallets, and intent-based routing. Most cross-chain stablecoin orchestration platforms — including LI.FI, Across, and Eco — use EIP-712 typed-data for user-signed intents.
Status: Final. Universally adopted by signing-heavy apps.
6. EIP-4844: Proto-Danksharding (Blob Transactions)
EIP-4844 introduced blob-carrying transactions to Ethereum. Authored by Vitalik Buterin, Dankrad Feist, Diederik Loerakker, George Kadianakis, Matt Garnett, Mofi Taiwo, and Ansgar Dietrichs and activated March 13, 2024 with the Dencun hard fork, the specification defines a new transaction type with separate fee market.
The cost effect on Layer 2s was immediate. Median L2 fees on Arbitrum, Optimism, Base, and Linea fell roughly 90% within the first week, expanding the addressable market for stablecoin transfers and onchain consumer apps. L2fees.info tracks per-rollup costs.
Status: Final. Active since March 2024.
7. ERC-4337: Account Abstraction (Smart Accounts)
ERC-4337 brings smart-account features — batched transactions, gas sponsorship, session keys, recovery — without requiring a hard fork. Authored by Vitalik Buterin, Yoav Weiss, Dror Tirosh, Shahaf Nacson, and Alex Forshtat and finalized March 2023, the EIP-4337 specification introduces UserOperations, bundlers, paymasters, and an EntryPoint contract.
The standard is live on every EVM chain because it requires no consensus changes. Cumulative UserOperation count exceeded 50 million by mid-2025, with daily volume tracked on BundleBear. Production wallet stacks include Safe, Biconomy, ZeroDev, and Alchemy.
Status: Final. Live on mainnet since March 2023.
8. EIP-7702: EOA-to-Smart-Account Delegation
EIP-7702 lets externally owned accounts temporarily delegate execution to a smart contract, bringing smart-wallet features to existing EOAs without forcing migration. Authored by Vitalik Buterin, Sam Wilson, Ansgar Dietrichs, and Matt Garnett and activated May 7, 2025 with the Pectra hard fork, the specification introduces Type 4 transactions with authorization lists.
EIP-7702 replaced an earlier proposal, ERC-3074, that gave too much power to a single trusted contract. The new design distributes trust by letting users sign delegations to any contract they choose. Adoption since Pectra has been driven by gas-sponsored onboarding and batched approval flows.
Status: Final. Active since May 2025.
9. ERC-4626: Tokenized Vault Standard
ERC-4626 standardizes the interface for tokenized yield vaults. Authored by Joey Santoro, t11s, Jet Jadeja, Alberto Cuesta Cañada, and Mikhail Vladimirov and finalized April 2022, the EIP-4626 specification defines functions like deposit, withdraw, convertToShares, and convertToAssets.
Adoption has been rapid. Yearn, Morpho, Spark, Pendle, and most ERC-20 yield protocols deployed since 2022 implement ERC-4626. The standard means an integrator can build one adapter and connect to any compatible vault, which is why aggregators like DefiLlama can list vault yields without protocol-specific connectors.
Status: Final. The default vault interface for new yield protocols since 2022.
10. ERC-7683: Cross-Chain Intents
ERC-7683 defines a shared format for cross-chain intents that any compatible solver can fill. Authored by Mark Toda, Matt Rice, Hart Lambur, and Xinyuan Sun and published July 2024, the specification introduces a GaslessCrossChainOrder struct that orchestrators across systems can interpret.
The motivation is fragmentation. Pre-7683, each cross-chain platform — LI.FI, Across, Wormhole, Hyperlane, LayerZero — had its own intent format. Solvers had to integrate with each one separately. ERC-7683 lets a solver fill orders from any compatible system using one integration.
Status: Final. Adoption growing across cross-chain platforms since late 2024. Eco's intent routing supports ERC-7683 orders alongside its native format.
How These EIPs Compose
The ten standards above stack into a coherent developer experience. A modern stablecoin payment flow on Ethereum touches at least five of them in a single transaction:
ERC-20 (USDC) — the asset being transferred.
EIP-1559 — the gas market for the transaction.
EIP-712 — the typed-data signature for the user's intent.
ERC-4337 or EIP-7702 — the account abstraction path enabling gas sponsorship.
ERC-7683 — the cross-chain intent format if the destination is on a different chain.
For developers building on top of this stack, the practical implication is that each integration is opt-in. ERC-20 is foundational; everything else can be added or skipped depending on the use case. A pure single-chain DEX needs only ERC-20 and EIP-712. A cross-chain stablecoin payment platform needs all five.
How Eco Uses These Standards
Eco's stablecoin orchestration network spans 15 chains and integrates most of the standards above as primitives. ERC-20 is the asset layer. EIP-712 is the signing scheme for intents. ERC-4337 and EIP-7702 are both supported as account-abstraction paths, which lets users with either smart accounts or existing EOAs participate in the same routing flow. ERC-7683 cross-chain intents are evaluated for solver interoperability with other orchestrators.
For developers integrating Eco into stablecoin swap aggregators, B2B payout APIs, or deposit automation tools, the standards in this list cover most of the integration surface. Tracking which EIPs are scheduled for the next hard fork — particularly proposals around blob throughput, account abstraction, and cross-chain coordination — is part of how cross-chain platforms anticipate future capability and cost shifts.
FAQ
Why aren't EIP-2612 (permits) or EIP-2930 (access lists) in this list?
Both are useful but more specialized. EIP-2612 is a strong candidate — it standardizes gasless approvals for ERC-20 tokens — but adoption is uneven across stablecoins. EIP-2930 access lists are mostly used by sophisticated MEV-aware applications. The list above covers standards with broad applicability across most stablecoin and cross-chain use cases.
What about EIP-3074?
ERC-3074 was an earlier account-abstraction proposal that the community rejected in mid-2024 in favor of EIP-7702. It never reached Final on mainnet. The decision came from concerns about giving too much power to a single trusted invoker contract. EIP-7702 took its place by distributing trust across user-signed authorizations.
Are there standards specific to Layer 2s I should know?
L2s generally inherit Ethereum's EIPs and ERCs. Most rollups implement EIP-1559 fee markets with rollup-specific parameters and support EIP-712 signing without modification. ERC-4337 deployed on every L2 in 2023. EIP-7702 is rolling out across rollups in 2025. Few L2s have their own application-level standards distinct from Ethereum's.
How do I track new EIPs that might join this list?
The ethereum/EIPs repository and the EIP index are the primary sources. EIPs Insight tracks status counts and recent activity. For Core EIPs scheduled into upcoming forks, the ethereum/pm GitHub repository publishes ACD agendas.
Which EIP should I learn first?
Start with ERC-20 if you're building anything involving tokens. Move to EIP-712 next — it underlies most signing patterns in modern apps. After those, ERC-4337 and EIP-7702 cover account abstraction, EIP-1559 covers gas, and EIP-4844 covers L2 economics. ERC-7683 is the most relevant for cross-chain work.

