nodes about PC and header bytes

Signed-off-by: Danno Ferrin <[email protected]>
ethereum · Nov 5, 2019 · d8451c6 · d8451c6
1 parent 4b2aecf
commit d8451c6
Showing 1 changed file with 9 additions and 3 deletions.
diff --git a/EIPS/eip-2348.md b/EIPS/eip-2348.md
@@ -79,9 +79,15 @@ For this EIP, only header version `1` (contracts starting with the byte stream `
 next three validations are applied to the content of the contract, keeping all other semantics of
 the current "version 0" EVM contracts, including the same gas schedule.
 
-For purposes of EVM Program Counter calculations the first byte after the version header is location
-`0`. The contract header is not part of the accessible contract data. There is no mechanism within
-the EVM to retrieve the header values.
+**unresolved** - How do we deal with executing with the header?
+
+- Should contract execution start at index 4 as PC=0,
+  - This causes EXTCODECOPY indexes to not match up
+- should contract execution start at index 4 as PC=4,
+  - This would require some possibly non-trivial EVM changes
+- should the version header be a multi-byte instruction which is a no-op? Contract starts at 0 and
+  PC=0
+  - This introduces a new opcode, may be the simplest.
 
 ### `BEGINDATA`