Add discussion link and reference ERCs

ethereum · Sep 2, 2024 · 24dc0b2 · 24dc0b2
1 parent 17ac984
commit 24dc0b2
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/EIPS/eip-is-contract.md → EIPS/eip-7761.md b/EIPS/eip-is-contract.md → EIPS/eip-7761.md
@@ -3,7 +3,7 @@ eip: 7761
 title: IS_CONTRACT instruction
 description: Introduce IS_CONTRACT instruction
 author: Andrei Maiboroda (@gumb0), Piotr Dobaczewski (@pdobacz), Danno Ferrin (@shemnon)
-discussions-to: <URL>
+discussions-to: https://ethereum-magicians.org/t/eip-7761-is-contract-instruction/20936
 status: Draft
 type: Standards Track
 category: Core
@@ -17,7 +17,7 @@ Allow EOF contracts to discriminate between EOA (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 and ERC-1155 standard contracts to be implemented, as they rely on discovering whether a token's `safeTransfer` call target was an EOA or a smart contract:
+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 smart contract:
 
 - `safeTransfers` to EOA succeed
 - `safeTransfers` to smart contracts 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)