Team co-sign launches: independent wallets, one coordinated create

The short answer

Select Team, enter creator buy (may be zero) plus additional buyers with wallet + SOL amount. Prepare the launch (metadata + simulation). Creator connects and signs create. Each team wallet connects in turn and signs only its buy. Submit: on mainnet as one Jito bundle; on devnet as create-first, then member buys.

Prep the team before anyone signs

1. Agree amounts and wallets offline; paste exact addresses into Launch.
2. Each member funds their own wallet with buy amount + fee buffer.
3. Creator funds create, optional own buy, and—on mainnet—platform fee + tip.
4. Use a shared settings link if helpful, then re-check every wallet string before prepare.

Order of operations in the UI

1. Creator prepares. Metadata upload and simulation. Fix any preview error before collecting signatures.
2. Creator signs create. Includes optional creator buy and, on mainnet, settlement pieces the product attaches.
3. Member signs buy. Connect the exact wallet listed for that buy. The UI should refuse a mismatched address.
4. Repeat members until every non-zero buy has a signature.
5. Submit coordinated launch. Mainnet: atomic bundle. Devnet: sequential after create lands.

Why mainnet and devnet feel different

Mainnet Team aims for all-or-nothing landing via Jito: create, member buys, and settlement packaged together. Devnet is for practice and may confirm create first so you can debug without requiring full atomic infrastructure.

For general bundle context, see bundles and atomic execution.

Failure modes operators should plan for

• Wrong wallet connected for a member step.
• Insufficient SOL after fee / tip / rent checks.
• Simulation fails after an amount or metadata change—re-prepare.
• Bundle accepted by a relay but not landed—wait for confirmation UI, do not rebroadcast the same signatures blindly.
• A member drops mid-session—cancel and rebuild rather than partial social claims.

Primary and official sources