Cherum vs Multisender: batch payments on one chain vs. cross‑chain fan‑out
Where the two overlap, where they do not, and which one your list actually needs.
What Multisender does well
Multisender has been doing batch payments since 2018 and covers a lot of ground: 46+ EVM chains in one dApp, plus dedicated apps for Solana, TON, Tron, Sui and Aptos, NFT batch sends, CSV upload and pre-send simulation. If you hold one token and want it delivered to a long list of addresses on that same network, it's a proven tool with more chain coverage for that specific job than almost anyone.
Pricing is a flat service fee per batch, set per network in the native coin, on top of gas. A VIP membership removes the service fee entirely, which pays off at large volumes.
Where Cherum is different
Every Multisender operation is one network, one token. Cherum handles the case where that isn't true: recipients on different chains, each receiving a different token, sent from a single signature. With a swap in one network or across networks, your wallet approves the Permit2 contract once per token and network, for any amount, then signs one Permit2 message per batch for its exact total. A batch in one token on one network approves our contract for exactly what the batch spends, fee included. Bridging and swapping are built in, and recipients get gas on arrival. Refunds go to the wallet that paid; if a payment stops in our contract, we deliver it or refund it ourselves.
| Feature | Multisender | Cherum |
|---|---|---|
| Send to many recipients | Yes (large lists) | Yes |
| Multiple chains in one action | No, one network per operation | Yes |
| Different token per recipient | No, one token per operation | Yes |
| Built-in swap / bridge | No | Yes |
| Non-EVM chains | Yes, in separate apps (Solana, TON, Tron, Sui, Aptos) | Yes, 25 networks in one flow, incl. Bitcoin, XRP, Cardano |
| NFT batch sends | Yes | No |
| Gas delivered to recipients | No | Yes |
| Token allowance | Contract approval for the batch total | One token on one network: our contract, for exactly the batch total, fee included. With a swap in one network or across networks: one Permit2 approval per token and network, then one signature per batch for its exact total |
| CSV import | Yes | Yes |
| Custody | Non-custodial | Non-custodial |
| Cost | Flat service fee per batch (per network) + gas; VIP removes it | Small routing fee in the quote |
When to use which
Use Multisender when…
You're distributing one token (or NFTs) to many wallets on a single network you already hold it on, especially at volumes where the per-batch fee or VIP membership is cheap relative to the send.
Use Cherum when…
Recipients sit on different chains or want different tokens (contributors paid in USDC on Base, GRAM on TON and USDT on Tron from one balance), and you want one signature instead of bridging and swapping first.