Customer guide: Prelaunch mint confirmation

Prelaunch registration help: required and optional form fields, payment before submission, unavailable or offline registration, and mint confirmation after launch.

Version V0.0.4

Prelaunch Registration records your creator wallet and launch intent before your token mint exists.

After you create the token, return to TokenOps before you revoke mint or metadata authority. This gives TokenOps the best chance to verify that the creator wallet you registered is connected to the mint you created.

Before you start: availability, form fields and payment

Why does the page say registration is not available or offline?

If the page says "Prelaunch registration is currently not available" and explains that an admin feature flag controls it, public registration has not been enabled. The page can still be reachable while its form is hidden. Refreshing or clearing your browser cache does not enable registration.

Contact TokenOps support through BEX Contact if you expected registration to be available. Include the page URL and displayed error, without wallet secrets. If a different loading error appears, it may need a separate connection or service check.

Operators can check Global Settings > Prelaunch Registration. Public registration, mandatory payment and checkout availability are separate settings. Enabling the form alone does not make payment mandatory. For paid registration, check the payment requirement, checkout preview/handoff and an available package together. This FAQ describes the controls; it does not assert that registration is currently enabled or disabled.

Which fields can I fill in?

• Creator Wallet (required): the Solana creator wallet used for the registration and later mint confirmation.
• Project Name (required): up to 120 characters.
• Symbol (required): 2-10 characters.
• BEX Detail logo (required): an image URL or upload. The form recommends a square image of at least 256 x 256 pixels.
• Banner logo (optional): an image URL or upload; the form recommends 600 x 200 pixels or wider.
• Description (optional): up to 5,000 characters.
• Recovery Email (optional): a support contact if checkout is interrupted.
• Recovery Telegram (optional): a support contact for recovering the paywall link.
• Socials and evidence (optional): add multiple entries, each with a channel type, URL or supported handle, and an optional short note. Types are Website, X, Telegram, Discord, DexScreener, CoinGecko, CoinMarketCap, GitHub, Docs and Other.

Logo uploads support PNG, JPEG, WebP and GIF and require connecting and signing with the creator wallet. Image URLs must be valid HTTPS URLs; supported domain inputs are normalized by the form.

You do not need a mint address for the initial pre-registration. Submit it later, after creating the token, in the mint-confirmation step below. Verification method, registration status and payment references are system fields, not form inputs.

When do I pay?

You can fill in the form before buying a package. When paid registration is enabled, an active prelaunch package is required before the final "Submit prelaunch registration" action can succeed. Both the form and backend enforce this requirement. Payment is not deferred until after the registration is saved.

Buy the package through the paywall, wait for confirmation, return to the registration form and check the package before submitting. Paying alone does not submit the registration. If paid registration is disabled, that package gate does not apply; public registration must still be enabled separately.

Register and confirm your launched mint

Recommended sequence:

1. Connect your creator wallet and fill in the pre-registration form before launch.
2. When paid registration is required, buy the pre-registration pack and wait for payment confirmation. Return to the form, check that the package is available, and submit the registration. The payer wallet may be different from the creator wallet, but the checkout must stay authenticated as the creator wallet until the paywall asks for the payment transaction.
3. Create the token mint on your launch platform.
4. Return to TokenOps before revoking authority.
5. Connect and sign with the same creator wallet.
6. Submit the created token mint.
7. Wait for TokenOps to record the mint/creator evidence.
8. Revoke authority where appropriate for your token setup.
9. Trigger or wait for a revocation status check.

What to enter when confirming the launched mint:

• Launched Mint: paste the token mint address of the token you created on Pump.fun or another launch platform. This is the only required field in that confirmation step.
• Launch Platform: keep Auto-detect unless you know the exact launch platform. Selecting Pump.fun is a routing hint for checks; it is not proof by itself.
• Optional Note: leave it empty if there is nothing special to explain. You may add a Pump.fun page URL, Solscan transaction link, launch transaction, or a short note such as "created on Pump.fun with the registered creator wallet". Do not paste seed phrases, private keys, wallet login data, or unrelated personal information.

Provider choice can affect the strongest evidence TokenOps can later detect. Read which Solana launch provider gives the strongest BEX verification before choosing a launch path.

Why the timing matters:

• If TokenOps sees current authority before revocation, it can record a stronger evidence snapshot.
• If authority is already revoked, TokenOps may still find historical evidence, but that is a different and usually weaker evidence level.
• If TokenOps only sees that authority is revoked without a prior creator/mint snapshot, it cannot honestly say it verified the creator relationship before revocation.

Revocation after verification can be useful because it shows that TokenOps first observed the creator/mint relationship and later observed that authority was removed or made immutable. This is still not a safety guarantee, but it is a stronger factual signal than a self-submitted claim.

Payments are for processing and workflow access. They do not guarantee approval, safety, public listing, or refunds after rejection.

Payment-wallet note: if you want to pay from another wallet, use it only as the payment wallet when the paywall requests the transaction. Do not replace the pre-registration creator/auth wallet with the payer wallet, or the checkout may report a wallet mismatch.