Exploration on how the EIL can reduce UX friction on multisig transactionn
InteropSAFE is an exploration of how the Ethereum Interoperability Layer (EIL) can reduce UX friction for multisig-style treasury operations—especially when sending funds to many recipients across chains. The original scope was structured around two milestones, but the current constraints of the EIL SDK (running on a Tenderly forked network without some required features like Safe proxies) led us to iterate toward a simpler approach.
Originally, we defined: • Milestone 1 – UI & Interaction Design Design a full front-end flow: wallet login, interoperable Safe creation (members + threshold), a default connected Safe screen (address, network selector, balance, signers), a USDC claim view on Base, and a “Send a batch of txs” interface for multi-recipient payouts in USDC/ETH. Additional views would show historical transactions and signer changes to cover the whole lifecycle of a multisig. • Milestone 2 – Dapp Logic, EIL SDK & Backend Integrate the EIL SDK and helper contracts to power those flows: Privy/Wagmi auth, ENS resolution and batched Safe deployments via EIL, and a payout engine using CrossChainSdk, CrossChainBuilder, and TransferAction to execute multi-recipient transfers across chains. A backend would surface transaction/signature status and history to the UI.
In practice, the current EIL environment runs on a forked Tenderly network and lacks some of the features we initially depended on (such as Safe proxies and related infrastructure). Because of this, we narrowed the implementation to focus on a simple, EIL-powered distribution flow: a clean “Send Batch” interface that lets a connected user specify multiple recipients and amounts (USDC or ETH) and have the EIL SDK orchestrate the batched execution behind the scenes.
Even with this reduced scope, InteropSAFE demonstrates how EIL’s cross-chain primitives can be wrapped into a single, approachable batch-send experience, and it sets a foundation we can extend back to the full multisig + Safe-centric design once the underlying network features are available.

