From 36ecd942a4adc9a59c6a332ff5eede9d77b864a0 Mon Sep 17 00:00:00 2001
From: pdobacz <5735525+pdobacz@users.noreply.github.com>
Date: Wed, 11 Sep 2024 09:05:37 +0200
Subject: [PATCH] Update EIP-7761: reference 3540 explicitly

---
 EIPS/eip-7761.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/EIPS/eip-7761.md b/EIPS/eip-7761.md
index d42f574a7ee553..0cf72d0fcb13e2 100644
--- a/EIPS/eip-7761.md
+++ b/EIPS/eip-7761.md
@@ -17,7 +17,7 @@ Allow EOF contracts to discriminate between EOAs (Externally Owned Accounts) and
 
 ## Motivation
 
-EOFv1 as scoped in [EIP-7692](./eip-7692.md) removes code introspection capabilities from the EVM, including the `EXTCODESIZE` instruction. This makes it hard for [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md) standard contracts to be implemented, as they rely on discovering whether a token's `safeTransfer` call target was an EOA or a contract account:
+EOFv1 as scoped in [EIP-7692](./eip-7692.md) removes code introspection capabilities from the EVM, including the `EXTCODESIZE` instruction (in [EIP-3540](./eip-3540.md)). This makes it hard for [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md) standard contracts to be implemented, as they rely on discovering whether a token's `safeTransfer` call target was an EOA or a contract account:
 
 - `safeTransfers` to EOAs succeed
 - `safeTransfers` to contract accounts call an `onERC721Received` (`onERC1155Received`) on them and expect to get a special magic return value, otherwise the transfer reverts (on the assumption that such a receipient may not be able to interact with the token)