The previous lesson demonstrated how to set EOA code with a Type 4 delegation, but largely glossed over the details of the smart contract.
We’ll explore the topic more deeply now.
Prior to EIP-7702, an EOA and a smart contract were separate entities with a clear boundary. An EOA would call a smart contract, the smart contract would perform some action, and that was it.
In a post EIP-7702 world, an EOA can act like a smart contract, which enables it to use the Ethereum Virtual Machine (EVM) at full capacity.
EIP-7702 marks this special EOA configuration through a special pointer to an address where an “old fashioned” contract can be found. Thus we still need to write a smart contract before we can delegate to it.