Why Funding 20 Launch Wallets Isn't One Transaction

Prepping a launch with a full set of snipe wallets can mean funding twenty separate addresses before you even get to the actual buy. The natural assumption is that one wallet sending twenty transfers should be one transaction. It isn't, past a certain point, and the reason is a hard limit rather than a design choice.

The 1,232-byte ceiling

A Solana transaction can't exceed 1,232 bytes — that's the space left over after network packet headers, and it's enforced by the protocol itself, not by any wallet or app. Every transfer instruction you add takes up part of that budget. Stack enough of them in one transaction and you hit the ceiling before you run out of wallets to fund.

What that means in practice

Rather than guess at exactly where that line falls and risk a transaction that silently exceeds it, our Fund Wallets flow batches transfers in groups of eight, sent as separate sequential transactions. Funding twenty wallets becomes three transactions instead of one — a small, deliberate margin below the real limit, not an attempt to squeeze in the maximum possible per transaction.

Why not just push closer to the limit

Squeezing more transfers into fewer transactions would mean less margin for error if any per-transfer overhead changes, and it buys very little — a couple of transactions saved on a twenty-wallet launch, at the cost of a batch that's more likely to fail outright if it's ever slightly miscalculated. We'd rather it just work every time.

This batching happens automatically in the Fund Wallets panel — you see one "funding" step, and the batching itself stays invisible as long as every batch succeeds. Wallets funded by an earlier batch keep their balance even if a later one fails, so nothing gets double-sent if you retry.