Arc Token Multisender
Sending an airdrop one transfer at a time pays the full cost of a transaction per recipient. The Arc Token Multisender batches recipients into a handful of contract calls, so you pay the transaction overhead once per batch instead of once per wallet. Paste or upload a list with a custom amount per row, approve the token once, and watch each batch settle on Arc in under a second.
- Service fee
- 50 USDC flat
- Network
- Arc Mainnet
- Gas token
- USDC (18 decimals)
- Custody
- Non-custodial
One 50 USDC payment per use, charged on Arc Mainnet. No percentage of your token, no subscription.
Build the airdrop list
Paste addresses, upload a CSV or start from an example. Every row is checked in the browser — addresses are validated, duplicates are collapsed into the first occurrence and malformed lines are reported with their line number — so nothing is submitted that cannot succeed.
One payment per use of the Arc Token Multisender. That is roughly 0.02 ETH in value, but the fee itself is settled in USDC: Arc Mainnet has no ETH, because USDC is the native gas token. Gas comes out of the same balance, so there is nothing to bridge and nothing volatile to buy.
Hard-coded in the contract at deployment as an immutable value. There is no setter and no admin key, so nobody — including Arctools — can redirect it.
How the multisender works
Four steps from a list of wallets to settled airdrops on Arc Mainnet.
- 1Choose what you are sendingAny ERC-20 on Arc Mainnet, or native USDC paid straight out of your balance. ERC-20 airdrops are pulled with transferFrom, so the contract never holds your tokens.
- 2Build the recipient listPaste one address per line, paste address,amount pairs, or upload a CSV. Every line is validated in the browser and rows that cannot succeed are dropped before you pay for gas.
- 3Approve the exact total onceERC-20 airdrops need an allowance for the sum you are sending — not an unlimited one. Native USDC payouts need no approval at all.
- 4Send and watch every batch settleRecipients are grouped into batches of 200 per transaction. Each batch reports its own hash and receipt, and Arc finalises each one in under a second.
Native USDC (used for gas and msg.value) carries 18 decimals. The ERC-20 interface at 0x3600…0000 exposes the same balance with 6 decimals. Mixing the two in one calculation is off by 10¹² — Arctools always uses the ERC-20 interface for pool math and the native interface for gas and service fees.
1. What are you sending?
Pick the asset, then the payout shape.
ERC-20 contract on Arc Mainnet. Arctools reads name, symbol, decimals and total supply to size the amounts.
Parsed with 18 decimals, matching the token's own interface.
2. Recipient list
One address per line. Amounts come from the field above.
0x1234…abcd, one per line. Blank lines and # comments are ignored.
Cost & summary
Everything charged before you sign.
The contract charges its flat fee on every call, so a list that fits in one batch pays it once. Keep the list under 200 recipients to stay at a single fee, and send in one transaction.
Current allowance: 0 tokens
3. Send
You stay in control — Arctools never takes custody of your tokens or liquidity.
The approval covers exactly the total you sent, and the multisender can only ever pull that figure. Once the airdrop settles you can set the allowance back to zero from your wallet, or by approving 0 for the token, so the contract has no standing permission over your balance.
What Arc Token Multisender does
Every option you need to airdrop an ERC-20 or native USDC to thousands of Arc wallets in batched calls — configured before you sign, not patched in afterwards.
Batched, not one-by-one
Recipients are grouped into batches so the per-transaction overhead is paid a handful of times rather than once per wallet — the difference between an airdrop you can afford and one you cannot.
ERC-20 and native USDC
Airdrop any ERC-20 on Arc, or distribute native USDC directly. Save a holder snapshot and the export drops straight into this form.
Per-row amounts or a flat amount
Give every wallet the same amount, or supply a two-column list where each recipient gets a different figure. Both formats are validated before anything is signed.
Validation before you pay
Every address is checksum-checked and every amount parsed in the browser. Malformed rows are flagged and excluded so you never spend gas on an entry that cannot succeed.
Approval you control
The tool requests an allowance for exactly the total you are sending. You can also revoke the allowance afterwards in a single follow-up transaction.
Live batch progress
Each batch reports its own status and transaction hash as it settles. If a batch fails, the tokens stay in your wallet and the remaining batches continue.
Arc Token Multisender — frequently asked questions
Straight answers about how this works on Arc Mainnet, what it costs and what happens onchain.
How much does an Arc airdrop cost?
Why do I have to approve the token first?
How many wallets can I airdrop to?
Where do I get the list of holders?
What happens if one address in my list is invalid?
Can I use the multisender for an NFT or a native USDC payout?
More questions? Read the full FAQ or contact the team.
Guides for Multisender
Long-form walkthroughs with the exact clicks, amounts and gotchas.
How to Airdrop Tokens on Arc with a Multisender
Snapshot, filter, approve and batch send tokens on Arc Mainnet, with the real USDC cost of an airdrop broken down batch by batch before you sign anything.
Read the guideTools that pair with this one
Everything on Arctools shares one wallet, one USDC balance and one flat fee.
Arc Token Snapshot
FreeExport every holder of an Arc token or NFT collection at any block.
Open SnapshotsArc Token Launch
50 USDC flatDeploy a fully configurable ERC-20 on Arc Mainnet in a single transaction.
Open Token LaunchBurn Tokens on Arc
50 USDC flatPermanently destroy tokens to cut supply and prove it on the Arc Explorer.
Open Token BurnReady to multisender on Arc Mainnet?
Connect a wallet, pay 50 USDC once, and everything settles in under a second.