From 8f43e4cb0fd2fd4385d680e43f7b28e6a9e142ad Mon Sep 17 00:00:00 2001 From: Danno Ferrin Date: Thu, 4 Apr 2024 02:55:48 -0700 Subject: [PATCH] Update EIP-7620: Update InitcodeTransaciton validation Merged by EIP-Bot. --- EIPS/eip-7620.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/EIPS/eip-7620.md b/EIPS/eip-7620.md index e6eb04b189722f..286b52c3a025b1 100644 --- a/EIPS/eip-7620.md +++ b/EIPS/eip-7620.md @@ -73,7 +73,8 @@ initcode_cost = 0 #### Transaction validation -- `InitcodeTransaction` is invalid if there are more than `MAX_INITCODE_COUNT` entries in `initcodes`, or if any one exceeds `MAX_INITCODE_SIZE`. +- `InitcodeTransaction` is invalid if there are zero entries in `initcodes`, or if there are more than `MAX_INITCODE_COUNT` entries. +- `InitcodeTransaction` is invalid if any entry in `initcodes` is zero length, or if any entry exceeds `MAX_INITCODE_SIZE`. - `InitcodeTransaction` is invalid if the `to` is `nil`. Under transaction validation rules `initcodes` are not validated for conforming to the EOF specification. They are only validated when accessed via `TXCREATE`. This avoids potential DoS attacks of the mempool. If during the execution of an `InitcodeTransaction` no `TXCREATE` instruction is called, such transaction is still valid.