MultiMesh

Wiki Powered byIconIQ
MultiMesh

MultiMesh

MultiMesh is a non-custodial cross-chain swap aggregator that aims to discover and route the lowest-cost cross-chain swap paths by scanning multiple bridges and The service is presented as a beta product and is live on . [1]

Overview

MultiMesh is designed to abstract the complexity of moving assets across ecosystems by aggregating bridge routes and liquidity sources into a unified interface. Rather than operating a proprietary bridge, it functions as a routing and aggregation layer that selects or composes paths across existing cross-chain protocols to present a cost and time optimized option for each requested transaction.

The project emphasizes that it does not deploy its own bridging and instead routes through established providers, aligning with a non-custodial design philosophy. [1] [2]

The publicly advertised user experience highlights features associated with retail swaps and portfolio operations—such as a swap UI, a send flow that can direct assets to different destination wallets, limit orders, dollar-cost averaging (DCA, marked beta), analytics, and pricing tools—alongside developer-facing resources including a widget, documentation, and a changelog.

In live UIs, MultiMesh displays route comparisons and provider attributions, presenting estimated costs and times for candidate paths. The service is described as “Powered by LI.FI,” and examples of route providers shown include , Hop, , Relay, and Stargate. [1]

Products

MultiMesh provides a set of tools for cross-chain asset management and interaction across multiple networks.

Cross-chain Swap:

The platform aggregates liquidity from multiple bridges and (DEXes) through . For each request, it evaluates available routes based on parameters such as cost, estimated execution time, and risk, and enables users to execute swaps across supported chains. [1]

Cross-chain Limit Orders:

Users can define target price conditions for cross-chain swaps. Orders are executed automatically when specified conditions are met, using deBridge DLN infrastructure. The feature supports transactions between EVM-compatible networks and non-EVM chains such as . [1]

Gas Refuel:

MultiMesh allows users to transfer native gas tokens across chains within a single transaction. This functionality is designed to facilitate transaction execution on destination networks without requiring prior token bridging. [1] [2]

Portfolio View:

The interface provides an aggregated view of token balances across multiple supported blockchain networks. Users can initiate swaps directly from the portfolio interface. [1]

Embeddable Widget:

MultiMesh offers an embeddable interface that enables third-party platforms to integrate cross-chain swap functionality. Integrators can include the widget within their applications and associate activity with a designated identifier. [1]

Points and Referral System:

The platform includes a points-based system tied to user activity, as well as a referral mechanism through which users may receive a portion of fees generated by referred participants. [1]

Architecture and Technology

Architecture

MultiMesh operates as a routing and aggregation layer rather than as a standalone bridge or liquidity pool. Its primary function is to compute and present available transaction paths across multiple bridges, , and routing protocols.

The system aggregates routes from established cross-chain infrastructure providers and presents users with available options. This approach enables users to evaluate trade-offs between parameters such as transaction cost, execution time, and slippage before confirming a transaction.

Bridging logic and liquidity management are handled by the underlying providers, each of which maintains its own smart contracts and liquidity pools. MultiMesh does not deploy or rely on proprietary contracts that custody user funds, maintaining a non-custodial interaction model. [1]

Technology

MultiMesh is implemented as a non-custodial interface for cross-chain transactions. The system does not custody user funds and does not deploy proprietary swap contracts. Instead, it relies on external infrastructure providers for routing, execution, and settlement. [1]

Technology Stack

The MultiMesh interface is implemented as a web-based application using Next.js 14 (App Router) and TypeScript. Wallet connectivity is supported through integrations with wagmi v2, viem, and RainbowKit, enabling interaction with EVM-compatible networks. Support for Solana-based wallets is provided through the @solana/wallet-adapter, including compatibility with Phantom.

Cross-chain routing is facilitated through the REST API and the @lifi/sdk, which are used to construct and submit transaction requests. Cross-chain limit order functionality is implemented via the deBridge DLN REST API.

Data storage is managed using Supabase with a PostgreSQL database, while application hosting is provided by Vercel. Treasury management is conducted using a 2-of-2 Gnosis Safe deployed on the mainnet. [1]

Aggregate Infrastructure

MultiMesh utilizes an aggregation layer provided by to access multiple bridges and decentralized exchanges (DEXes). Supported infrastructure includes

For each request, available routes are evaluated based on parameters such as transaction fees, slippage, and estimated execution time. The selected route is displayed to the user prior to transaction confirmation. [1] [2]

Supported Chains

MultiMesh supports multiple networks for cross-chain interactions, including

Support also extends to , where transactions are processed as a destination network via deBridge DLN, with SOL as the native token. [1]

Fees

MultiMesh applies a total protocol fee of 40 basis points (bps) per swap transaction. Of this amount, 15 bps is allocated to MultiMesh as an integrator fee, collected through’s FeeForwarder mechanism and directed to the protocol treasury. The remaining 25 bps is allocated to as part of its routing infrastructure. [2]

No additional subscription fees or deposit fees are applied. The fee structure is incorporated into the quoted output amount, which is displayed to the user prior to transaction confirmation. [1] [2]

Fee Model

The fee model is based on per-transaction charges rather than recurring fees. Fees are applied at the point of execution and are integrated into the routing process through .

The allocation reflects a separation between the interface layer (MultiMesh) and the underlying routing infrastructure, with each component receiving a defined portion of the total fee. [2]

Use Cases

  • Cross-chain token swaps with comparative route selection across multiple bridge providers
  • Sending assets cross-chain to a different recipient wallet on the destination network
  • Limit orders and DCA to manage positions across chains
  • Embedding cross-chain swap functionality in wallets or dApps through a widget and documentation
  • Utilizing analytics and pricing tools to assess estimated time and costs for cross-chain routes

These use cases reflect the project’s dual focus on end-user swaps and integrator workflows that require a unified cross-chain interface. [1] [2]

Team

The project was initiated by a founding team with complementary roles in both technical development and operational coordination.

  • Tomide Akinrodoye (Founder); associated with business development activities including partnerships, ecosystem coordination and strategic positioning of the platform. [4]
  • Michael Kurz (Co-founder); involved in full-stack engineering including frontend, backend, integration, database, security, infrastructure. [3]

Partnerships

MultiMesh integrates with external infrastructure providers to support routing, execution, and security-related functions within the platform. These partnerships include:

  • : MultiMesh utilizes LI.FI as its primary aggregation layer for cross-chain routing. Transaction execution is performed through LI.FI’s system [1]
  • : MultiMesh integrates with deBridge to support cross-chain limit order functionality via the deBridge DLN (Decentralized Liquidity Network). This infrastructure enables execution of transactions across multiple environments, including transfers between EVM-compatible networks and non-EVM networks such as . [1]
  • Blockaid: MultiMesh is included in Blockaid’s domain allowlist, which is used by supported wallet interfaces to assess transaction safety. This classification may affect how transactions initiated through the interface are evaluated within compatible wallet environments. [1]

참고 문헌.

카테고리위키 MC이벤트용어집