This article highlights some of the problems in the multi-chain world and proposes some high-level solutions.

There are three main problems faced by users when interacting with different chains:

  1. Network setup: Switching networks, adding RPC, etc.
  2. Fund procurement: Getting funds on that chain for gas fee payments and other payments.
  3. Siloed view: One has to view all assets differently (solved by Debank for EOA); not for SCWs.

Potential solution:

  1. Network abstraction: One solution is to figure out the network for the user and switch based on the app/asset that the user is interacting with.

    Potential Implementation: Use one RPC to connect to different chain RPCs.

  2. Funds

    1. Gas abstraction: Enable users to pay for gas on chain A with assets on chain B.

      1. Example: Sign a tx with zero value.

      Potential Implementation: Use a relayer for now. In future, we could enable paymasters to talk to each other and use Axelar to bridge the required funds.

    2. Assets transfer: Enable users to bridge assets on the go.

      1. Example: Bridge USDC and then swap/buy/stake.

      Potential Implementation: Use the Axelar network to bridge in the backend.

  3. Unified Interface:

    1. One address/One Identifier.

      Potential Implementation: Use multichain address resolution, such as ENS's, to create overarching addresses.

    2. One view to look at all the cross chains (Debank but multiple SC together).

      Potential Implementation: Fetch smart contract info from different chains together.

References: