Wallet List Format
Wallet list quality matters because invalid inputs create avoidable setup and launch failures.
What a Wallet List Represents
A wallet list is the dataset that says who should receive tokens and how much each wallet should receive.
At the simplest level, it looks like:
wallet_address, amountFor a campaign with n recipients:
L = { (w₁, a₁), (w₂, a₂), ..., (wₙ, aₙ) }That same logical structure is what later becomes an onchain list entry set or a merkle-based dataset.
Recommended Practice
- Keep one wallet per line or row.
- Validate addresses before upload.
- Keep amounts aligned with your distribution logic.
- Save the source file you used for the launch.
Good Input Habits
| Practice | Why it helps |
|---|---|
| One recipient per row | Makes validation easier |
| Clean amount formatting | Avoids parsing confusion |
| No accidental duplicates | Prevents double allocation mistakes |
| Keep the original source file | Helps with audits and reruns |
Example
If every recipient gets the same amount, your logical dataset still has one row per wallet:
wallet₁, 50
wallet₂, 50
wallet₃, 50
...If allocations differ by tier, keep the amount explicit in every row rather than relying on assumptions outside the file.
Before Uploading
Check these questions:
- Are all wallet addresses valid?
- Does each row have the intended amount?
- Are there accidental duplicate wallets?
- Does the list match the campaign you are about to launch?
Read Next
Last updated on