From 2e8601d390999b81d3d185930acb8bb36cfdceba Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Fri, 6 Jan 2023 14:07:32 +0100 Subject: [PATCH 1/9] =?UTF-8?q?=F0=9F=93=9D=20Informational=20EIP=20on=20f?= =?UTF-8?q?ull=20EVM=20equivalence?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-draft_evm_equivalence.md | 58 +++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 EIPS/eip-draft_evm_equivalence.md diff --git a/EIPS/eip-draft_evm_equivalence.md b/EIPS/eip-draft_evm_equivalence.md new file mode 100644 index 00000000000000..471e55c434538a --- /dev/null +++ b/EIPS/eip-draft_evm_equivalence.md @@ -0,0 +1,58 @@ +--- +eip: +title: Full EVM Equivalence +description: Canonicalise the definition of Full EVM Equivalence +author: Pascal Caversaccio (@pcaversaccio) +discussions-to: https://ethereum-magicians.org/t/evm-equivalence-and-ethereum-stack-compatibility-definition-future-informational-eip/10044 +status: Draft +type: Informational +created: 2023-01-06 +--- + +## Abstract + +This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. + +## Motivation + +In light of the recent zkEVM announcements by various projects and the ongoing discussion, confusion, and ambiguity about how **full** EVM equivalence is defined, we define a canonical definition to foster a common understanding of the term "Full EVM Equivalence". + +## Specification + +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence "MUST" fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) version at time `t`. + +## Rationale + +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. + +## Backwards Compatibility + +This proposal is fully backward compatible until the first release of the Ethereum Yellow Paper in April 2014. + +## Test Cases + +### Example 1 ✅ + +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t`. + +> Protocol `X` is fully EVM equivalent. + +### Example 2 ❌ + +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t` _except_ using the similar pricing for zero and non-zero byte of data. + +> Protocol `X` is **not** fully EVM equivalent. + +### Example 3 ❌ + +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t` _except_ that the opcode `SELFDESTRUCT` does not destroy any storage. + +> Protocol `X` is **not** fully EVM equivalent. + +## Security Considerations + +There are no security considerations directly related to the definition of "Full EVM Equivalence". + +## Copyright + +Copyright and related rights waived via [CC0](../LICENSE.md). From 47050e5e960cb19a466560628cc8808faaee0e55 Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Fri, 6 Jan 2023 16:10:51 +0100 Subject: [PATCH 2/9] =?UTF-8?q?=E2=99=BB=EF=B8=8F=20=20remove=20quotation?= =?UTF-8?q?=20marks?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-draft_evm_equivalence.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-draft_evm_equivalence.md b/EIPS/eip-draft_evm_equivalence.md index 471e55c434538a..e5c646a3ef01e0 100644 --- a/EIPS/eip-draft_evm_equivalence.md +++ b/EIPS/eip-draft_evm_equivalence.md @@ -19,7 +19,7 @@ In light of the recent zkEVM announcements by various projects and the ongoing d ## Specification -Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence "MUST" fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) version at time `t`. +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) version at time `t`. ## Rationale From bfd99f3c55eb98f0db5ef40c901189f606b8c50b Mon Sep 17 00:00:00 2001 From: Pandapip1 <45835846+Pandapip1@users.noreply.github.com> Date: Fri, 6 Jan 2023 12:28:26 -0500 Subject: [PATCH 3/9] Assign number 6269 and fix external link issue --- EIPS/{eip-draft_evm_equivalence.md => eip-6269.md} | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) rename EIPS/{eip-draft_evm_equivalence.md => eip-6269.md} (78%) diff --git a/EIPS/eip-draft_evm_equivalence.md b/EIPS/eip-6269.md similarity index 78% rename from EIPS/eip-draft_evm_equivalence.md rename to EIPS/eip-6269.md index e5c646a3ef01e0..2f51655ce4b2e3 100644 --- a/EIPS/eip-draft_evm_equivalence.md +++ b/EIPS/eip-6269.md @@ -1,5 +1,5 @@ --- -eip: +eip: 6269 title: Full EVM Equivalence description: Canonicalise the definition of Full EVM Equivalence author: Pascal Caversaccio (@pcaversaccio) @@ -11,7 +11,7 @@ created: 2023-01-06 ## Abstract -This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. +This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. ## Motivation @@ -19,11 +19,11 @@ In light of the recent zkEVM announcements by various projects and the ongoing d ## Specification -Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) version at time `t`. +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) version at time `t`. ## Rationale -A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. ## Backwards Compatibility From da87c922b6ccfcb5033e23fe29c946e0ac1f994f Mon Sep 17 00:00:00 2001 From: Pandapip1 <45835846+Pandapip1@users.noreply.github.com> Date: Fri, 6 Jan 2023 12:31:19 -0500 Subject: [PATCH 4/9] Replace yellow paper with execution specs --- EIPS/eip-6269.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index 2f51655ce4b2e3..6f8ca670d8fd38 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -11,7 +11,7 @@ created: 2023-01-06 ## Abstract -This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. +This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. ## Motivation @@ -19,11 +19,11 @@ In light of the recent zkEVM announcements by various projects and the ongoing d ## Specification -Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) version at time `t`. +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e) version at time `t`. ## Rationale -A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. ## Backwards Compatibility From 08d9bedbe9b50f56e6059ed95ea62c25b96924b5 Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Fri, 6 Jan 2023 18:35:16 +0100 Subject: [PATCH 5/9] Update EIPS/eip-6269.md Co-authored-by: Pandapip1 <45835846+Pandapip1@users.noreply.github.com> --- EIPS/eip-6269.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index 6f8ca670d8fd38..438a663d991e82 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -5,7 +5,7 @@ description: Canonicalise the definition of Full EVM Equivalence author: Pascal Caversaccio (@pcaversaccio) discussions-to: https://ethereum-magicians.org/t/evm-equivalence-and-ethereum-stack-compatibility-definition-future-informational-eip/10044 status: Draft -type: Informational +type: Meta created: 2023-01-06 --- From ab9b87c23842454110e4ea8a76ea0128eb23a0c2 Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Fri, 6 Jan 2023 18:55:44 +0100 Subject: [PATCH 6/9] adjust links & wording Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-6269.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index 438a663d991e82..27e7be4c45f06e 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -3,7 +3,7 @@ eip: 6269 title: Full EVM Equivalence description: Canonicalise the definition of Full EVM Equivalence author: Pascal Caversaccio (@pcaversaccio) -discussions-to: https://ethereum-magicians.org/t/evm-equivalence-and-ethereum-stack-compatibility-definition-future-informational-eip/10044 +discussions-to: https://ethereum-magicians.org/t/evm-equivalence-eip-6269-and-ethereum-stack-compatibility-definition/10044 status: Draft type: Meta created: 2023-01-06 @@ -11,7 +11,7 @@ created: 2023-01-06 ## Abstract -This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e). This definition applies retroactively from the first release of the Ethereum Yellow Paper in April 2014. +This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master). This definition applies retroactively from the first release of the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf) in April 2014. ## Motivation @@ -19,33 +19,33 @@ In light of the recent zkEVM announcements by various projects and the ongoing d ## Specification -Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e) version at time `t`. +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master) version at time `t`. ## Rationale -A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Execution Layer Specification](https://github.com/ethereum/execution-specs/tree/24de2192e02bba11e61746aa9dee04d4e7a8b62e) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. ## Backwards Compatibility -This proposal is fully backward compatible until the first release of the Ethereum Yellow Paper in April 2014. +This proposal is fully backward compatible until the first release of the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf) in April 2014. ## Test Cases ### Example 1 ✅ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t`. +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t`. > Protocol `X` is fully EVM equivalent. ### Example 2 ❌ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t` _except_ using the similar pricing for zero and non-zero byte of data. +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ using the similar pricing for zero and non-zero byte of data. > Protocol `X` is **not** fully EVM equivalent. ### Example 3 ❌ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Yellow Paper at time `t` _except_ that the opcode `SELFDESTRUCT` does not destroy any storage. +_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ that the opcode `SELFDESTRUCT` does not destroy any storage. > Protocol `X` is **not** fully EVM equivalent. From d3aa0adb714a40755e5ad257f86b7f9ca23e39ac Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Sat, 7 Jan 2023 01:02:59 +0100 Subject: [PATCH 7/9] amendments Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-6269.md | 31 +++++++++++++++++++++---------- 1 file changed, 21 insertions(+), 10 deletions(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index 27e7be4c45f06e..f4b0d7c64f2fc6 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -7,11 +7,12 @@ discussions-to: https://ethereum-magicians.org/t/evm-equivalence-eip-6269-and-et status: Draft type: Meta created: 2023-01-06 +requires: 5757 --- ## Abstract -This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is **complete** compliance with the latest version of the [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master). This definition applies retroactively from the first release of the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf) in April 2014. +This EIP standardises the definition of "Full Ethereum Virtual Machine (EVM) Equivalence". Full EVM equivalence is the **complete** compliance with the latest version of the [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/79db92bd4c49bdf5f559fdebea5a9a3a2bf3fb83). This definition applies retroactively since the first release of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) on 2 April 2014 ([first version](https://github.com/ethereum/yellowpaper/blob/0d0d23301d077bbdab5cafae6ab06001e282fae2/Paper.tex)). ## Motivation @@ -19,35 +20,45 @@ In light of the recent zkEVM announcements by various projects and the ongoing d ## Specification -Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence MUST fully (=100%) comply with the latest [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master) version at time `t`. +The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. + +Any protocol, network, smart contract system, or similar that claims at time `t` full EVM equivalence **MUST** fully (=100%) comply with the latest [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/79db92bd4c49bdf5f559fdebea5a9a3a2bf3fb83) version at time `t`. For any time `t` before 6 September 2022 (Bellatrix hard fork date), the **REQUIRED** reference source is the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf). The first public version of the Ethereum Yellow Paper is available at commit [`0d0d23301d077bbdab5cafae6ab06001e282fae2`](https://github.com/ethereum/yellowpaper/blob/0d0d23301d077bbdab5cafae6ab06001e282fae2/Paper.tex). ## Rationale -A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/master) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/79db92bd4c49bdf5f559fdebea5a9a3a2bf3fb83) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. + +Prior to the Bellatrix hard fork on 6 September 2022, the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) was considered more complete and is therefore chosen as the main reference point. ## Backwards Compatibility -This proposal is fully backward compatible until the first release of the [Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf) in April 2014. +This proposal is fully backward compatible up to the the first release of the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) on 2 April 2014. ## Test Cases ### Example 1 ✅ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t`. +_Assumption:_ A protocol `X` follows at time "`t` >= 6 September 2022" all the specifications stated in the Ethereum Execution Client Specifications at time `t`. -> Protocol `X` is fully EVM equivalent. +> Protocol `X` is fully EVM equivalent at time `t`. ### Example 2 ❌ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ using the similar pricing for zero and non-zero byte of data. +_Assumption:_ A protocol `X` follows at time "`t` >= 6 September 2022" all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ using the similar pricing for zero and non-zero byte of data. -> Protocol `X` is **not** fully EVM equivalent. +> Protocol `X` is **not** fully EVM equivalent at time `t`. ### Example 3 ❌ -_Assumption:_ A protocol `X` follows at time `t` all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ that the opcode `SELFDESTRUCT` does not destroy any storage. +_Assumption:_ A protocol `X` follows at time "`t` >= 6 September 2022" all the specifications stated in the Ethereum Execution Client Specifications at time `t` _except_ that the opcode `SELFDESTRUCT` does not destroy any storage. + +> Protocol `X` is **not** fully EVM equivalent at time `t`. + +### Example 4 ✅ + +_Assumption:_ A protocol `X` followed at time "`t` < 6 September 2022" all the specifications stated in the Ethereum Yellow Paper at time `t`. Due to a protocol change at time `t + T`, the protocol additionally supports a transient opcode. -> Protocol `X` is **not** fully EVM equivalent. +> Protocol `X` was fully EVM equivalent at time `t`. Protocol `X` is **not** fully EVM equivalent at time `t + T`. ## Security Considerations From 61785fd4cd41a4304364360ed39bb8fa5409be37 Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Sat, 7 Jan 2023 01:15:58 +0100 Subject: [PATCH 8/9] wording Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-6269.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index f4b0d7c64f2fc6..5b24bbb0ff6043 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -26,7 +26,7 @@ Any protocol, network, smart contract system, or similar that claims at time `t` ## Rationale -A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence. The [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/79db92bd4c49bdf5f559fdebea5a9a3a2bf3fb83) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. +A proper equivalence definition requires a common, publicly available reference that specifies the formal specification of the equivalence benchmark. The [Ethereum Execution Client Specifications](https://github.com/ethereum/execution-specs/tree/79db92bd4c49bdf5f559fdebea5a9a3a2bf3fb83) formulates the formal specification of the Ethereum protocol, which is publicly available and serves as a common reference for all protocols, networks, smart contract systems, or the like that aim to build similar implementations. Prior to the Bellatrix hard fork on 6 September 2022, the [Ethereum Yellow Paper](https://github.com/ethereum/yellowpaper/blob/1016c0603062b76388e3c3c19786cd5f9ca9ac61/paper.pdf) was considered more complete and is therefore chosen as the main reference point. From c38c8538b0cb0a7896a75052800a0794fc8c918d Mon Sep 17 00:00:00 2001 From: Pascal Marco Caversaccio Date: Mon, 13 Feb 2023 21:27:57 +0100 Subject: [PATCH 9/9] change type to informational Signed-off-by: Pascal Marco Caversaccio --- EIPS/eip-6269.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-6269.md b/EIPS/eip-6269.md index 5b24bbb0ff6043..5d4c482a6284cb 100644 --- a/EIPS/eip-6269.md +++ b/EIPS/eip-6269.md @@ -5,7 +5,7 @@ description: Canonicalise the definition of Full EVM Equivalence author: Pascal Caversaccio (@pcaversaccio) discussions-to: https://ethereum-magicians.org/t/evm-equivalence-eip-6269-and-ethereum-stack-compatibility-definition/10044 status: Draft -type: Meta +type: Informational created: 2023-01-06 requires: 5757 ---