Update EIP-7702: Remove old note about universal cross-chain deployme…

…nt (#8909)

Update EIP-7702: Remove old section

EIPS/eip-7702.md

@@ -144,7 +144,7 @@ Consistency is a valuable property in the EVM, both from an implementation persp
 
 The main families of instructions where a ban was considered were storage related and contract creation related. The decision to not ban storage instructions hinged mostly on their importance to smart contract wallets. Although it's possible to have an external storage contract that the smart contract wallet calls into, it is unnecessarily inefficient. In the future, new state schemes may even allow substantially cheaper access to certain storage slots. This is something smart contract wallets will very much want to take advantage of that a storage contract wouldn't support.
 
-Creation instructions were considered for a ban on other similar EIPs, however because this EIP allows EOAs to spend value intra-transaction, the concern with bumping the nonce intra-transaction and invalidating pending transactions is not significant. A neat byproduct of this is that by combining EIP-7702 and CREATE2 it will be possible to commit to deploying specific bytecode to an address without committing to any fee market parameters. This solves the long-standing issue of universal cross-chain contract deployment.
+Creation instructions were considered for a ban on other similar EIPs, however because this EIP allows EOAs to spend value intra-transaction, the concern with bumping the nonce intra-transaction and invalidating pending transactions is not significant.
 
 ### Signature structure