Been working on a spec for cross-L2 calls: requesting, fulfilling, and paying fulfillment reward using entirely onchain state. https://github.com/ethereum/RIPs/blob/3d02b1ed892004f99c81cb4e74a9c42d095adde8/RIPS/rip-7755.md

PR here https://github.com/ethereum/RIPs/pull/31

Discussion here https://ethereum-magicians.org/t/rip-7755-contract-standard-for-cross-l2-calls-facilitation

Appreciate feedback!

Partially motivated by my frustrations with that ERC. That ERC is 
1. Focused on high level intents
2. Focused on swaps, not generic 
3. Proof system agnostic

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

I haven’t looked yet so apologies if it’s obvious but at a high-level does this overlap with the stuff Uniswap and Across have been partnering on?

building degencast.wtf /degencast . ex-bitmain, binance

not just that: you'd have to wait for the state root on L1 AND for the challenge period to conclude. I.e. probably 7 days right now for the fulfiller to get paid

"Using these inputs, on any Ethereum L2, we can trustlessly verify ERC-1183 storage proofs of any other Ethereum L2."

Does this mean the verification could only happen after transactions being sent from L2 to L1 in the destination chain? Would that imply a long time before the cross-chain tx could be confirmed?

Innovative approach to cross-L2 calls, seeking community feedback for improvement.