EIP-7329 Splitting the EIP and ERC repositories (ERC/EIP Repository split)
Final · Other · EIP status Final · created 2023-07-13
A Meta proposal that moves application standards (ERCs) out of the EIP repository into a new repository, leaving only core protocol change proposals in the existing EIP repository.
Why it is needed
When the EIP repository was first created, the idea was to gather all Ethereum-related standards in one place. At the time the community was small and most participants were active in both protocol and application work, so combining the two felt natural. As the ecosystem grew, the distance between application development and core protocol development widened considerably, yet the repository remained a single one. The split became even more apparent once the consensus layer also began using the EIP process. Procedural changes that would help core development were hard to make because ERC quality control had to be handled at the same time, and while there were attempts on the ERC side to form working groups or review groups, such category distinctions did not even technically exist within the unified repository structure. The starting point of this proposal is that the two communities need separate repositories if they are to evolve their processes according to their own needs.
What changes
Today
- EIPs and ERCs follow the same process and the same editorial rules in a single repository
- Proposal numbers are determined by the number of the pull request (PR) that first introduced them
- Procedural changes suited to core development are hard to adopt because they are tied up with ERC quality control issues
After EIP-7329
- ERCs and EIPs in the Interface category are moved to a new ERC repository, leaving only core protocol proposals in the EIP repository
- Numbers are assigned by each repository's editors from a shared document, with EIPs receiving even numbers and ERCs odd numbers
- An ercs.ethereum.org subdomain is created, and existing ERC addresses on eips.ethereum.org redirect to the new site
Who is affected
- Smart contract, wallet, and app developers: ERCs such as token or wallet standards should be proposed in the new ERC repository. If one is mistakenly submitted to the existing EIP repository, an editor will direct it to the new repository.
- Core developers and client teams: The EIP repository becomes dedicated to core protocol changes discussed on AllCoreDevs calls, and procedural changes suited to core development can be adopted independent of ERC concerns.
- EIP and ERC editors: Each repository is split off to run its own process, with numbers assigned from a single shared document.
- Users of existing document links: Visiting an old address still works, since redirects send you to the new ERC site.
In depth
Division of scope between the two repositories
After the split, the EIP repository handles core protocol changes, that is, proposals of the kind discussed on AllCoreDevs calls. The ERC repository handles everything else that does not require core protocol changes, such as smart contract application interfaces, wallet standards, and DeFi protocol standards. This division holds even if editors later make procedural changes such as introducing working groups, topic groups, expert groups, or special interest groups. Any subgroup that involves core protocol changes belongs to the EIP repository, and any other subgroup belongs to the ERC repository. How each repository will run itself going forward is outside the scope of this EIP. Since the differing needs of the two communities are precisely the motivation for this proposal, it only states that their operating approaches will likely diverge significantly, without specifying further.
Changes to the numbering rule
Until now, proposal numbers have been determined by the number of the PR that first introduced them. After the split, editors maintain a single shared document from which numbers are assigned. Each repository's editors assign numbers incrementally, with EIPs receiving even numbers and ERCs odd numbers. Splitting numbers into even and odd ensures the two repositories never collide even though each assigns its own numbers. The timing of when each repository's editors switch to this numbering scheme is left to their own policy decisions.
Rationale for the split: the cost of ambiguity and deployment timelines
The source text frames the difference between the two communities along two axes. The first is the cost of specification ambiguity. Core protocol work has little tolerance for implementation differences, and ambiguous specifications are costly: if one part of a new specification is implemented incorrectly, the Ethereum mainnet can split, causing node operators and service users losses ranging from millions to billions in value. By contrast, even a loosely specified Solidity interface can be implemented by each contract in a compatibly adjusted way, and a missing RPC API has little effect on communities that do not use that wallet. The second axis is deployment timing. A core EIP that adjusts the gas cost of transaction data must be applied network-wide at a fixed point in time. By contrast, an RPC that adds new semantics to gas estimation does not need to be rolled out to every client at once, requires deployment by RPC service providers as well, and wallets may even use early support as a differentiator.
A separate lifecycle for core development
The EIP repository's official lifecycle is Draft -> Review -> Last Call -> Final. However, AllCoreDevs calls already run a different lifecycle for core EIPs, which the source text expresses as Draft -> Eligible for Inclusion -> Considered for Inclusion -> Testnet -> Mainnet. At the third stage an EIP is assigned to a specific fork, a consideration that does not apply at all to smart contract or wallet standards. After the split, the core side is expected to make procedural changes such as adding the Eligible for Inclusion and Considered for Inclusion stages, adding testnet and mainnet stages, adding a fork header to mark EIPs slated for implementation in a specific fork, and replacing the test section with links to reference tests. On the ERC side, changes such as a strong working group model, an outdated or replaced stage to mark proposals superseded by later specifications, and appointing reviewers dedicated to specific EIPs could be adopted.
Alternatives considered
The source text reviews alternatives raised instead of splitting. A working group model would be an important social signal to the ERC community that experts have gathered, but on the core side the AllCoreDevs-Execution and AllCoreDevs-Consensus calls already serve that role, so it would only add friction to the existing process. Domain-specific dedicated editors have already been implemented via the eip-editors.yml file, but have had no measurable effect on community differentiation and do not address the governance and workflow changes core developers want. Convenience fixes such as allowing Discord links or loosening restrictions on external links are worth trying regardless of whether the split happens, but they do not address the underlying differentiation problem. Replacing editors with an AI chatbot is assessed as benefiting no one. The source text notes that most of these alternatives have their own merits and that adopting the split does not mean rejecting them, that is, they can be pursued together.
Objections and responses
To the objection that the community will be split, the source text responds that differentiation is already underway. The AllCoreDevs call has already split into consensus layer and execution layer calls, wallet API discussions are handled by AllWalletDevs, and cross-chain issues are handled by CAIP (Chain Agnostic Improvement Process). The source text argues this should be seen not as fragmentation but as 'sharding,' where subcommunities sharing a common interest gather together and thereby grow the overall scope. To the objection that, since this affects process, it should first be documented in EIP-1, it responds that doing the split first follows the maxim of refactoring before adding new features, and that deciding which repository a proposal belongs in is central to the decision-making process, giving ample grounds to treat it as a Meta-category EIP. The point that repository structure changes need not be bundled with process changes was accepted, and this EIP was revised to deal only with the repository structure change.
Backward compatibility and current status
Old ERC links using the existing eips.ethereum.org address continue to work. Redirects are configured so that visiting that location forwards to the corresponding address on the new ERC repository. Even after the split, members of the ERC community can still submit a new ERC to the existing EIP repository, in which case an editor will direct them to the new repository. The text notes that an ERC that does not respond to editor requests would not get merged anyway. Since this proposal deals only with the proposal process for EIPs and ERCs, adopting it is not seen as creating any new attack surface. This EIP's status is Final, meaning the specification is settled.