Launchpad

The launchpad deploys a new ERC-20 token, initializes its market, and stores the metadata needed by the Vorax interface. The goal is predictable token creation: one launch flow, explicit configuration, verified contracts, and no silent fallbacks to reference deployments.

Launch Flow

1. Creator enters token name, symbol, image, description, website, and socials.
2. The interface derives launch configuration and validates it against contract limits.
3. Address suffix mining runs after the launch data is known.
4. The launch transaction deploys the token and initializes the configured market.
5. Backend services cache launch metadata, image references, and airdrop data.
6. The token page reads Vorax launch metadata before using external market data.

Address Suffix Mining

Vorax can search for a deterministic token address suffix before deployment. Mining is performed after the launch form is complete because the final deployment input depends on the token configuration.

Production behavior:

• Browser mining runs in a Web Worker so the form remains responsive.
• Candidate results are cached per launch draft.
• Backend mining can be used as an acceleration path, not as a trust assumption.
• Suffix difficulty must remain realistic for normal laptops and phones.

BSC Constraints

• Vorax launchpad production is BSC-only.
• Static-fee launch behavior is the production path.
• Creator buy remains disabled unless final BSC contracts and UI support it.
• Production builds must use Vorax-owned contract addresses.

Creator Checks

Before signing, creators should verify:

• Token name, symbol, description, image, and social links.
• Admin address and fee recipient.
• Airdrop root, if an airdrop is configured.
• Vault configuration, if tokens are locked.
• The predicted address suffix, if suffix mining is enabled.

Operator Checks

Before enabling production launches:

• Factory, hooks, lockers, extensions, fee recipients, and owner values are verified.
• Deployment scripts and verification scripts run against the final BSC RPC.
• UI constants are generated from the final deployed contracts.
• Backend health, metadata cache, image upload, and airdrop registration are live on the production domain.