5/5
## EIPs vs. ERCs: Understanding Ethereum's Core Standards In the Ethereum ecosystem, you'll frequently encounter the acronyms EIP and ERC. While they sound similar, they represent two fundamental concepts that govern how the network evolves and how applications interact within it. This lesson will demystify these terms, explaining their distinct roles, the crucial relationship between them, and why they are the cornerstones of Ethereum's decentralized development. ### What is an Ethereum Improvement Proposal (EIP)? An **EIP**, or **Ethereum Improvement Proposal**, is a formal design document that proposes a new feature, process, or standard for the Ethereum network. It is the primary mechanism through which anyone can suggest improvements or changes to Ethereum's core protocol, client APIs, or contract standards. Think of an EIP as a detailed blueprint for a potential upgrade. This process is open and decentralized; anyone in the community, from core developers to researchers and even informed users, can write and submit an EIP for consideration. #### The EIP Lifecycle For an idea to become an official standard, it must pass through a rigorous, multi-stage review process to ensure its technical soundness, security, and benefit to the network. 1. **Drafted:** An author formalizes their idea into a detailed proposal, outlining the technical specifications and the rationale behind the change. This draft is then submitted to the community. 2. **In Review:** The wider Ethereum community scrutinizes the proposal. Developers, researchers, and other stakeholders assess its feasibility, security implications, and whether it could potentially break existing applications (backwards compatibility). 3. **Last Call:** If the EIP gains significant community support and passes the initial review, it enters a final review period. This is the last opportunity for anyone to raise critical concerns before the proposal is finalized. 4. **Final:** Once all concerns are addressed and the proposal is approved, the EIP becomes an official standard. For **Core EIPs**—those that change the protocol itself—this status is typically achieved when the change is implemented on the Ethereum mainnet, often as part of a major network upgrade (also known as a hard fork). #### Types of EIPs EIPs are categorized based on the area of the network they aim to change: * **Core:** Proposes changes to the core consensus protocol that require a network-wide upgrade (e.g., modifications to gas fee calculations). * **Networking:** Suggests improvements to how network nodes communicate, such as the peer-to-peer protocol. * **Interface:** Defines standards for client APIs and other interfaces, ensuring applications can reliably interact with Ethereum clients. * **ERC:** Proposes application-level standards and conventions. This is a special subcategory that we will explore next. * **Meta:** A proposal about the EIP process itself or changes to its structure. * **Informational:** Provides general guidelines or information to the community but does not propose a network change. You can explore all official proposals at the EIP repository: **eips.ethereum.org**. ### What is an Ethereum Request for Comment (ERC)? An **ERC**, or **Ethereum Request for Comment**, is a specific type of EIP that focuses on creating standards at the application layer. Its primary goal is to ensure that different applications, tokens, and smart contracts built on Ethereum can interact with each other seamlessly. The relationship is simple: **all ERCs are EIPs, but not all EIPs are ERCs**. This is like saying all squares are rectangles, but not all rectangles are squares. ERCs are a specialized subset of EIPs dedicated to application-level functionality. #### The Importance of ERC Standards for Interoperability Without standards, the blockchain world would be chaotic. ERCs provide a common framework that enables the composability and interoperability that make the Ethereum ecosystem so powerful. * **Wallets:** How can your MetaMask wallet display the balance of thousands of different tokens? Because they all follow a common standard like **ERC-20**. The wallet knows exactly how to query the token's contract for your balance. * **Decentralized Exchanges (DEXs):** How can a DEX like Uniswap allow you to trade any token for another? Because all fungible tokens are built to the ERC-20 standard, the exchange's smart contracts know how to handle them. * **NFT Marketplaces:** How can OpenSea display NFTs from thousands of different collections? Because they all adhere to a common NFT standard like **ERC-721**, the marketplace knows how to interpret their metadata and ownership data. #### Key ERC Examples Several ERCs have become foundational to the web3 landscape: * **ERC-20:** The universal standard for **fungible tokens**. These are interchangeable tokens, like USDC or SHIB. * **ERC-721:** The original standard for **non-fungible tokens (NFTs)**. Each token is unique and represents ownership of a specific digital or physical asset. * **ERC-1155:** A **multi-token standard** that allows a single smart contract to manage both fungible and non-fungible tokens, optimizing efficiency. * **ERC-165:** A standard for **interface detection**. It allows a smart contract to announce which ERC standards it supports, so other applications know how to interact with it correctly. * **ERC-4626:** The **tokenized vault standard**. It standardizes how yield-bearing vaults work in DeFi, making them much more composable and easier for aggregators to integrate. * **ERC-712:** A standard for **structured data signing**. It improves security and user experience by making messages signed by a wallet human-readable, preventing phishing and replay attacks. ### Conclusion EIPs are the engine of Ethereum's evolution, providing a formal, community-driven process for upgrading the core network. ERCs are a vital subset of EIPs that create the rules for application-level interactions, fostering the interoperability that allows the ecosystem to thrive. This decentralized approach ensures that anyone with a good idea can contribute to building a better Ethereum. In our next lesson, we will dive deep into one of the most impactful Core EIPs ever implemented: **EIP-1559**, which fundamentally changed how gas fees are calculated on the Ethereum network.
In the Ethereum ecosystem, you'll frequently encounter the acronyms EIP and ERC. While they sound similar, they represent two fundamental concepts that govern how the network evolves and how applications interact within it. This lesson will demystify these terms, explaining their distinct roles, the crucial relationship between them, and why they are the cornerstones of Ethereum's decentralized development.
An EIP, or Ethereum Improvement Proposal, is a formal design document that proposes a new feature, process, or standard for the Ethereum network. It is the primary mechanism through which anyone can suggest improvements or changes to Ethereum's core protocol, client APIs, or contract standards. Think of an EIP as a detailed blueprint for a potential upgrade.
This process is open and decentralized; anyone in the community, from core developers to researchers and even informed users, can write and submit an EIP for consideration.
For an idea to become an official standard, it must pass through a rigorous, multi-stage review process to ensure its technical soundness, security, and benefit to the network.
Drafted: An author formalizes their idea into a detailed proposal, outlining the technical specifications and the rationale behind the change. This draft is then submitted to the community.
In Review: The wider Ethereum community scrutinizes the proposal. Developers, researchers, and other stakeholders assess its feasibility, security implications, and whether it could potentially break existing applications (backwards compatibility).
Last Call: If the EIP gains significant community support and passes the initial review, it enters a final review period. This is the last opportunity for anyone to raise critical concerns before the proposal is finalized.
Final: Once all concerns are addressed and the proposal is approved, the EIP becomes an official standard. For Core EIPs—those that change the protocol itself—this status is typically achieved when the change is implemented on the Ethereum mainnet, often as part of a major network upgrade (also known as a hard fork).
EIPs are categorized based on the area of the network they aim to change:
Core: Proposes changes to the core consensus protocol that require a network-wide upgrade (e.g., modifications to gas fee calculations).
Networking: Suggests improvements to how network nodes communicate, such as the peer-to-peer protocol.
Interface: Defines standards for client APIs and other interfaces, ensuring applications can reliably interact with Ethereum clients.
ERC: Proposes application-level standards and conventions. This is a special subcategory that we will explore next.
Meta: A proposal about the EIP process itself or changes to its structure.
Informational: Provides general guidelines or information to the community but does not propose a network change.
You can explore all official proposals at the EIP repository: eips.ethereum.org.
An ERC, or Ethereum Request for Comment, is a specific type of EIP that focuses on creating standards at the application layer. Its primary goal is to ensure that different applications, tokens, and smart contracts built on Ethereum can interact with each other seamlessly.
The relationship is simple: all ERCs are EIPs, but not all EIPs are ERCs. This is like saying all squares are rectangles, but not all rectangles are squares. ERCs are a specialized subset of EIPs dedicated to application-level functionality.
Without standards, the blockchain world would be chaotic. ERCs provide a common framework that enables the composability and interoperability that make the Ethereum ecosystem so powerful.
Wallets: How can your MetaMask wallet display the balance of thousands of different tokens? Because they all follow a common standard like ERC-20. The wallet knows exactly how to query the token's contract for your balance.
Decentralized Exchanges (DEXs): How can a DEX like Uniswap allow you to trade any token for another? Because all fungible tokens are built to the ERC-20 standard, the exchange's smart contracts know how to handle them.
NFT Marketplaces: How can OpenSea display NFTs from thousands of different collections? Because they all adhere to a common NFT standard like ERC-721, the marketplace knows how to interpret their metadata and ownership data.
Several ERCs have become foundational to the web3 landscape:
ERC-20: The universal standard for fungible tokens. These are interchangeable tokens, like USDC or SHIB.
ERC-721: The original standard for non-fungible tokens (NFTs). Each token is unique and represents ownership of a specific digital or physical asset.
ERC-1155: A multi-token standard that allows a single smart contract to manage both fungible and non-fungible tokens, optimizing efficiency.
ERC-165: A standard for interface detection. It allows a smart contract to announce which ERC standards it supports, so other applications know how to interact with it correctly.
ERC-4626: The tokenized vault standard. It standardizes how yield-bearing vaults work in DeFi, making them much more composable and easier for aggregators to integrate.
ERC-712: A standard for structured data signing. It improves security and user experience by making messages signed by a wallet human-readable, preventing phishing and replay attacks.
EIPs are the engine of Ethereum's evolution, providing a formal, community-driven process for upgrading the core network. ERCs are a vital subset of EIPs that create the rules for application-level interactions, fostering the interoperability that allows the ecosystem to thrive. This decentralized approach ensures that anyone with a good idea can contribute to building a better Ethereum.
In our next lesson, we will dive deep into one of the most impactful Core EIPs ever implemented: EIP-1559, which fundamentally changed how gas fees are calculated on the Ethereum network.
An essential breakdown of EIPs vs. ERCs: Understanding Ethereum's Core Standards - This lesson distinguishes between EIPs, which propose core protocol upgrades, and ERCs, the subset of EIPs that create application-level standards. Discover how this dual system allows Ethereum to evolve securely while ensuring the interoperability that powers everything from NFTs to DeFi.
Previous lesson
Previous
Next lesson
Next
Give us feedback
Course Overview
About the course
What blockchains are and how they work
Key blockchain components: wallets, gas, nodes, consensus
How to send transactions
The role and risks of smart contracts
How blockchains scale with L2 rollups
Real-world use cases like DEXs, RWAs, stablecoins, and NFTs
Blockchain threats like MEV and Sybil attacks
The lifecycle of a blockchain transaction
Security researcher
$49,999 - $120,000 (avg. salary)
Web3 developer
$60,000 - $150,000 (avg. salary)
Smart Contract Engineer
$100,000 - $150,000 (avg. salary)
Smart Contract Auditor
$100,000 - $200,000 (avg. salary)
Web3 Developer Relations
$85,000 - $125,000 (avg. salary)
Last updated on October 17, 2025
Duration: 20min
Duration: 1h 16min
Duration: 50min
Duration: 2h 02min
Duration: 41min
Duration: 36min
Duration: 7min
Certification: Blockchain Basics
This proficiency exam is designed to confirm your understanding of all key concepts and learnings presented in the course material. You will have 45 minutes to answer 30 questions and score 18 to pass and earn a Certificate of Completion.
Course Overview
About the course
What blockchains are and how they work
Key blockchain components: wallets, gas, nodes, consensus
How to send transactions
The role and risks of smart contracts
How blockchains scale with L2 rollups
Real-world use cases like DEXs, RWAs, stablecoins, and NFTs
Blockchain threats like MEV and Sybil attacks
The lifecycle of a blockchain transaction
Security researcher
$49,999 - $120,000 (avg. salary)
Web3 developer
$60,000 - $150,000 (avg. salary)
Smart Contract Engineer
$100,000 - $150,000 (avg. salary)
Smart Contract Auditor
$100,000 - $200,000 (avg. salary)
Web3 Developer Relations
$85,000 - $125,000 (avg. salary)
Last updated on October 17, 2025