From d9303c5a70740e6183367cbde59db988686fb159 Mon Sep 17 00:00:00 2001 From: Manu NALEPA Date: Mon, 16 Dec 2024 11:40:35 +0100 Subject: [PATCH] Adap link texts to the document title, and a link to the `Ethereum Proof-ofStake Consensus Specifications`. --- EIPS/eip-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1.md b/EIPS/eip-1.md index 49853e6bc4a71a..4d3c29ab540fb4 100644 --- a/EIPS/eip-1.md +++ b/EIPS/eip-1.md @@ -21,7 +21,7 @@ For Ethereum implementers, EIPs are a convenient way to track the progress of th There are three types of EIP: -- A **Standards Track EIP** describes any change that affects most or all Ethereum implementations, such as—a change to the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Ethereum. Standards Track EIPs consist of three parts—a design document, an implementation, and (if warranted) an update to the [reference implementation](https://github.com/ethereum/execution-specs) and [formal specification](https://github.com/ethereum/yellowpaper). Furthermore, Standards Track EIPs can be broken down into the following categories: +- A **Standards Track EIP** describes any change that affects most or all Ethereum implementations, such as—a change to the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Ethereum. Standards Track EIPs consist of a design document, an implementation, and (if warranted) an update to the [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs), the [Ethereum Proof-of-Stake Consensus Specifications](https://github.com/ethereum/consensus-specs) and the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper). Furthermore, Standards Track EIPs can be broken down into the following categories: - **Core**: improvements requiring a consensus fork (e.g. [EIP-5](./eip-5.md), [EIP-101](./eip-101.md)), as well as changes that are not necessarily consensus critical but may be relevant to [“core dev” discussions](https://github.com/ethereum/pm) (eg. the miner/node strategy changes 2, 3, and 4 of [EIP-86](./eip-86.md)). - **Networking**: includes improvements around [devp2p](https://github.com/ethereum/devp2p/blob/readme-spec-links/rlpx.md) ([EIP-8](./eip-8.md)) and [Light Ethereum Subprotocol](https://github.com/ethereum/devp2p/blob/master/caps/les.md), as well as proposed improvements to network protocol specifications of [whisper](https://github.com/ethereum/go-ethereum/issues/16013#issuecomment-364639309) and [swarm](https://github.com/ethereum/go-ethereum/pull/2959). - **Interface**: includes improvements around language-level standards like method names ([EIP-6](./eip-6.md)) and [contract ABIs](https://docs.soliditylang.org/en/develop/abi-spec.html).