With Pectra recently going live on Ethereum and other EVMs, a lot of code using isContract basically broke.
Now EOA’s can sometimes have contract code, tricky stuff.
The Optimism OP Stack contracts used to rely on such a check for deposit transactions, that means you can’t do forced withdrawals - or escape hatch withdrawals as we call them in Superbridge - from smart contract wallets.
But with Pectra, that meant EOA’s sending calls via a delegated contract wouldn’t have been able to either!
Luckily they thought about this, and amended the OP Stack with a nice EOA library to detect this situation.
That means 7702 delegated accounts can still submit rollup bound transactions from Ethereum (or settlement chain), neat!
These changes are already live on some OP Stack networks, like OP Mainnet and Base, but I expect these changes to live on almost every network over time.
And for what it’s worth we allow forced exits on Superbridge, simply enable the toggle and submit your withdrawal from Ethereum?
26.07.25
Across Protocol also recently updated to use a similar helper.
For context, Across used to have the following semantics when bridging,
- Is the recipient an EOA? Send ETH, no matter if the output token specified is WETH or ETH
- Is the recipient a contract? Send WETH, no matter if the output token specified is ETH or WETH
Their check is a little simpler than the OP Stack one, but the result is the same!