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

Added: Ethereum Improvement Proposal #85

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added: Ethereum Improvement Proposal #85

wants to merge 1 commit into from

Conversation

KenMan79
Copy link
Contributor

| 👷 | Ethereum Improvement Proposal | EIP stands for Ethereum Improvement Proposal, a design document providing information to the Ethereum community, describing a new feature for Ethereum, or its processes or environment providing a concise technical specification for the proposed changes act as the “source of truth” for the community. They are the way for people to propose, debate, and adopt changes. Network upgrades and application standards for Ethereum are discussed and developed through the EIP process. The EIP author is responsible for building consensus within the community and documenting dissenting opinions. Anyone within the Ethereum community can create an EIP. Various stakeholders in the community will debate determining if it should be adopted as a standard or included in a network upgrade. Guidelines for writing EIPs are included in EIP 1, and EIPs play a central role in how changes happen and are documented on Ethereum The different types of EIPs include core EIPs for low-level protocol changes that affect consensus and require a network upgrade as well as ERCs for application standards to create tokens, like ERC20 and ERC721 allow applications interacting with these tokens to all treat tokens using the same rules, which makes it easier to create interoperable applications. Every network upgrade consists of a set of EIPs that need to be implemented by each Ethereum client on the network. This implies that to stay in consensus with other clients on the Ethereum mainnet, client developers need to make sure they have all implemented the required EIPs. Because non-core EIPs don't have to be adopted by all applications, but core EIPs must be widely adopted because all nodes must upgrade to stay part of the same network, core EIPs require broader consensus within the community than non-core EIPs.|

| 👷  | Ethereum Improvement Proposal | EIP stands for Ethereum Improvement Proposal, a design document providing information to the Ethereum community, describing a new feature for Ethereum, or its processes or environment providing a concise technical specification for the proposed changes act as the “source of truth” for the community. They are the way for people to propose, debate, and adopt changes. Network upgrades and application standards for Ethereum are discussed and developed through the EIP process. The EIP author is responsible for building consensus within the community and documenting dissenting opinions. Anyone within the Ethereum community can create an EIP.  Various stakeholders in the community will debate determining if it should be adopted as a standard or included in a network upgrade. Guidelines for writing EIPs are included in EIP 1, and EIPs play a central role in how changes happen and are documented on Ethereum The different types of EIPs include core EIPs for low-level protocol changes that affect consensus and require a network upgrade as well as ERCs for application standards to create tokens, like ERC20 and ERC721 allow applications interacting with these tokens to all treat tokens using the same rules, which makes it easier to create interoperable applications. Every network upgrade consists of a set of EIPs that need to be implemented by each Ethereum client on the network. This implies that to stay in consensus with other clients on the Ethereum mainnet, client developers need to make sure they have all implemented the required EIPs. Because non-core EIPs don't have to be adopted by all applications, but core EIPs must be widely adopted because all nodes must upgrade to stay part of the same network, core EIPs require broader consensus within the community than non-core EIPs.|
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

Successfully merging this pull request may close these issues.

1 participant