What Happens If You Pick the Same Wallet for Two Roles in a Launch

Say you've got a wallet you want to use as both a bundle buyer and a snipe buyer on the same launch — maybe it seems like a way to give it a bigger role without adding a new wallet to manage. Our launch flow won't let you pick it twice, and once you see why, it's a fairly small thing.

What we check for

Once a wallet is picked for one role, it disappears from the dropdown for every other role in the launch — dev, bundle, and snipe all read from the same "already in use" list, so you physically can't select the same wallet twice through the UI.

There's a second check behind that one, server-side, in case a duplicate ever gets through some other way: every wallet ID in the launch gets compared before anything is submitted, and a repeat returns a direct, specific error — "the same wallet is selected in more than one place" — rather than a vague ownership failure that wouldn't tell you what actually went wrong.

What to do instead

If you want a wallet to hold a bigger position, the straightforward way is a larger SOL amount on the one role it's already assigned to, not a second assignment.

A related, narrower rule on the funding side

The Fund Wallets panel has its own version of this, scoped more narrowly: a wallet that's itself underfunded can't be picked as the source for funding the others, since it doesn't have enough to spare in the first place. A launch wallet that's already sufficiently funded isn't restricted the same way — it just isn't a candidate while it's still one of the wallets waiting on SOL.

This is purely a same-launch restriction — a wallet you used as a bundle buyer on one launch is completely free to be a snipe buyer on the next one.