Wallets & Holders

Configure generated, imported, and empty holder wallets and their launch allocations.

Network scope: Panda Bundler supports Pump.fun on Solana, Pons on Robinhood Chain, and Uniswap on Ethereum. Features, wallet limits, funding routes and launch controls vary by venue. SOL, Jito and Solana-address examples below apply only to Solana; do not reuse them for an EVM network. Select the correct network in the live app and confirm its requirements before funding or signing.

Every launch assigns roles and token-buy allocations to a wallet set.

Panda Bundler wallet modes and allocation flow

Wallet sources

• Generated wallets — new wallets created inside the Bundler workspace.

• Imported wallets — existing wallets added to the account and selected for the draft.

• Empty holders — wallets included in the configuration without an initial token allocation.

• Operational wallets — developer, MEV, worker, funding, or other roles shown by the current mode.

A launch configuration can contain up to 200 holder wallets. The active product view is the source of truth for the allowed count and role combination.

Allocation

Use Token Buy % to define each participating wallet's share. Review the total allocated percentage, required network asset per wallet (SOL in Solana workflows), role labels, generated versus imported status, and whether a wallet is already assigned elsewhere.

Holder-map expectations

Wallet allocation affects the resulting holder distribution, but it cannot guarantee a clean graph or hide on-chain relationships. Funding paths, transfers, timing, token accounts, and later trades remain public and can be grouped differently by third-party analytics.