What is Pre-Launch Registration?
Version V0.0.4
Pre-Launch Registration is a timestamped intent record for a founder or creator wallet before a token launch is live.
It can store the intended project name, symbol, creator wallet, description, and public links. The record helps BEX compare later launch evidence with the wallet and metadata that were registered before launch.
Pre-Launch Registration does not create a public BEX project profile by itself. It does not prove token safety, ownership approval, market quality, or legitimacy.
It is one part of a broader Pre-Verification model: moving useful evidence earlier, before the market has only hype, charts, and influencer posts to work with.
Creator wallet and payment wallet
The pre-registration is tied to the creator wallet that signs the intent. That creator/auth wallet remains the wallet TokenOps uses for the prelaunch record and later mint confirmation.
The wallet that pays for the pre-registration pack can be different. For example, a team may register the creator wallet but pay the package from another Solana or BSC wallet. During checkout, keep the pre-registration authenticated with the creator wallet; switch or connect the payer wallet only when the paywall asks for the payment transaction.
After launch, the strongest path is to return to TokenOps before revoking mint or metadata authority. The creator wallet signs again, the customer submits the new mint, and TokenOps records the strongest evidence available at that time. Later authority revocation can become an additional factual signal if TokenOps first captured the creator/mint relationship before revocation.
What it can provide:
- a timestamped platform record;
- the wallet that submitted the intent;
- the intended name and symbol;
- optional public links and description;
- a later place for manual or automated launch evidence;
- a later revocation evidence signal when authority was first verified and then revoked.
- earlier public history that can help distinguish a real launch from later copycats or impersonation attempts.
What it does not provide:
- automatic token listing;
- automatic owner approval;
- a trust score;
- a guarantee that the launched token is safe;
- proof that every copycat or similarly named token is unrelated.
Users should treat prelaunch data as one research signal, not as a safety guarantee.
Why this can matter:
- investors can compare a live token against earlier registered claims;
- founders can establish a public timestamp before launch;
- communities can inspect whether the launched mint matches the earlier project intent;
- researchers can review wallet, liquidity, burn, permission, and behavior signals earlier.
Related FAQs: