Skip to content

Commit

Permalink
EIPS eligible for Inclusion (ethereum#2378)
Browse files Browse the repository at this point in the history
* EIPS eligible for Inclusion

Meta EIP for tracking Eligibility for Inclusion as defined in the EIP-centric Forking Model.

* Spelling and formatting updates

* Formating Github Markdown

* Added number and responded to Feedback

* Update and rename EIP-2378.md to eip-2378.md

* EFI: Updated Discussion-to URL to the /EIP

Given that this will be a registry EIP and the informational part will be moved out eventually. It made sense to me for the appropriate discussion about what EIPs are included should happen on the /ethereum/eip gitter channel.
  • Loading branch information
MadeofTin authored and tkstanczak committed Nov 7, 2020
1 parent ed44054 commit 6a0ebbe
Showing 1 changed file with 74 additions and 0 deletions.
74 changes: 74 additions & 0 deletions EIPS/eip-2378.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
---
eip: 2378
title: EIPs Eligible for Inclusion
author: James Hancock (@MadeofTin)
discussions-to: https://gitter.im/ethereum/EIPs
status: Draft
type: Meta
created: 2019-11-13

---

<!--You can leave these HTML comments in your merged EIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new EIPs. Note that an EIP number will be assigned by an editor. When opening a pull request to submit your EIP, please use an abbreviated title in the filename, `eip-draft_title_abbrev.md`. The title should be 44 characters or less.-->

## Simple Summary
<!--"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the EIP.-->

As part of an EIP centric forking model, this EIP tracks the first step in the approval process for any EIP to be included in a fork or upgrade. Specifically, the stage where the Core Developers vet the concept of an EIP and give a "green light" sufficient for EIP authors to move forward in development.

## Abstract
<!--A short (~200 word) description of the technical issue being addressed.-->

The pipeline for Core EIPs, per the EIP-Centric upgrade model, is as follows.
```
[ DRAFT ] -> [ ELLIGLE FOR INCLUSION ] -> [ IMPLEMENTATION ] -> [ TESTING ] -> [ ACCEPTED ] -> [ DEPLOYED ]
```

This EIP documents all EIPs marked as **Eligible For Inclusion** by the All Core Devs. Typically to reach this stage, an EIP must be discussed in brief on an AllCoreDevs Call and motioned by rough consenses to be moved to this stage. Any additions to this list are required to provide a link to the meeting notes when this discussion and decision took place.

The requirements for **Eligible for Inclusion** is that the AllCoreDevs, representing the major clients and ecosystem stakeholders etc:

- Are positive towards the EIP,
- Would accept (well written) PRs to include the EIP into the codebase.
- So that it could be toggled on for testing…
- …but not with an actual block number for activation

## Motivation
<!--The motivation is critical for EIPs that want to change the Ethereum protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the EIP solves. EIP submissions without sufficient motivation may be rejected outright.-->

Development of clear specifications and pull requests to existing Ethereum Clients is a large investment of time and resources. The state of *Eligible for Inclusion* is a signal from the Ethereum Core Developers to an EIP Author validiating the idea behind an EIP and confirms investing their time further pursing it is worthwhile.

## Specification

| EIP | Title | Pipeline Status | Date of Initial Decision | REF |
| -------- | ----------------------------------------------------- | -------- | ---------- | ---- |
| EIP-663 | Unlimited SWAP and DUP instructions | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1057 | ProgPoW, a Programmatic Proof-of-Work | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1380 | Reduced gas cost for call to self | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1559 | Fee market change for ETH 1.0 chain | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1702 | Generalized Account Versioning Scheme | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1962 | EC arithmetic and pairings with runtime definitions | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-1985 | Sane limits for certain EVM parameters | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |
| EIP-2046 | Reduced gas cost for static calls made to precompiles | ELIGIBLE | 2019-11-01 | [🔗](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%2074.md) |

## Rationale

**EIP Number**

**Title**

**Pipeline Status** : Show the current status in the context of the EIP centric model. The list is sorted by furthest along in the process.

**Date of Initial Decision** : Date of the initial decision for Eligibility for Inclusion

**REF** : Link to the decision on the AllCoreDevs Notes


## References

- EIP Centric Forking Model Proposal by @holiman - https://notes.ethereum.org/@holiman/S1ELAYY7S?type=view



## Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

0 comments on commit 6a0ebbe

Please sign in to comment.