Ethereum Multisender: Bulk Send ETH and ERC-20 Tokens

A multisender is a tool that sends tokens to many wallets in a single transaction instead of one at a time. You give it a list of addresses and amounts, and its smart contract loops the transfers in one batch, so 100 recipients cost roughly one transaction's worth of overhead instead of 100. Tokenry's multisender is non-custodial: the tokens move straight from your wallet to the recipients.

Both. It works as an ERC-20 multisender, sometimes written erc20 multisender, for any token contract, and it also sends native ETH. Paste an ERC-20 token address to airdrop that token to multiple addresses, or send ETH itself, one asset per batch.

Batching typically cuts gas by 60 to 90% versus sending individually, because you pay the base transaction overhead once per batch instead of once per wallet. Sending to 500 wallets one at a time means 500 separate transactions; the multisender turns that into a handful. The bigger your list, the more you save.

There is no fixed number, because mainnet gas is priced in gwei and swings with demand, but you have real levers. The cost comes down to the gas price when you send, the per-recipient gas of the transfer, and the ETH price. The biggest lever you control is timing: gas is usually cheapest off-peak, roughly 02:00 to 07:00 UTC and on weekends, and most expensive during US market hours, so watching the Etherscan gas tracker and firing when gwei is low can cut the bill several times over. Sending native ETH is cheaper per recipient than an ERC-20, and batching is where the 60 to 90% saving comes from. The review step shows the estimated gas before you sign, so there is no surprise.

Both. Choose native ETH to pay out the coin itself, or paste any ERC-20 contract address to distribute that token. Each run sends one asset at a time, so you send ETH in one batch and a given ERC-20 in another rather than mixing them in the same transaction.

Yes. The multisender handles any standard ERC-20, which includes USDC and USDT, so a payroll or treasury run works exactly like an airdrop: upload an address,amount CSV with a different amount per row. Batching many payments into one transaction is where a treasury saves most versus paying contributors one at a time. It stays non-custodial and the contract is verified on Etherscan, so the stablecoins leave your own wallet only when you sign each batch, which matters for DAO and multisig accountability. USDC and USDT need the same one-time approval before the first send, and the review step catches a malformed payroll line before you sign, not mid-run.

For any ERC-20, you sign a one-time approval that lets the multisender contract move that specific token on your behalf. It is a standard ERC-20 security step that you do once per token, and you can revoke it later. Native ETH needs no approval, since there is no token contract to authorize.

Each batch on Ethereum handles up to 800 recipients. If your list is longer, the tool automatically splits it into multiple batches and walks you through signing each one, so there is no hard cap on the total number of wallets you can pay.

Neither. Each batch is its own transaction, so a failure is isolated: batches that already confirmed stay confirmed, and the funds for unsent batches never leave your wallet. Wallets already paid are not paid again, you simply resume the remaining recipients. If a batch stalls because gwei jumped mid-airdrop, you can wait for gas to drop or resubmit higher and keep signing the rest, picking up from where it stopped. Because it is non-custodial, a failed transaction just reverts on-chain and nothing is lost, and the review step's gas estimate helps you avoid starting a big run right as gas is climbing.

One recipient per line, as address,amount. You can paste the list or upload a CSV, and the tool tolerates trailing commas, extra spaces, and tab separators, then validates every address before you send. Invalid rows are flagged so you can fix them rather than sending to a bad address.

Yes. Tokens move directly from your wallet to each recipient inside the same transaction, and the contract never holds or pools your funds. The contract is verified on Etherscan, so you can read exactly what it does before you use it.

Disperse pioneered this non-custodial batch-send pattern, and Tokenry uses the same idea with a full interface on top: CSV upload, address validation, automatic batch splitting for large lists, and a clear review step, rather than hand-formatting input for a bare contract. Same trustless mechanics, less room for a costly mistake.

Mainnet is the right choice when your recipients and token already live on Ethereum and you want maximum reach and credibility. For frequent or very large airdrops where fees add up, the same tool on Base, Arbitrum, Optimism, or Polygon costs a fraction of mainnet gas. Tokenry runs the identical multisender on all of them.