Update narrative on EIPs up-to-dateness and relevance (#106)

* Update narrative on EIPs up-to-dateness and relevance * Update spec/eof.md Co-authored-by: Alex Beregszaszi <[email protected]> --------- Co-authored-by: Alex Beregszaszi <[email protected]>
ipsilon · May 8, 2024 · 42e9147 · 42e9147
1 parent 22e56b0
commit 42e9147
Showing 1 changed file with 1 addition and 5 deletions.
diff --git a/spec/eof.md b/spec/eof.md
@@ -4,9 +4,7 @@
 
 ## Preface
 
-**This document describes all the changes which we previously dicussed titles as EOF 1.1 and EOF 2.0. Those changes do not have an EIP yet.**
-
-This unified specification should be used as a guide to understand the various changes the EVM Object Format is proposing. The individual EIPs ~~still remain the official specification and should confusion arise those are to be consulted~~ are not fully updated yet, and this document serves as a main source of truth at the moment. See appendix for the original list of EIPs.
+This unified specification should be used as a guide to understand the various changes the EVM Object Format is proposing. See appendix for the list of EIPs, which stand as the official specification.
 
 While EOF is extensible, in this document we discuss the first version, EOFv1.
 
@@ -349,8 +347,6 @@ Annotated examples of EOF formatted containers demonstrating several key feature
 
 These are the individual EIPs which evolved into this spec.
 
-Specifications contained within are **out-of-date**, use only for reference and to look up motivation!
-
 - 📃[EIP-3540](https://eips.ethereum.org/EIPS/eip-3540): EOF - EVM Object Format v1 [_history_](https://github.com/ethereum/EIPs/commits/master/EIPS/eip-3540.md)
 - 📃[EIP-3670](https://eips.ethereum.org/EIPS/eip-3670): EOF - Code Validation [_history_](https://github.com/ethereum/EIPs/commits/master/EIPS/eip-3670.md)
 - 📃[EIP-4200](https://eips.ethereum.org/EIPS/eip-4200): EOF - Static relative jumps [_history_](https://github.com/ethereum/EIPs/commits/master/EIPS/eip-4200.md)