Customer guide: Prelaunch mint confirmation

Version V0.0.3

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.

Recommended sequence:

1. Register your creator wallet with TokenOps before launch.
2. Buy the pre-registration pack. 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.