> For the complete documentation index, see [llms.txt](https://docs.visionmakers.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visionmakers.io/platform/disperse.md).

# Vision Disperse

Send tokens to an entire address list in a single transaction

vDisperse distributes tokens to many addresses at once, for airdrops, payroll, community rewards
and contributor payouts. It is the automated distribution module of the platform.

## Why batch

Sending individually costs one transaction per recipient. For a 500-address airdrop that is 500
signatures, 500 gas payments, and a partially completed run if anything interrupts you halfway.

Batching reduces total gas substantially and makes the distribution atomic: it either completes
or it does not, with no half-finished state to reconcile.

## Running a distribution

1. **Prepare the list.** Recipient addresses with an amount against each.
2. **Upload.** The platform parses the list and reports what it found.
3. **Review validation.** Malformed addresses, duplicates, zero amounts and the computed total are all surfaced before you proceed.
4. **Approve the token spend**, scoped to the total required rather than unlimited.
5. **Sign one transaction.**
6. **Verify.** The resulting transaction hash is your distribution record.

## Validation before signing

| Check | What it catches |
| --- | --- |
| Address format | Malformed or truncated addresses |
| Duplicates | The same recipient listed twice |
| Zero and negative amounts | Rows that would waste gas or fail |
| Total against balance | A distribution you cannot cover |
| Contract addresses | Recipients that are contracts rather than wallets |

<div class="callout">
<span class="callout-label">Validation is not verification</span>
The platform can tell you an address is well formed. It cannot tell you it is the right address.
A correctly formatted wrong address passes every check and the tokens are gone permanently. Test
with a small batch first.
</div>

## Common uses

| Use | Pattern |
| --- | --- |
| **Airdrops** | Large recipient count, equal or tiered amounts |
| **Community rewards** | Recurring, variable amounts by contribution |
| **Payroll and contributors** | Small list, regular cadence |
| **Competition prizes** | Driven by a [vMakers](/platform/vmakers) leaderboard |
| **Scheduled distributions** | Recurring, often with per-address amounts |

## Costs

You pay network gas for the single batch transaction, which scales with the number of recipients
but far less than sending individually. Platform fees are displayed before you commit.

## Limits

**Distribution is irreversible.** There is no recall, and no party can reverse it.

**Batch size is bounded by block gas limits.** Very large lists are split into several
transactions, each signed separately.

**Recipients must be able to receive the token.** Addresses on the wrong network, or contracts
that cannot handle the token, will fail or trap the tokens.

**Tax and reporting are yours.** Distributing tokens may create obligations for you and for
recipients. See [Risk Disclosures](/legal/risk-disclosures).

## Related

[Vision Makers Pad](/platform/pad) · [vMakers](/platform/vmakers)