Validate the distribution list
Keep the approved snapshot, token mint and recipient allocations in your own system. Check for duplicate wallets and assign each allocation to one clearly identified transfer.
TOKEN MIGRATIONS ON SOLANAA migration is one event.
A migration is one event.
Distribution reaches many.
Use Multi-Send to distribute supported tokens after a migration or as part of a launch workflow. Plan the recipient list, verify the quoted allocations and track payouts independently from the migration itself.
ILLUSTRATIVE WORKFLOW
- Approved holder allocations
- Batches of up to 20 wallets
- Recipient-level payout records
Your application owns the business process. MultiHopper supplies the routing step.
THE ROLE OF ROUTING
How does Multi-Send support token distributions?
For token projects and distribution platforms that already have an approved allocation list. MultiHopper can provide the routed distribution step on a supported Solana deployment. It does not create the replacement token, calculate holder eligibility or migrate a token contract for you.
A PRACTICAL EXAMPLE
Distribute an approved post-migration allocation.
Imagine a project finishing its eligibility review and preparing allocations for 35 wallets. Its application divides them into separately tracked transfers of no more than 20 destinations each. Before signing, the team verifies the mint, cluster support and each quoted post-fee payout. This is an illustrative plan, not a claim that a particular migration has completed.
Quote the recipient batches
Multi-Send allocation shares must equal the input total. Fees are deducted once from that total and payouts share the remainder. Check whether those net amounts satisfy your distribution plan before funding.
Track every payout
Follow the documented preparation and confirmation order, including the payout setup transactions. Reconcile each destination’s paid status and signature before marking its allocation delivered.
Implementation reference: Multi-destination implementation guide.
IN YOUR PRODUCT
Where it fits.
Post-migration allocations
Add routed distributions after your migration process has determined who receives which allocation.
Launch distributions
Coordinate supported-token payouts to several wallets with a reviewed allocation list.
Distribution platforms
Connect batch records, recipient status and support references inside your existing product.
LIMITS AND RESPONSIBILITIES
Define the boundaries before you build.
Public payout visibility
Destination addresses are excluded from the route’s published hop list, but payout transfers remain visible onchain. Multi-Send does not guarantee that wallets cannot be linked or clustered.
SPL deployment support
Confirm that the cluster’s program version supports SPL payouts for your integration. Do not assume that a token supported elsewhere in the product is automatically supported for multi-destination payout.
Batch and fee accounting
For more than 20 destinations, reconcile multiple transfers independently. Do not resubmit a paid allocation when recovering an incomplete batch; inspect its recorded status first.
Routing does not erase onchain history or guarantee anonymity. Smart-contract and execution risks remain. Review the security model and current audit status before selecting the value and scope of an integration.
CLEAR ANSWERS
Questions about token migrations.
Does Multi-Send migrate the token itself?
No. This use case concerns distribution. Token creation, migration mechanics, eligibility and allocation approval remain part of your project’s own workflow.
Can it remove wallet bundling from every analytics tool?
No such guarantee is made. The guide describes how destination commitments differ from the hop list, while explicitly stating that payouts are ordinary observable onchain transfers.
When is a distribution complete?
A Multi-Send transfer reaches completed only after all its destinations are paid. A distribution spanning several transfers needs an additional application-level check that every transfer and recipient is reconciled.
DOCUMENTATION AND EXAMPLES
Build from the documented workflow.
- Multi-destination implementation guide
- Pricing and cluster-specific fee schedules
- Security assumptions and audit status
- Developer quickstart
Watch the migrate.fun proof of concept ↗
See the existing migration-distribution case study and demonstration.
Reviewed October 5, 2026 against the linked documentation. Check the current guide and deployed cluster before implementation.
Explore related workflows.
Plan your token migrations integration.
Bring your workflow, supported asset and operational requirements to the team.