Mitosis + Hyperlane = Scalable Cross-Chain Liquidity

Mitosis
Mitosis Blog
Published in
3 min readApr 10, 2024

--

Scalable Expansion With Hyperlane

The Mitosis cross-chain liquidity protocol leverages Hyperlane as its communication layer to amplify its network coverage. Hyperlane’s unique features of permissionless interoperability and multi-VM support empower Mitosis to expand to a broad spectrum of networks. Extensive network access simplifies the user experience by allowing users to just settle with Mitosis rather than navigating through numerous cross-chain protocols. Here’s how it works:

How Mitosis Leverages Hyperlane

Communication layer is a crucial component for any cross-chain transfer protocol. The protocol must confirm that the user’s assets on the origin network are either locked or burnt before it sends the corresponding assets to the user on the destination network. The origin network must accurately communicate the status of the users’ assets with the destination network.

Mitosis cross-chain liquidity protocol incorporates Hyperlane as its communication layer. Hyperlane is an arbitrary message bridge designed to deliver any type of data between networks. Once users lock their assets to the Mitosis Vault in the origin network, Hyperlane relays the information on the amount and type of locked assets to the destination network. The Mitosis Vault on the destination network then sends the corresponding assets back to the users.

Why Hyperlane? Scalability.

The scalability of the communication layer is essential for cross-chain liquidity protocols. The scope of the communication layer’s network support directly impacts the liquidity protocol’s reach. This is precisely why Mitosis opted for Hyperlane: its scalability. Let’s explore the design elements that enable Hyperlane to achieve scalability.

Permissionless Interoperability

Permissionless interoperability allows networks to adopt Hyperlane autonomously without the resources from the Hyperlane team. In contrast, legacy cross-chain messaging protocols rely on the protocol team to establish new connections. The necessity for the team’s direct involvement in integrating networks one by one restricts the protocol’s network reach. This issue becomes more significant as the modular era progresses with a surge of new networks.

Conversely, integrating Hyperlane does not require resources or permissions from the Hyperlane team. Therefore, Hyperlane can expand across multiple networks simultaneously, with each network autonomously implementing Hyperlane to its own network. In short, permissionless interoperability translates into unmatched potential for network coverage.

Multi-VM Support

Thanks to contributions from diverse ecosystems, Hyperlane currently supports Ethereum, Solana, Move, and Cosmos with plans for further expansion. This wide range of support stands out among other protocols who are mostly constrained to only one or two ecosystems. Adapting a protocol to accommodate a new ecosystem entails complex modifications across different programming languages, consensus mechanisms, and VM environments. However, Hyperlane could obtain multi-VM support because teams that resonate with the value of permissionless interoperability have voluntarily adapted Hyperlane into their ecosystems.

Just Settle with Mitosis

By directly inheriting the scalability of Hyperlane, Mitosis obtains the potential for extensive network support across various ecosystems. Scalability in cross-chain liquidity protocol removes the need for users to study and trust numerous cross-chain protocols each supporting only a handful of networks. Instead, users will just settle with Mitosis to freely navigate through the blockchain landscape without barriers between chains and ecosystems.

Join the Mitosis Community

Please follow our journey and provide your thoughts on our Discord and X. We’ll run regular AMAs & podcasts and provide other essential updates to keep you in the loop. Interested in how Mitosis works? Take a deeper dive into our technical documentation.

Link3 | Website | Expedition | Documentation | X (Twitter) | Discord | Telegram

--

--