-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
classify Standard EIPs - adapted from BIP123 #17
Conversation
needs to be cleaned up a bit. It still mentions Bitcoin. And Networking is already specified to track seperatly in EIP-1 |
thanks for the feedback. Before this EIP, I did see EIP-1 did mention Networking separately. But it didn't seem as clean as BIP123. So it sounds like there's 2 approaches. We either remove the "Peer Services" in this EIP, or remove Networking in EIP-1 and let this EIP manage it/Networking under "Peer Services". |
ok lets change "Peer Services" to "Networking". Core networking; things that affect RLPx will continue to track separately. But things like eth wire protocol changes would fit nicely here. Lastly what do you think about adding another category for standardizing contracts? This would take care of things like #20 and #22 |
done changed to Networking. |
classify Standard EIPs - adapted from BIP123
According to SamWilsn in Editor Office Hours ethereum#17, functions that are only called by the contract maintainer must not be part of the Interfaces. Hence removing them
According to SamWilsn in Editor Office Hours ethereum#17, functions that are only called by the contract maintainer must not be part of the Interfaces. Hence removing them
According to SamWilsn in Editor Office Hours ethereum#17, functions that are only called by the contract maintainer must not be part of the Interfaces. Hence removing them
No description provided.