Send

Send Sonic (S) to many wallets

Send Sonic to many wallets in a single on-chain batch. Upload a CSV of addresses and amounts, confirm once, and send.u.cash disperses S to every recipient, non-custodial.

Why send Sonic in a batch

One on-chain transaction, many recipients. Pay your whole list at once instead of sending one by one.

One transaction

Disperse S to hundreds of wallets in a single on-chain batch, not dozens of separate sends.

CSV upload

Paste or upload a list of addresses and amounts. Review the total, then confirm once.

Non-custodial

S moves straight from your wallet to each recipient. U.CASH never holds the funds.

Web3 names

Send to ENS, Unstoppable Domains, and FIO handles. The batch resolves names to addresses for you.

Payroll and airdrops

Run payouts, rewards, and distributions in one go, on your own schedule.

Clear receipt

Every recipient and amount is logged in one batch record you can audit and export.

How it works

Step 01

Prepare your list

Add recipient addresses (or web3 names) and S amounts to a CSV.

Step 02

Upload to send.u.cash

Load your list and review the total Sonic to be sent and the network fee.

Step 03

Confirm one transaction

Approve a single on-chain batch. Your wallet signs it; U.CASH never holds the S.

Step 04

Recipients receive

Every address gets its Sonic directly. You get one batch record to audit and export.

What you can do

Payroll

Pay a team in S each cycle, one batch, every wallet.

Airdrops

Distribute Sonic to a community or holder list fairly and transparently.

Affiliate payouts

Settle partner and referrer balances in a single send.

Vendor payments

Pay many suppliers at once instead of handling each wire.

Refunds and rebates

Issue S back to many customers in one batch.

Grants and tips

Fund many contributors or creators from one transaction.

Send more than Sonic

Ethereum (ETH)

The leading smart-contract blockchain and home of ERC-20.

Base (ETH)

Ethereum L2 built on the OP Stack.

Arbitrum (ETH)

Leading Ethereum L2 by activity.

Polygon (POL)

EVM sidechain built for fast, cheap payments.

Berachain (BERA)

EVM L1 with Proof-of-Liquidity consensus.

Avalanche (AVAX)

Fast-finality EVM chain with sub-second settlement.

Before you start

The setup is deliberately short. One wallet capable of holding Sonic and a little S for gas on its chain, one receiving address for the output, and you have everything: a web3 name resolves to the address just as well as the raw string. Read the preview before signing, since it carries the whole trade at a glance, the amounts in and out, the fee, and the network cost. The wallet remains yours throughout and signs nothing you have not seen on screen, which is the whole security posture in one sentence.

Fees and settlement

The cost picture is two lines. The platform side is a flat 0.50% all-in on the swap, quoted before you sign, with no spread and no routing cut behind it. The network side is gas paid in S, settling with sub-second finality blocks on Proof-of-Stake DAG (ABFT), which the preview itemizes per leg. Settlement is on-chain to the address you chose: Credited once the transaction finalizes on-chain, typically well under a second. on this asset, after which the balance is spendable and non-custodial in the fullest sense, yours to move with no platform in the path.

The route runs on the aggregated DEX route, and atomicity is the property that matters: the approved number either happens in full or the transaction reverts with nothing moved but the attempt's gas. There is no resting state between legs where value sits in someone else's hands, and a route that misses your bounds simply fails clean, ready for a fresh quote. Cheap and loud beats silent and expensive as failure modes go.

Sending Sonic: FAQ

How many wallets can I send Sonic to at once?
As many as your list needs. Upload a CSV of addresses and amounts and send.u.cash batches the S transfers into one on-chain transaction.
What does it cost to batch-send Sonic?
You pay the on-chain network fee for the batch plus a small dispersion fee, far less than sending each transfer separately.
Do recipients need a U Account?
No. S lands in whatever wallet address, or web3 name, you specify for each recipient.

Send Sonic to your whole list

Batch-send S to many wallets in one on-chain transaction, non-custodial.