EIP-4 EIP Classification Scheme (EIP Classification)
Final · Other · EIP status Final · created 2015-11-17
A meta document defining the classification criteria that divide Standards EIPs into four layers: Consensus, Networking, API/RPC, and Applications. It adapts Bitcoin's BIP 123 for Ethereum.
Why it is needed
Ethereum is a system in which multiple standards move together. Some standards must be followed by every participant for the network to remain interoperable, while others are optional, where implementers can choose whether to support them. However, it was hard to distinguish the two from the proposal alone. Standards that touch lower layers of the system face far greater difficulty being accepted and deployed. So a classification scheme was needed that sorts EIPs by their interoperability requirement, meaning the degree to which different pieces of software must be compatible. This document defines those layers and provides criteria for judging which layer a Standards EIP belongs to.
What changes
Today
- Standards EIPs are handled as one undifferentiated group without layer distinctions
- It is hard to tell which proposals are essential for network compatibility and which are optional
After EIP-4
- Standards EIPs are placed into one of four layers: Consensus, Networking, API/RPC, or Applications
- The classification reveals that lower-numbered layers carry stricter interoperability requirements
- Consensus layer changes are further split into soft forks and hard forks
Who is affected
- EIP authors: Disclosing which layer a proposal belongs to can show in advance the scope of impact and the difficulty of reaching consensus on the change.
- Client teams: Standards that must be implemented and standards that may be optionally supported can be distinguished by layer.
- Wallet & app developers: If a standard you depend on is at the API/RPC or Applications layer, you can keep in mind that competing standards may coexist.
In depth
Origin and Principles of the Classification
This scheme adapts Bitcoin's BIP 123 for Ethereum. It divides Standards EIPs by system layer, with the principle that lower-numbered layers carry more complex interoperability requirements. Since standards at lower layers face much higher difficulty being accepted and deployed, the goal is to classify them in a way that reflects this reality in the EIP process.
Four Layers
A Standards EIP is placed into one of four layers: 1. Consensus, 2. Networking, 3. API/RPC, and 4. Applications. The consensus layer is the lowest and the applications layer is the highest. The document provides a definition for each layer along with criteria for judging which layer a given Standards EIP belongs to.
Consensus Layer: Soft Forks and Hard Forks
The consensus layer defines the cryptographic commitment structure. Its purpose is to let anyone locally verify whether a given state and history are valid, and to guarantee settlement assurances and finality convergence. It does not address how messages propagate across the network. A disagreement at this layer causes the network to split, with different nodes accepting mutually incompatible histories. Changes are divided into two kinds. A soft fork is a change in which some structures valid under the old rules become invalid under the new rules; structures invalid under the old rules remain invalid under the new rules. A hard fork is a change in which structures invalid under the old rules become valid under the new rules.
Networking Layer
The networking layer specifies the Ethereum Wire Protocol (eth) and the Light Ethereum Subprotocol (les). RLPx is excluded from this and is maintained separately in the devp2p repository. Basic node interoperability only requires part of the subprotocol, and nodes may additionally support optional extensions on top of it. New subprotocols can be added at any time without breaking compatibility with existing protocols, and older protocols can then be phased out gradually. This approach allows the entire network to be upgraded without serious risk of service disruption.
API/RPC Layer
The API/RPC layer specifies the high-level calls accessible to applications. EIPs in this layer are not required for basic network interoperability, but some client applications may be expected to support them. This is a layer where competing standards can coexist without breaking basic network compatibility.
The Applications Layer and Document Status
The applications layer specifies high-level structures, abstractions, and conventions that let different applications support similar functionality and share data. This document itself has type Meta and status Final, meaning it is not a proposal to change protocol code but a rules document governing the EIP process.