Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ethereum Request for Comments (ERCs) and Ethereum Standards (ESDs) #16

Closed
ethers opened this issue Nov 17, 2015 · 8 comments
Closed

Ethereum Request for Comments (ERCs) and Ethereum Standards (ESDs) #16

ethers opened this issue Nov 17, 2015 · 8 comments

Comments

@ethers
Copy link
Member

ethers commented Nov 17, 2015

Should we have something like ERC (Ethereum Request for Comments, like the IETF's RFC https://www.ietf.org/rfc.html) ?
Or do we want to somehow expand the notion of EIPs to include them?

The items in https://github.com/ethereum/wiki/wiki/Standardized_Contract_APIs are top candidates for ERCs.

https://en.wikipedia.org/wiki/Request_for_Comments
https://en.wikipedia.org/wiki/Internet_Standard

Then down the line (could take a while), some ERCs could be ESDs (Ethereum Standards).

This is relevant now, since token "standards" are being discussed quite heavily:
https://gist.github.com/frozeman/090ae32041bcfe120824

@niran
Copy link

niran commented Nov 17, 2015

Is it correct to view the token work as an "informational" EIP? If issues outside of the core protocol were fine for BIPs, like HD wallets, I'd expect them to be fine for EIPs as well.

https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1.mediawiki#eip-types

@wanderer
Copy link
Member

@niran yeah that was the idea for "informational" EIP.

@ethers
Copy link
Member Author

ethers commented Nov 18, 2015

opportunity for someone to write the token proposal as the first informational EIP... (@frozeman ?)

@frozeman
Copy link
Contributor

@wanderer if you can make me collaborator of this repo i can edit the issues (ERCs), to give them a good form, we should also add labels, and add them to the issues

@wanderer
Copy link
Member

@ethers @frozeman I think with EIP-3 we don't need to have RFC's ESD. The process for Informational EIPs would be 1) submit an EIP 2) If it gets adopted by a Majority then change the EIPs status to "Accepted" which would be the equivalent to becoming an ESD

@ethers
Copy link
Member Author

ethers commented Nov 19, 2015

ok, Informational can be used and feel free to close this.

also, is it too late for this (rename EIP to EEP)?
https://gist.github.com/frozeman/090ae32041bcfe120824#gistcomment-1623559
EEP = Ethereum Enhancement Proposal, like Python's PEPs. EIP (like BIP) is too hard to say out loud. Maybe that ship has already sailed.

@wanderer
Copy link
Member

@ethers yeah i think we are stuck on EIPs now plus E^i*pi = 1

@obscuren
Copy link
Contributor

In my head I pronounce EIP as "eeeeeeeep"

RaphaelHardFork pushed a commit to RaphaelHardFork/EIPs that referenced this issue Jan 30, 2024
* Add ERC-7254

* 7254: remove extra newlines

---------

Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
bumblefudge pushed a commit to bumblefudge/EIPs that referenced this issue Feb 16, 2024
to add hedera/readme, /c2, c10, & c19
just-a-node pushed a commit to connext/EIPs that referenced this issue Feb 17, 2024
* Add ERC-7254

* 7254: remove extra newlines

---------

Co-authored-by: lightclient <14004106+lightclient@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@niran @wanderer @frozeman @obscuren @ethers and others