Launch Settings

1. Reuse a Preset (optional)

   Select a recent launch or open Select a Preset to populate compatible settings. Skip this step to configure the launch manually.

   

   A preset can populate the form, but it does not validate the launch. Review the populated values before creating the plan.

2. Choose a launch mode

   Select Block-0, Quick, Organic, or Manual when available. The selected mode determines how deployment and the planned initial wallet actions run.

   

   Launch modes

   Understand each execution mode

   Compare how Block-0, Quick, Organic, and Manual execute the launch.

   Compare launch modes→
   

3. Set allocation and holder count

   Set the developer buy, holder allocation, and number of holder wallets. Use the unit displayed beside each field.

   

4. Configure Block-0 when selected

   Choose a displayed preset or configure the wallet layers and delays manually. This section appears only when Block-0 is supported by the active launch route.

   

   Block-0

   Configure the execution layers

   Compare presets, wallet layers, delays, and cost indicators before funding.

   Open the Block-0 guide→
   

5. Assign wallets

   Import wallets into the roles requested by the current plan, such as Deployer, Holders, or Block-0 execution layers. The role counters show how many wallets are assigned and required.

   

   Wallet inventory

   Prepare wallets before assigning them

   Create or buy wallets, then return here to assign each launch role.

   Open the Wallet Marketplace→
   

6. Choose funding

   Use standard funding, or enable CEX Funding when available. CEX Funding routes the distribution through the CEX sources shown in Proxima.

   

7. Advanced settings (optional)

   Open Advanced Settings only when the launch needs a deliberate change from its route defaults.

   

   • Slippage sets the allowed execution tolerance shown by the active route.
   • Funding Delay delays wallet funding by the configured minutes and seconds.
   • Alternative Routing applies to the displayed share of eligible wallets and adds the per-wallet cost shown by Proxima.
   • Empty Holders adds holder addresses that do not buy at launch. Regular and empty holders cannot exceed the limit displayed in the form.
   • Fee Target adds the full value as a deploy-bundle tip bonus in Block-0 mode. In other modes, Proxima splits it randomly across the buy chunks.
   • Scheduled Mode executes deployment and the developer buy at launch, but waits to submit holder buys until you select Snipe in the Live Workspace.
   • Use Streamflow Airdrop for cleanup, when available, transfers tokens from input wallets to output wallets. Recipients claim equal shares; this is a transfer, not a trade.
   Scheduled Mode leaves the holder buys pending after deployment. Open the correct launch in the Live Workspace, recheck the holder plan, then select Snipe once. Verify the resulting wallet actions in History or Activity.

Resume a Streamflow airdrop

When a configured Streamflow cleanup has not finished, the Live Workspace displays its airdrop section. Resume only after confirming which input wallets already transferred tokens and which recipients still need to claim.

Do not run a normal Cleanup over the same wallets until the Streamflow state is known; the two flows move supply differently.