Creators
Launching
Follow the WickDeck launch flow on Whitechain: connect a wallet, choose a token template and market tier, publish metadata, and submit.
What is it?
Launching creates a token and opens its bonding curve. The compose flow is at Launch. Submitting requires a connected wallet. Reading the form does not.
Why does it exist?
Every native market has to pick a raise asset, a tier, a token template, and a token identity before the factory will deploy. The review ticket is there so those choices are visible before signature.
How does it work?
- Choose a token template (Standard, Burn, Fee, or Rewards). Wick Standard still applies. Custom is not self-serve.
- Choose a raise asset (WBT, USDC.e, USDT.e, or bridged ETH) and a market tier.
- Set name, symbol, and metadata. Reserved names are blocked.
- Review the Wick Standard checks on the ticket.
- The launch fee follows the factory's fee policy. Kind None is free. Base charges a listed amount of an enabled payment asset (WBT, or another enabled asset at that asset's own discount). LaunchToken allocates a percent of the new supply, default 1% and capped at 5%. BaseAndToken charges both. The creator picks the payment asset, not the rate.
- Fixed supply
- Cannot mint more
- Cannot blacklist
- Cannot change fees
- Cannot pause sells
- Defined Ignition path
What can go wrong?
A submitted launch can still expire, fail to Ignite, or trade poorly. Metadata can be misleading. The factory will not check whether the project is real.
What should traders understand?
If you are evaluating a new market, read the ticket facts (tier, Fair Start, raise asset) and then Scan. Creation itself is not a signal of demand.
WickDeck protocol constraints can reduce certain technical risks, but cannot guarantee token value, creator behavior, market liquidity, or trading outcomes.