diff --git a/EIPS/eip-7761.md b/EIPS/eip-7761.md index 22d52c85e650a4..ecd40558d67aa9 100644 --- a/EIPS/eip-7761.md +++ b/EIPS/eip-7761.md @@ -1,7 +1,7 @@ --- eip: 7761 title: ISCONTRACT instruction -description: Introduce ISCONTRACT instruction +description: Introduce ISCONTRACT instruction to replace the EXTCODESIZE > 0 check in EOF author: Andrei Maiboroda (@gumb0), Piotr Dobaczewski (@pdobacz), Danno Ferrin (@shemnon) discussions-to: https://ethereum-magicians.org/t/eip-7761-is-contract-instruction/20936 status: Draft @@ -80,11 +80,11 @@ Removing code introspection is one of the tenets of EOF and `ISCONTRACT` would b ### "Endgame Account Abstraction" issues -TBD - can someone verbalize it? - +TBD - can someone verbalize it? + ### Relation to [EIP-7702](./eip-7702.md) "Set EOA account code" -After [EIP-7702](./eip-7702.md) is activated, the discrimination between EOAs and contract accounts using `EXTCODESIZE` (or `ISCONTRACT`) has an edge case: Whenever an EOA sets its code to a contract account which does not respond as expected to an `onERC721Received` (`onERC1155Received`) callback, transfers to it will revert, despite the recipient being able to interact with the token. This has been deemed unlikely to be a problem, as for the intended real-world uses of `EIP-7702`, those callbacks will be implemented by designator codes. +After [EIP-7702](./eip-7702.md) is activated, the discrimination between EOAs and contract accounts using `EXTCODESIZE` (or `ISCONTRACT`) has an edge case: Whenever an EOA sets its code to a contract account which does not respond as expected to an `onERC721Received` (`onERC1155Received`) callback, transfers to it will revert, despite the recipient being able to interact with the token. This has been deemed unlikely to be a problem, as for the intended real-world uses of EIP-7702, those callbacks will be implemented by designator codes. ### Including safe guarding against proxy bricking @@ -100,7 +100,7 @@ This problem is potentially solvable on the application layer (proxy upgrade wou ## Security Considerations -TBA +Needs discussion ## Copyright