# Introduction Ethereum’s adoption of the rollup-centric roadmap, along with the recent boom of L2s, L3s, and RollApps has created isolated markets, dividing users, capital, and developers. Interchain bridges and communication protocols attempt to solve this problem, but the UX is generally poor, with latency being a prominent issue. It is nearly impossible to design a multi-chain application on top of existing solutions that provide an experience similar to single-chain applications. Musafir is a novel idea—a UX layer that inherits the security of Ethereum via Eigenlayer and offers near-instantaneous finality and access to assets on all blockchains. This allows applications to create seamless, chain-agnostic UX using Musafir. In this paper, we will cover the technical innovations that make this vision possible, explore possible applications built using Musafir, and discuss future developments. Musafir is a cross-chain protocol built on Ethereum using EigenLayer that allows for instant settlement of assets between different chains allowing developers to build cross-chain apps that settle instantaneously and giving users the ability to spend their assets on any chain without latencies of traditional bridging. Musafir significantly improves the user experience of Ethereum and its L2s and allows for the building of wallet applications that can completely abstract away the complexities of bridging and fragmentation between different L2s. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://musafir.gitbook.io/musafir/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.