Mark

Synchronous atomic composability is very overrated imo. Like, think about what are some specific cross-L2 things *you* are already doing or envision yourself doing that could be more seamless. For me, the top two are: 1. I have coins on Optimism, I want to pay Bob, but Bob is only on Arbitrum. 2. I have coins on Taiko, I want to use a dapp on Polygon, so I need to send-to-self to Polygon in order to use that dapp. These are not fancy nerd problems that can be fixed by solving synchrony. These are UX problems that can be fixed with: (i) widely adopting ERC-3770 so that the chain is part of the address, so an address once again becomes a self-contained "how do you pay me" identifier (ii) a cross-L2 exchange protocol (eg. ERC-7683), so you can do cross-chain sends programmatically without juggling which specific intermediaries to trust and which APIs to connect to (iii) wallet integration, so sending cross-L2 is done by putting the recipient's ERC-3770 address into the exact same textbox as you use for regular sends today Solving nerd problems *can* make this much more efficient, especially by making cross-chain swap markets more friendly to liquidity providers, by reducing withdraw times from 1 week (optimistic rollups) to 1 hour (zk rollups today) to 1 slot (ideal zk rollups with proof aggregation). But even there, there's multiple orders of magnitude of unclaimed gains that don't even require getting into synchony.

Gm. Have a ton to clean up apparently, feedback super helpful, hopefully secondary checks coming back -- will have an updated list out later today