Skip to content
Magi logo Magi Documentation

Senders and Receivers

Feeless Value Transfer via Native Asset Mapping Within Magi.

Senders & Receivers are users who leverage Magi to send value between different blockchain wallet addresses that are connected to Magi - like sending BTC to an Ethereum wallet address — without using traditional bridges, swaps, or liquidity pools. All of this happens inside Magi, using its internal accounting system and wallet-layer abstraction, powered by Native Asset Mapping.

What Native Asset Mapping Enables

Section titled “What Native Asset Mapping Enables”

Native Asset Mapping is Magi’s mechanism for linking different blockchain wallet addresses and allowing transfers of the respective native assets between those wallets. It allows users to:

  • Connect wallets from different blockchains (BTC, ETH, SOL, etc.) to Magi.
  • Send native assets (e.g., BTC) to a connected wallet address associated with another blockchain (e.g., an ETH wallet).
  • Receive native assets.

The sender pays a one-time network fee to deposit the asset into Magi; the protocol handles the internal ledger shift and the receiver can send that asset to any other wallet address connected to Magi.

Key Features of This Role

Section titled “Key Features of This Role”
  • Protocol-level value movement - no external bridges or intermediaries.
  • Receive native BTC to a connected ETH wallet (and vice versa).
  • Users pay a fee only when depositing to or withdrawing from Magi; all internal transfers between connected wallets are feeless. - transfers within Magi are feeless.
  • Receivers must connect to Magi to access funds - the system auto-resolves the deposit to their mapped address.
  • Receivers can withdraw funds after completing a swap to the asset of their choice.
  • All assets remain native throughout.

Implications & Use Cases

Section titled “Implications & Use Cases”
  • Remittances: A user in country A can send BTC directly to someone’s ETH wallet in country B.
  • Payments: Customers can pay with the wallet address they have; merchants receive to the wallet address they have with no fees within Magi.
  • Wallet abstraction: Users don’t need to know what chain someone is using — just send to their connected wallet.
  • UX simplification: No need to swap, bridge, or even know which asset a recipient prefers — Magi resolves it.