SPL Token Distribution Checklist Before You Send

1. Confirm the asset and network

Start with the selected Solana network and the exact SPL token mint. Token names and symbols are not unique, so the mint address is the identifier that matters.

Confirm the token decimals as well. Decimal precision determines how a visible amount is converted into the integer base units used by the transfer instruction.

• Correct Solana network selected
• Mint address copied from a trusted source
• Token symbol and decimals match the mint
• Connected wallet is the intended sender

2. Freeze and review the recipient list

Use a final version of the recipient file for the run. Changing rows while another person is reviewing totals creates avoidable uncertainty.

Check every address-and-amount pair, resolve duplicates, and compare the final recipient count and token total with the approved allocation record.

• One reviewed source file
• Duplicate policy applied
• Amounts fit the token's decimal precision
• Recipient count and total amount approved
• No private information included

3. Fund both value and execution costs

The sender needs enough SPL tokens for the allocation and enough SOL for transaction fees. Some recipients may also need an associated token account created for the mint, which can add rent-related cost.

Review the balances immediately before sending. A previous transaction can change the available amount even when the recipient file has not changed.

4. Use a test batch and read the wallet prompt

For a new mint, a new recipient source, or a material change in process, start with a small group of wallets that you can verify. Confirm their balances and transaction details before proceeding with the larger list.

When the wallet prompt appears, verify the connected account, network, and transaction request. Do not sign because the page looks familiar; sign because the reviewed details match the intended operation.

5. Keep proof and stop on uncertainty

After sending, save the transaction signature and inspect it on a Solana block explorer. Compare completed and failed results with the approved source list before planning another run.

Stop if the mint, total, fee requirement, wallet prompt, or recipient list is uncertain. A delayed distribution is easier to repair than an irreversible transfer to the wrong address.

• Transaction signature saved
• Explorer status checked
• Recipient outcomes compared with the source file
• Failed rows isolated before any retry
• Run record retained for the team