Build a Safe CSV Airdrop file from your payout sheet

A payout sheet as a team keeps it, and the CSV Airdrop file this page builds from it. The amounts lose their formatting but not a digit, the token becomes its contract on Base, and Mei Lin’s address, pasted in lowercase, gets its checksummed (EIP-55) form.

The app reads a comma-separated file with a header row and one transfer per line. This page writes exactly these columns, in this order:

• No other columns. A name, a note or a decimals column makes the app refuse the whole file with “Unknown header field(s)”. It looks up each token’s decimals itself, from the Safe’s balances or the token contract.
• No more decimals than the token has. The app multiplies the amount by the token’s decimals and drops anything finer without a warning. USDC and USDT have 6, so this page refuses 2437.3333333 instead of letting it become 2437.333333.
• At most 499 transfers per file. The app refuses a file longer than 501 lines and counts the line break at the end as one; with the header line, that leaves 499.
• One network per file. The app runs inside a Safe, and a Safe lives on one network. A sheet that pays on Base and on Arbitrum One becomes two files, one for each Safe.

The header line, as the app expects it: token_type,token_address,receiver,amount,id

A wrong token contract is the quietest mistake in a CSV Airdrop file. Native USDC and bridged USDC.e on Arbitrum One are different tokens, and a contractor’s exchange may credit only one of them. The sheet says USDC or USDT; the file gets the contract below for the row’s network.

Not in the list: USDT on Base, because it is a bridged copy of Ethereum USDT, not issued by Tether, and exchanges may not credit deposits of it. A row in USDT on Base is refused.

• A look-alike address. One that starts and ends like another address in the sheet but differs in the middle, the trace of address poisoning. To compare this month’s addresses with the ones you paid before, use the address checker.
• A retyped address. Mixed case that doesn’t match the EIP-55 checksum means at least one character is wrong, and the row is refused. An all-lowercase address has no checksum to check; the file gets its checksummed form.
• A TRON address on an EVM row. USDT on TRON (TRC-20) and on Ethereum or Arbitrum (ERC-20) look alike in a sheet. A T… address on a Base row is refused, and rows marked TRON are left out: a Safe can’t pay them.
• The wrong token for the network. USDC.e anywhere but Arbitrum One, USDT on Base, or a token the registry doesn’t know.
• Amounts from a formula or a currency format. 2437.3333333, $3,200 or 3,20,0. Amounts are read exactly or not at all: nothing is rounded or guessed. If your sheet writes 3.200,50, choose that under “Amounts are written like”.
• A totals row, someone listed twice, a shared address. A row with an amount and no address is refused; the same person and address twice, or one address for two people, is flagged for you to check.

1. Build the files here and download the one for your Safe’s network.
2. Open your Safe in Safe{Wallet} on that network, go to Apps and open CSV Airdrop.
3. Upload the file or paste its text. The app lists every transfer with its token and amount: check the count and the total against this page.
4. Submit. The Safe gets one transaction with every transfer in it; the owners confirm it and one of them executes it.

Paying from Payclose? It proposes the batch to your Safe itself, and offers the same kind of file as a fallback: see paying from a Safe.

CSV Airdrop sends what the file says. It doesn’t know what you paid last month, who approved this month, or whether an address changed since the last payout, and for a monthly contractor payout that’s where the risk is. Payclose adds that around the same Safe:

• Every payout compared with the last one: people added or removed, amounts and addresses changed. The payout diff checker does this for two files.
• A new or changed address checked against every address you’ve paid, approved, and held for 24 hours before its first payout.
• Approvals signed with passkeys and recorded, then one batch per network proposed to your Safe.
• After execution, every transfer reconciled with the approved lines, and a proof file anyone can check.

Your owners still sign in Safe{Wallet}, and Payclose never holds funds or keys. More on contractor payouts from a Safe multisig.