From 4183219df4b39f76a3fa6aed0b1aadbf2324d4df Mon Sep 17 00:00:00 2001
From: pdobacz <5735525+pdobacz@users.noreply.github.com>
Date: Wed, 3 Jul 2024 11:28:06 +0200
Subject: [PATCH] Update EIP-7620: Disallow referencing by both RETURNCONTRACT
 and EOFCREATE

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 f690f07a54637..8b672835bdbde 100644
--- a/EIPS/eip-7620.md
+++ b/EIPS/eip-7620.md
@@ -103,7 +103,8 @@ We extend code section validation rules (as defined in [EIP-3670](./eip-3670.md)
 5. `RETURNCONTRACT` the subcontainer pointed to `deploy_container_index` must not contain a `RETURNCONTRACT` instruction
 6. It is an error for a container to contain both `RETURNCONTRACT` and either of `RETURN` or `STOP`
 7. It is an error for a subcontainer to never be referenced in its parent container
-8. `RJUMP`, `RJUMPI` and `RJUMPV` immediate argument value (jump destination relative offset) validation: code section is invalid in case offset points to the byte directly following either `EOFCREATE` or `RETURNCONTRACT` instruction.
+8. It is an error for a given subcontainer to be referenced by both `RETURNCONTRACT` and `EOFCREATE`
+9. `RJUMP`, `RJUMPI` and `RJUMPV` immediate argument value (jump destination relative offset) validation: code section is invalid in case offset points to the byte directly following either `EOFCREATE` or `RETURNCONTRACT` instruction.
 
 ### Data Section Lifecycle