Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Send to several people

Batch transfers let you send funds to several recipients in one flow. Each row can have its own recipient, token, and amount, so the feature works for payroll, contributor transfers, reimbursements, grants, or any list of transactions you would otherwise submit one at a time.

TL;DR

Create or upload your transfer list, review every row, approve the required token totals, and deploy one temporary escrow. Mirage then delivers each transfer separately from node-controlled liquidity. Every recipient sees only their own incoming transfer.

Before you start

Have the following ready:

  • The recipient address for every transfer
  • The token and exact amount for every row
  • Enough of each token to cover the combined totals and quoted fees
  • Native network currency for gas
  • A connected wallet on the network where you want to pay

Check Tokens and Networks before preparing a large list. Every token in the batch must be supported on the selected network.

Step 1: Create the transfer list

Open the Mirage app, choose Send to multiple recipients, and select the network for the batch. You can add transfers manually or upload a CSV.

Enter transfers manually

Add one row for each transfer, then enter its recipient, token, and amount. This is the easiest option for a short list or a batch you are still adjusting.

Review a row as soon as you add it. A valid blockchain address can still belong to the wrong person, and blockchain transfers cannot be redirected after delivery.

Upload a CSV

For a longer list, download the current CSV template from the batch form. Fill one transfer per row without renaming, deleting, or rearranging the template's columns, then upload the completed file.

After importing, Mirage shows the parsed rows in the form. Treat the import as a shortcut for data entry, not as final approval. Check that:

  • Every row was imported
  • Each recipient matches your source list
  • Token symbols and networks are correct
  • Amounts use the intended decimal places
  • There are no duplicate or blank rows

Step 2: Review the batch

Before continuing, Mirage shows the transfer rows, combined token requirements, and estimated fees. Review both the individual rows and the totals.

Pay particular attention when the batch contains more than one token. Each token has its own combined requirement, approval, and available balance. The sender-side escrow funding will reflect aggregate batch requirements, not a separate deposit matching each recipient transfer.

Step 3: Approve the tokens

If the batch uses ERC-20 tokens, your wallet may ask you to approve the exact amount Mirage needs for each funding token. A batch containing several tokens can therefore require several approval transactions.

An approval lets the escrow deployment use the quoted token amount. It does not send the recipient transfers. After the required approvals are confirmed, return to the execution screen and continue.

Native network currency does not require an ERC-20 approval, but you still need enough to cover its transfer amount, if any, and gas.

Step 4: Deploy the escrow

Confirm the deployment transaction in your wallet. This creates and funds one temporary escrow for the batch. The escrow holds the batch requirements and node tip while the transfers are being delivered.

Mirage encrypts the recipient rows on your device and broadcasts the encrypted instructions to the Nomad network. One or more nodes can verify the escrow and accept different parts of the batch.

Keep the execution page open until the deployment is confirmed and the batch appears in your History. Once it is recorded there, you can return to the batch later if the page is closed or refreshed.

Step 5: Follow each transfer

The batch progress view tracks each recipient separately. Several nodes can work on the same batch at once, and rows can complete at slightly different times because each delivery is an individual onchain transfer.

Do not resend the entire batch because one row is still pending. First check the status of that row. Other recipients may already have been paid.

The batch is complete when every required recipient transfer has been delivered and proven. If a row cannot complete, use its current status and the batch recovery controls to decide the next step.

How batch privacy works

A batch adds useful separation beyond saving time:

  • The sender-side amount is aggregated. Escrow funding reflects combined requirements, so it does not directly match one recipient's amount.
  • Recipients are separated. Each recipient sees only their own transfer, not the sender address, the other recipients, or their amounts.
  • Batch membership is not announced. An incoming transfer does not state that it belonged to a Mirage batch.
  • The complete recipient list is encrypted. Mirage relays encrypted instructions rather than publishing the batch rows.

The sender still knows the complete list because they created it. Individual token transfers, amounts, and timestamps also remain public on their respective onchain events. What the chain does not provide is an authoritative map joining those recipient transfers to the sender or to one another.

Read Batch Transaction Privacy for the complete sender, recipient, node, Mirage, and public-observer breakdown.

If something goes wrong

Before deployment, correct the list and request an updated quote. After deployment, avoid rebuilding the same batch immediately because the escrow may already contain funds or several nodes may be processing assigned rows.

You can cancel and recover escrowed funds while there are no active node reservations. If reservations are active, each node must complete its assigned work and prove delivery or allow its reservation to expire. Always check which rows have already completed before retrying or creating replacement transfers.

See Cancel or Recover a Transfer for the recovery flow, or Contact Support if the wallet, approval, or deployment appears stuck.

Receipts and records

Open History and select the batch to review its rows and final statuses. Download the available receipt or export after the batch completes, then compare it with your original list before marking the transfers as reconciled.

The receipt contains the batch details in readable form. Keep it private, store it with the same care as payroll or vendor records, and share it only with people who should see the recipient list.

Learn more about local history and backups in Receipts and Records.