Arc

Creators

Launching

Follow the WickDeck launch flow on Arc: connect a wallet, choose token mechanics and market tier, publish metadata, post the creator bond, 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 raise asset (USDC or EURC) and market tier.
  • Set name, symbol, and metadata. Reserved names are blocked.
  • Post the USDC creator bond required by the tier.
  • Review the Wick Standard checks on the ticket.
  • The create fee is factory.createFeeUsdc() on-chain. Docs do not invent a dollar figure.
  • 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, bond, 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.