Why a Snipe Wallet Pays Its Own Jito Tip and a Bundle Wallet Doesn't

Every Jito bundle needs a tip to get considered for inclusion. On a Bundle-mode launch, the dev wallet pays one shared tip for the whole group. On a Snipe-mode launch, each wallet pays its own. That's not an oversight — it follows directly from how the two modes actually work.

One bundle, one tip

Bundle wallets submit together, as a single unit, in a single Jito bundle. There's one thing being submitted, so there's one tip attached to it, and the dev wallet — which is already paying to create the token — covers it. Splitting that one tip across multiple wallets would just move a small cost around without changing anything about how the bundle lands.

Many snipe wallets, many bundles

Snipe wallets aren't one submission — each one is its own independent single-wallet bundle, sent in parallel so that one wallet's outcome never depends on another's. Each of those independent bundles needs its own tip to be considered, the same way any Jito bundle does. There's no single shared submission to attach one tip to.

Why not have the dev wallet cover those too

It could, mechanically — but it would mean the dev wallet's balance requirement scales with how many snipe wallets you add, which gets expensive and opaque fast on a twenty-wallet snipe wave. Having each wallet cover its own small tip keeps the cost visible per wallet and keeps the dev wallet's requirement fixed regardless of how wide the snipe wave is.

This is why our balance checks size the buffer differently per role — a bundle wallet only needs to cover its buy plus rent, a snipe wallet needs to cover its buy plus rent plus its own tip. See choosing a buy mode for how the two roles differ more broadly.