Skip to content

Commit

Permalink
Merge 6be8d02 into 6aeb8b9
Browse files Browse the repository at this point in the history
  • Loading branch information
SamWilsn authored Apr 17, 2023
2 parents 6aeb8b9 + 6be8d02 commit 303a47f
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 1 deletion.
11 changes: 11 additions & 0 deletions EIPS/eip-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,8 @@ Each EIP must begin with an [RFC 822](https://www.ietf.org/rfc/rfc822.txt) style

`withdrawal-reason`: *A sentence explaining why the EIP was withdrawn.* (Optional field, only needed when status is `Withdrawn`)

`adoptable`: *One of `true` or `false`.* (Optional field, but highly recommended to be set to `true`. Defaults to `false`)

Headers that permit lists must separate elements with commas.

Headers requiring dates will always do so in the format of ISO 8601 (yyyy-mm-dd).
Expand Down Expand Up @@ -192,6 +194,15 @@ EIPs may have a `requires` header, indicating the EIP numbers that this EIP depe

A `requires` dependency is created when the current EIP cannot be understood or implemented without a concept or technical element from another EIP. Merely mentioning another EIP does not necessarily create such a dependency.

#### `adoptable` header

EIPs may have a `adoptable` header. There are a two options available:

- `false`: No changes.
- `true`: Marking a proposal as `adoptable: true` allows _anyone_, with editor permission, to champion the proposal should it become `Stagnant`. Specifically, any editor can merge anyone else's PR that only changes the `status` header of the EIP from `Stagnant` to `Draft`.



## Linking to External Resources

Other than the specific exceptions listed below, links to external resources **SHOULD NOT** be included. External resources may disappear, move, or change unexpectedly.
Expand Down
3 changes: 2 additions & 1 deletion eip-template.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,8 @@ status: Draft
type: <Standards Track, Meta, or Informational>
category: <Core, Networking, Interface, or ERC> # Only required for Standards Track. Otherwise, remove this field.
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
requires: <EIP number(s)> # Only required when you reference an EIP in the `Specification` section. Otherwise, remove this field.
requires: <EIP number(s)> # Only required when you reference an EIP in the `Specification` section. Otherwise, remove this field.
adoptable: false # Allows editors to select a new champion if the authors cannot be contacted and the proposal stagnates.
---

<!--
Expand Down

0 comments on commit 303a47f

Please sign in to comment.